Deterministic locode coordinate format

[alexandrulesi]

Hi folks,

following up on the suggestion on this issue on the datahub.io locodes repo I'm opening this ticket here.

@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?

We're using the above mentioned repo to source locodes and are facing the issue that the coordinates come in different formats and not just the one mentioned in their documentation. We'd ideally like to use a dataset where all entries are in the same format or at least the formats are distinguished.

So yes your suggestion sounds good. What would be even cooler, though optional, is if you added a conversion step on your side so that both new columns are fully populated. Then we wouldn't need to do conversion on our end every time we pull the dataset.

Thanks for the offer :)

[cristan]

Created the CoordinatesDecimal column. I'll think about what to do with the UN/LOCODE format: make all coordinates in the Coordinates column the UN/LOCODE degrees format, or add another column dedicated for this.

[cristan]

Done. The Coordinates column now everywhere has the UN/LOCODE flavour of the degrees notation and there's now also a CoordinatesDecimal column with decimal coordinates.

[alexandrulesi]

Thanks @cristan!