This example works:

geopy.point.Point('+037.33270,-122.00530')

This example does not work:

geopy.point.Point('+041.69438,+001.51461')

ValueError: Failed to create Point instance from string: unknown format.

The string in example that is not working is indeed valid GPS, so I believe that this is a bug.

If we could compute the location_postcode table directly from place instead of placex, it wouldn't be necessary anymore to copy over the about 3M postcode helper points into placex. That would be a nice save of space and would allow to get rid of a couple of special cases in the placex triggers.

The main issue is that we don't have country_codes in the place table, so they would need to

We have, for a very long time, had a little bit of logic for managing one small aspect of localization (the order of housenumber and street name in labels) in a file in pelias/api: middleware/localNamingConventions.js.

Since that file was created, we've created an entire package, [pelias/labels](https://github.com