You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every now and then a node with an American call sign pops up in China on the meshmap, because someone forgot to put the minus sign in front of the Longitude.
Putting in N/S W/E radio buttons might make this possible oversight more apparent to the user.
Something like this, in pseudocode:
if (lat < 0) {
/* we can reasonable assume they meant S,
regardless of the radio button */
} else {
/* it is possible the negative sign was forgotten */
}
if (lon < 0) {
/* we can reasonable assume they meant W,
regardless of the radio button */
} else {
/* it is possible the negative sign was forgotten */
}
if (radio_lat == "S") {
lat = abs(lat) * -1;
} else {
/* they either appropriately selected "N" or
appropriately entered a S lat with negative
number */
}
if (radio_lon == "W") {
lon = abs(lon) * -1;
} else {
/* they either appropriately selected "E" or
appropriately entered a W lon with negative
number */
}
Or more simply:
if (radio_lat == "S") { lat = abs(lat) * -1; }
if (radio_lon == "W") { lon = abs(lon) * -1; }
The text was updated successfully, but these errors were encountered:
Every now and then a node with an American call sign pops up in China on the meshmap, because someone forgot to put the minus sign in front of the Longitude.
Putting in N/S W/E radio buttons might make this possible oversight more apparent to the user.
Something like this, in pseudocode:
Or more simply:
The text was updated successfully, but these errors were encountered: