Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Treat a latitude containing a comma as a Latitude Longitude pair when entering a Waypoint #106

Closed
JohnLines opened this issue Oct 7, 2020 · 1 comment
Closed

Treat a latitude containing a comma as a Latitude Longitude pair when entering a Waypoint #106

JohnLines opened this issue Oct 7, 2020 · 1 comment

Comments

@JohnLines
Copy link

If waypoints are geing added manually, for example you know that at some point, such as an old fashioned paper diary you were in Berlin, and get find the location of Berlin by looking it up, you will know the position as 52.52, 13.405

Rather than the user having to split this, it would be useful the latitude contained a comma, to treat this as entering a latitude of 52.52 and a longitude of 13.405
@rnorris
Copy link
Collaborator

rnorris commented Oct 9, 2020

This should be straight forward to add.

NB FYI: As mentioned in the manual:
"One way to create new waypoints is to copy a latitude/longitude coordinate pair, such as the one shown on most geocaches, and paste it into an active TrackWaypoint layer. Viking can automatically recognize several variations of the lat/lon format."

Unfortunately if you paste text from a Web Browser it is internally in HTML format, and Viking may not understand that properly if it is not in UTF16 (possibly an older default whereas now it seems to be UTF8 - at least on my system). I'll fix this error.

Copying text from a terminal / plain text program like notepad / gedit should work.

rnorris added a commit to rnorris/viking that referenced this issue Nov 14, 2020
@rnorris
Github viking-gps#106: Allow entering lat/lon pairs of text in latitu…
c96c102 
…de fields.

Expose existing parser for more general use.
Use in Goto Lat/Lon dialog and Waypoint dialog.

Add some tests to show what strings can be handled presently.
@rnorris rnorris closed this as completed Nov 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rnorris @JohnLines