Open williamcioffi opened 5 years ago
I've added parameters to set lat and lon once for a prv output but i'm going to leave the issue open for now because I'm still not sure what best practices are.
add option so that this parameter could also be as long as the number of gonio hits. should add the ability to set the lq too in that case since these are probably from the boat track. could imagine an algorithm to convert signal strength to location quality but this is more opinionated than i want to be inside this simple function, so it should be left to the user.
ps how does the portal do this?
These don't matter, unless you care about the init values for
FastGPS
solved positions.The user should be able to specify the either a single lat/lon to use for the entire output
prv
or a series of lat/lon's to be used for each message. Right now for simplicity all data is reported under a single fake Argos message pass. So I guess if you give one lat/lon it would still produce a single pass in theprv
and if you gave the right number of lat/lon's then it would make one pass per Goniometer hit.One trouble is if there are lots of other Gonio hits, then the user will have to figure out how many lat/lon's they need. So I might need some helper functions to assist with that.
Here are some possibilities for how you would select different lat/lons as the "fake Argos Doppler position":
parsegonio
.parsegonio
. Since the range of the goniometer is limited, the boat should always be within 10 miles or so of the tag when it receives a message.parsegonio
.parsegonio
(I think I can) and then combine the gonioprv
with the realprv
and re-decode them. DAP / Argos Message Decoder then should use a reasonable init location from whatever was received on the satellite nearest in time.