-
Hi, I am creating a local comma deliminated file to feed into the SHARP sounding program.
The data being stored, and forwarded to the sondehub database has some false winds at low levels.
Somehow…
-
Hello, for information, this morning I decoded a M10 901-2-11018 well, but invisible on sondehub, I started the SDR and the probe appeared well on Sondehub, sending data like the DFM17 does not work e…
-
The standard freqency is 434.74 though it should be 434.714. Please correct.
-
Until I figure out a better way to handle assigning a single custom data template to multiple callsigns, the Horus binary decoder assumes that the custom field section matches the format used by RS41n…
-
As per title, burst and landing locations cannot be clicked for more information when in Imperial units mode only. Works fine if swapped back to metric units. Tried in Chrome, Explorer and Edge same r…
-
The predictor code seems to make use of positions that have null position (e.g. lat/lon=0), resulting in dodgy ascent rate calculations if the payload has poor GPS lock.
The query used to get recen…
-
The small altitude plots in the payload list clearly have some kind of time scale issue, when comparing the data loaded via the API, and the new data coming in via websockets.
-
Hello, no tracking of DFM17 on Sondehub, decoding works but is not visible on Sondehub.
State: Connected: Waiting for ACK from server. Last upload start: -1 s ago Last reply: {"message": "some or a…
-
When tracking a sonde the left column shows details like
DATETIME(LOCAL)
BURSTTIMER
For those living near a timezone border this is ambiguous.
It is unclear whether the 'LOCAL' is referring to w…
-
I recovered T4820142 and wanted to report recover (with notes). Would be great if could report recovery without location services. (No location services available on reporting device or no desire to…