[PATCH] Improving matching of ISO 6709 GPS format

Miika Turkia miika.turkia at gmail.com
Mon Jan 13 01:01:22 UTC 2014

Sounds good to me, provided there is no issue with how this is represented
in different locales. There should also be an example of each supported GPS
format before the regexp as a comment. It would help to see what one is
trying to match...


On Mon, Jan 13, 2014 at 10:40 AM, Tim Wootton <tim at tee-jay.demon.co.uk>wrote:

>  On 13/01/14 08:03, Tim Wootton wrote:
> On 13/01/14 07:37, Miika Turkia wrote:
>  Google format seems to have comma as separator: 31.203405,-67.51465
>  However, how does the decimal point-comma differences between different
> locales affect this, or does it? We could, of course, check if we have odd
> number of commas in the coordinates to make sure the comma we are looking
> for is separator between long and lat, not a decimal point.
> Good point (excuse the pun), this is trickier than it seems!
> What if the location is exactly on a line with only 0s after the dp do
> they and the dp still get shown? if not that would mess with the odd/even
> count.
> From what I can see, looks like they're still shown, so that'd work.
> So that would be:
>     if 1st non-whitespace is a digit and number of commas is even then
> treat it as ISO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20140113/497fab46/attachment.html>

More information about the subsurface mailing list