-
Updated
Oct 13, 2020 - Go
geocoding
Here are 518 public repositories matching this topic...
-
Updated
Oct 7, 2020 - Ruby
-
Updated
Oct 14, 2020 - JavaScript
Nominatim sometimes presents results that are not directly related to an OSM object. These are:
- postcode (country + postcode + a parent OSM object)
- interpolations (OSM way + a housenumber)
- Tiger house numbers (OSM way + Tiger interpolations + housenumber)
- auxillary data (Currently unused)
These objects don't have good details pages at the moment. They usually simply redirect to th
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 14, 2020 - TypeScript
-
Updated
Sep 22, 2020 - TypeScript
-
Updated
Aug 5, 2020 - Python
-
Updated
Oct 14, 2020 - Go
-
Updated
Feb 29, 2020 - C#
-
Updated
Oct 10, 2020 - C#
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 8, 2020 - Python
-
Updated
Oct 1, 2020 - JavaScript
-
Updated
Nov 12, 2019 - Objective-C
-
Updated
Sep 14, 2020 - Java
-
Updated
Jul 17, 2016 - JavaScript
-
Updated
Sep 10, 2020 - JavaScript
-
Updated
Jun 10, 2020 - C#
-
Updated
Oct 14, 2020 - Rust
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
-
Updated
Sep 16, 2020 - JavaScript
-
Updated
Aug 24, 2019 - Objective-C
-
Updated
Jun 5, 2020 - Python
-
Updated
Aug 7, 2020 - JavaScript
Improve this page
Add a description, image, and links to the geocoding topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the geocoding topic, visit your repo's landing page and select "manage topics."
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.