forked from n6cta/mwtchahrd
Parse APRS location from packets that have that information. #26
Reference in New Issue
Block a user
Delete Branch "aprs_loc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #10.
21499a93d97ce55f020bad5f2ccd0dHad a thought about a missing piece as I was falling asleep, now I can't remember it!
EDIT: Remembered, it was that I didn't check the lat/lon values against 9999 before sending them on.
Are these values too long? Spothole doesn't seem to pick up all the locations.
"dx_latitude":47.94133333333333,"dx_longitude":-97.02683333333333,curl seems to work:
curl --request POST --header "Content-Type: application/json" --data '{"dx_call":"M0TRT","time": 1761415746, "freq":14200000, "comment":"Test spot please ignore", "de_call":"M0TRT", "dx_latitude":47.94133333333333, "dx_longitude":-97.02683333333333}' https://spothole.w1cdn.net/api/v1/spotI think I was running on two machines at once, one only with locations and one with all UI frames. This was messing up the mapping.
Oh things got simpler; you can send an empty string to json lat/lon and it will be interpreted as a bad location by spothole. I thought I would have to send a specific
Noneornullor empty number (whatever that looks like).You can also send lat/lon as strings:
curl --request POST --header "Content-Type: application/json" --data '{"dx_call":"W1CDN","time": 1761447599, "freq":14200000, "comment":"Test spot please ignore", "de_call":"W1CDN", "dx_latitude":"47.94133333333333", "dx_longitude":"-97.02683333333333"}' https://spothole.w1cdn.net/api/v1/spotAnd spothole will parse/map right:
Location caching is next. Deciding whether to finish off this PR with only sending spots with parsed locations (so the map always works) or to leave it as everything for now (and the map locations will be overwritten by UI frames with no location data).
We discussed #11 on Matrix: https://matrix.to/#/!bVjIHuavAgnyyjeDTM:matrix.farpn.net/$bryXVDi7prNeZBnEZwKjf9ysMh19A2D1V-ilO8zbnz0?via=matrix.farpn.net&via=matrix.org&via=im.xoo.sh
Leaving this running for a while to see if location caching works, but fewer 20m packets in the dark.
I opened a ticket with Ian to see about differentiating SSIDs in Spothole code: https://git.ianrenton.com/ian/spothole/issues/68.
Ian has updated Spothole to account for SSIDs: https://git.ianrenton.com/ian/spothole/issues/68#issuecomment-759.
I have updated https://spothole.w1cdn.net with the changes.
We really should submit
dx_ssidas integer rather than string though.Parse APRS location from packets that have that information.to WIP: Parse APRS location from packets that have that information.Not sure I completely understand, but clap must be handling empty references.
WIP: Parse APRS location from packets that have that information.to Parse APRS location from packets that have that information.