Some locode coordinates in invalid format

[alexandrulesi]

Example Chuchungsa with coordinates 26.9826N 88.9391E, that does not match expected DDMM[N/S] DDDMM[W/E] pattern

[sabas]

That's in the original release, somehow invalid data was published.. I notify the secretariat also on this issue.

[sabas]

@alexandrulesi the data is in that format on the specific request of Buthan representative as I learned from the call...
We'd wish to move to decimal coordinates but it's a long way to do it officially.

Btw you can also use @cristan 's https://github.com/cristan/improved-un-locodes

[cristan]

Right now, my project just has way more and much more accurate coordinates: they are still in 2 different formats.

But that's quite easy to remedy on my side. If you want that, create an issue on my project. What would you like? A new column with all in the un/locode format? A new column with all entries in the decimal format? Something else?

[alexandrulesi]

Thanks folks! I'll create an issue on the other repo then

[cristan]

Update: my project has been updated now :) The Coordinates column now has UN/LOCODE style degrees and a CoordinatesDecimal column has been added for good measure.