Automatic pasting of coordinates copied in different formats
It would be nice to have some feature which will accept many different formats of coordinates. People are different and are passing the coordinates in many strange forms. It would be nice to have and option in Add New Point ( or anywhere you are pasting a coordinates) to just paste the coordinates string in any format ( I can prepare the list of all crazy possibilities I encountered). Then Locus would parse the string ( possibly with usage of regex) and just accept it. Now, the manual writing the degrees, minutes and seconds is fatal. I know people who just don`t know how to copy/paste, so when they see the cache, which has any calculations of coordinates in it - they simply give up. Locus should be more flexible in this topic.
User should:
1. read the descripion of the cach,
2. calculate or find any coordinates in the description,
3. copy them,
4. and paste easily in the Add New Point:
- in any of the fields
or
- create a new field for the pasted data
or
- parse the clipboard for the copied coordinates and automatically put them to the coordinates editboxes ( and somehow inform the user about that fact)
I like this idea 
Menion, so how it works now?
Menion, so how it works now?
Hmm, current implementation ...
Best is to check this doku: http://docs.locusmap.eu/doku.php/manu...
bottom part "Clipboard"
Hmm, current implementation ...
Best is to check this doku: http://docs.locusmap.eu/doku.php/manu...
bottom part "Clipboard"
wow. I totally forgot about this thread, and now I`m experimenting with this pasting from clipboard.
1. From my point of view, this text field should be already filled with data from clipboard. User don`t want to spend another two seconds on thing that can be done automatically. Locus should just take a clipboard contents and paste it into TEXT editbox and parse it.
2. I found it really hard to correctly fill this field. Many times I`m taking coordinates from different sources and they just don`t work. And Locus is not helping me with debugging them (Invalid value). What would you say if I will gather a list of all types of coordinated encountered by me in different places? If you like, I can even help you more. I`m specialising in regular expressions, so if you will give me a piece of code responsible for parsing these coordinates, I can take it and extend it greatly.
wow. I totally forgot about this thread, and now I`m experimenting with this pasting from clipboard.
1. From my point of view, this text field should be already filled with data from clipboard. User don`t want to spend another two seconds on thing that can be done automatically. Locus should just take a clipboard contents and paste it into TEXT editbox and parse it.
2. I found it really hard to correctly fill this field. Many times I`m taking coordinates from different sources and they just don`t work. And Locus is not helping me with debugging them (Invalid value). What would you say if I will gather a list of all types of coordinated encountered by me in different places? If you like, I can even help you more. I`m specialising in regular expressions, so if you will give me a piece of code responsible for parsing these coordinates, I can take it and extend it greatly.
also forget to close this topic ;)
ad 1. agree, make sense ... done
ad 2. regular expressions are still quite a mystery for me. No, not so bad, but I rather around weeks ago ordered big book just about this http://knihy.cpress.cz/regularni-vyra... - should be delivered every day :). Because it`s quite useful method and I still have much to learn.
So if you can post me here or on email any coordinate sample that do not work, I`ll try to find a way and in case I`ll not be success, I`ll use your offered, appreciated, help
also forget to close this topic ;)
ad 1. agree, make sense ... done
ad 2. regular expressions are still quite a mystery for me. No, not so bad, but I rather around weeks ago ordered big book just about this http://knihy.cpress.cz/regularni-vyra... - should be delivered every day :). Because it`s quite useful method and I still have much to learn.
So if you can post me here or on email any coordinate sample that do not work, I`ll try to find a way and in case I`ll not be success, I`ll use your offered, appreciated, help
Wow. Do you really have time for reading books? I didn`t read anything for a looong time:/ My whole knowledge is internet based. Google is always helpful when you need to learn a new topic. I will put some good regex stuff for you in my folder in dropbox.
Wow. Do you really have time for reading books? I didn`t read anything for a looong time:/ My whole knowledge is internet based. Google is always helpful when you need to learn a new topic. I will put some good regex stuff for you in my folder in dropbox.
Remember that parsing coordinates in Locus shouldn`t be like this: "Give me a text, I will parse it for you, but remember that this text must be well formatted. If not, change it, before I will parse it for you." This means user needs to remember the correct format of coordinates. What if the user is just a normal person who don`t get what he only see: "Invalid value"? Believe me that this is frustrating. Thats why I created a list of all crazy coordinates format I found in different places/applications/webpage/geocaches and so on. I didn`t create them, people did. These are real examples, how people imagine and send coordinates:
+54.598660, +16.913420
-------------------------------
N50 36.780
E19 29.588
-------------------------------
N 51° 06.111`
E 21° 04.788`
± 0.1 m
-------------------------------
prawie dziala, trzeba usunac spacje przed E i zrobic ja jeszcze raz
51°24,061 21°09,477
-------------------------------
51°23,997` 21°09,775`
-------------------------------
N 51°24.160` , E 21°09.846`
-------------------------------
51 03.548 E021 05.437
-------------------------------
Averaged location:
N 51° 06.111`
E 21° 04.788`
± 0.1 m
-------------------------------
Google Maps link:
https://maps.google.com/?q=51.10185,21.07979
-------------------------------
N 51°35.103` | E 21°32.970`
-------------------------------
N 52°07.405` E 21°19.384`
-------------------------------
Coordinates: N53° 55.057 E022° 09.927 ± 0.2 m
-------------------------------
N 53°55.427
E 022°11.025
-------------------------------
N 53° 55.126
E 022° 09.534
-------------------------------
I am here: 52 48.678 N 16 10.362 E
-------------------------------
http://maps.google.com/maps?q=loc:52.81130,16.17270
-------------------------------
galileo://51.424489,21.3114564
Some of them are multilines. People sometimes are copying several lines from different sources, so it is also important to analyze the whole string and just rip coordinates from them.
Remember that parsing coordinates in Locus shouldn`t be like this: "Give me a text, I will parse it for you, but remember that this text must be well formatted. If not, change it, before I will parse it for you." This means user needs to remember the correct format of coordinates. What if the user is just a normal person who don`t get what he only see: "Invalid value"? Believe me that this is frustrating. Thats why I created a list of all crazy coordinates format I found in different places/applications/webpage/geocaches and so on. I didn`t create them, people did. These are real examples, how people imagine and send coordinates:
+54.598660, +16.913420
-------------------------------
N50 36.780
E19 29.588
-------------------------------
N 51° 06.111`
E 21° 04.788`
± 0.1 m
-------------------------------
prawie dziala, trzeba usunac spacje przed E i zrobic ja jeszcze raz
51°24,061 21°09,477
-------------------------------
51°23,997` 21°09,775`
-------------------------------
N 51°24.160` , E 21°09.846`
-------------------------------
51 03.548 E021 05.437
-------------------------------
Averaged location:
N 51° 06.111`
E 21° 04.788`
± 0.1 m
-------------------------------
Google Maps link:
https://maps.google.com/?q=51.10185,21.07979
-------------------------------
N 51°35.103` | E 21°32.970`
-------------------------------
N 52°07.405` E 21°19.384`
-------------------------------
Coordinates: N53° 55.057 E022° 09.927 ± 0.2 m
-------------------------------
N 53°55.427
E 022°11.025
-------------------------------
N 53° 55.126
E 022° 09.534
-------------------------------
I am here: 52 48.678 N 16 10.362 E
-------------------------------
http://maps.google.com/maps?q=loc:52.81130,16.17270
-------------------------------
galileo://51.424489,21.3114564
Some of them are multilines. People sometimes are copying several lines from different sources, so it is also important to analyze the whole string and just rip coordinates from them.
Hi.
I ran into a little problem yesterday when trying to find the final coordinates of one of my own puzzle caches; Locus or the API don't seem to import the hidden ones. Separate issue.
Anyway, I opened the cache page in Firefox, went to the private page showing all waypoints including the hidden ones, and copied one set of coords to the clipboard.
Then in Locus, I created a new waypoint, and in the Select Location popup, tapped Clipboard. The result was, well, quite wrong.
This is what I pasted, the format Groundspeak uses:
N 53° 23.456 W 113° 23.456 (Numbers randomized a bit.)
It'd be great if this format could be parsed correctly. Thanks.
Hi.
I ran into a little problem yesterday when trying to find the final coordinates of one of my own puzzle caches; Locus or the API don't seem to import the hidden ones. Separate issue.
Anyway, I opened the cache page in Firefox, went to the private page showing all waypoints including the hidden ones, and copied one set of coords to the clipboard.
Then in Locus, I created a new waypoint, and in the Select Location popup, tapped Clipboard. The result was, well, quite wrong.
This is what I pasted, the format Groundspeak uses:
N 53° 23.456 W 113° 23.456 (Numbers randomized a bit.)
It'd be great if this format could be parsed correctly. Thanks.
Hi
I ran into a little problem yesterday when trying to find the final
coordinates of one of my own puzzle caches; Locus or the API don't seem
to import the hidden ones. Separate issue
you as owner of a cache can download with PC and import the gpx file to locus, so you see also all hidden coord and wpt coords. I described it in german thread
http://forum.locusmap.eu/index.php?topic=4364.msg34099#msg34099
parsing problem should be answerd by menion
Hi
I ran into a little problem yesterday when trying to find the final
coordinates of one of my own puzzle caches; Locus or the API don't seem
to import the hidden ones. Separate issue
you as owner of a cache can download with PC and import the gpx file to locus, so you see also all hidden coord and wpt coords. I described it in german thread
http://forum.locusmap.eu/index.php?topic=4364.msg34099#msg34099
parsing problem should be answerd by menion
Good day guys,
I believe that idea here is already implemented for some time and I did not received complains on parsing coordinates for some time. So idea implemented. If there will be obvious problem that Locus Map do not handle some coordinates that it should, please created new "problem" topic here on help desk.
Thank you.
Good day guys,
I believe that idea here is already implemented for some time and I did not received complains on parsing coordinates for some time. So idea implemented. If there will be obvious problem that Locus Map do not handle some coordinates that it should, please created new "problem" topic here on help desk.
Thank you.
Replies have been locked on this page!