Closed mbof closed 6 months ago
My theory at this point is that a latitude above 90 degrees or a longitude above 180 degrees can pass through the parser somehow, and then generates bad config data. This runtime check should prevent bad data from being accepted by the waypoint editor.
It's possible for some waypoint coordinates to get misparsed, and end up with "NaN" in latitude and longitude. Not sure how to repro it but there should be guards against it so that invalid data doesn't get written to the device.