This returns nothing as the data has been removed from elasticsearch.
The data needed to populate this element has actually already been downloaded in the S3 file.
To use this the S3 file should be stored in local memory and when clicking on path we need logic to check if the sonde is using elasticsearch or s3 data and switch accordingly.
For sondes older than 3 days we don't keep their data on elasticsearch and instead rely on the s3 archived file.
For example: https://sondehub.org/W0140427
The problem is when clicking on a point along the sondes path to get more information an API call is made to:
https://api.v2.sondehub.org/sondes/telemetry?duration=0&serial=W0140427&datetime=2024-06-29T00:41:48.000Z
This returns nothing as the data has been removed from elasticsearch.
The data needed to populate this element has actually already been downloaded in the S3 file.
To use this the S3 file should be stored in local memory and when clicking on path we need logic to check if the sonde is using elasticsearch or s3 data and switch accordingly.