Originally Posted by nohal
I can hardly imagine having a more universal parser
Never underestimate the imagination of Hydrographic Authorities...
I posted in the 523 Beta thread an example of interpretation of a standard Admiralty coordinate format, the most widely used. Generally, the new parser has problems with unusual (for programmers) separator sequences. Forums
- Post 416763">Here you can find some other strange examples. With all respect to various National HOs, Admiralty is by far the most important, and even if only one extended format should be allowed I'd pick this one.
Completely dropping the minutes would not be so dangerous, because this is immediately noticeable, but taking minute fractions for seconds can well go unnoticed, and 1/2 a mile off can get you well into trouble.
I very often annote the charts
with new features and dangers. For a 4-cornered area editing this by hand means ca. 40 additional key-mouse strokes. For bigger things, like 30-odd positions area boundary or a set of TSS lanes or 80 postions of measurement buoys, I use an OpenOffice spreadsheet macro to convert the coordinate format and a Python script to generate GPX, but this is too heavy for a simple feature, so I use then my 136 parser...
So the ability to paste directy from UKHO does help a lot.