-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[discuss] import OSM cities/regions when they are a 'node' or 'way' #71
Comments
Should get fixed by new admin lookup |
This node does not seem to be imported at all any more. Is this ticket still relevant? http://pelias.github.io/compare/#/v1/place%3Fids=openstreetmap:address:node:1700534808 |
This ticket is super old (2 July 2015). It came about as Munich/München was not searchable at that time, now you can find it but with encoding issues in the admin metadata that @dianashk pointed out will be solved soon. The OSM entity linked above never got imported because (I think) it's not in the features whitelist, let's track this issue as a discussion about importing those entities or using their metadata. I'll update the ticket description and the labels. |
Is it possible to import the cities that are nodes? e.g. Importing Denmark's data, Copenhagen isn't found in OSM as it's a node. https://www.openstreetmap.org/node/13707878 Also applies to relations, according #81 it is possible, but I can't find documentation on it, nor can I find this node in pelias: https://www.openstreetmap.org/relation/2192363 |
Parallel imports
Openstreetmap contains entities marked as
place: city
which are not imported in to Pelias because that tag is not listed in the features whitelist.The following
osm:node
for Munich contains loads of great meta data. such as population info and translations.Would it be worth importing these entities or linking them to the relevant Geonames or WOF records?
http://www.openstreetmap.org/node/1700534808
note: this description was updated and so the first 2 comments make less sense in context.
The text was updated successfully, but these errors were encountered: