Closed theoway closed 1 year ago
Hi @theoway, you said you cloned the Portland Metro project and then it returned results in India such as 'Bara Gumbad tomb..'?
@missinglink I used Portland metro project as reference. I then imported my own dataset.
My config is attached in the issue (pelias.json
)
It looks like you're missing the administrative hierarchy information, eg. City, County etc.
In Pelias this information is added for every place by performing a point-in-polygon lookup against the whosonfirst data.
That whosonfirst data is downloaded during the download step and the index is generated in the prepare step.
I suspect that you're importing places for India but the administrative data for India isn't available.
Thanks! That makes sense. As you can see from the config, I'm only using OSM dataset.
So, that means I need to import WOF data as well for India.
Could you please give me notes on how I can download relevant WOF data?
PS: I'm still confused on how Nominatim is able to serve administrative data as well, considering both of my Pelias and Nominatim setup used the exact same OSM dataset, and nothing else.
We don't use the administrative hierarchy from OSM which nominatim does, so they only need one data file, we combine multiple data sources, and use whosonfirst for the administrative hierarchy.
You don't strictly need to 'import' whosonfirst into Pelias, doing so will make each city, state etc searchable by adding a document to the elasticsearch index.
But you will certainly need to download
and prepare
the correct whosonfirst data so that when you import OSM each record is assigned administrative information.
@missinglink Thanks so much! This has helped a lot.
Describe the bug Responses of
search
&autocomplete
send incompletelabels
that are same asname
, that is, only consist of place name and not the address(region, state, country, pincode etc) suffixed to them. The endpoints also throw warning:"warnings":["performance optimization: excluding 'address' layer"]
Even after disabling this optimization inpelias.json
, this warning still comes.I am only using OSM data, imported as an
osm.pbf
file. It is a merged dataset made from merging two differentosm.pbf
files. My file is not corrupt as I have tested the same file with Nominatim, and it returned completed addresses with each location.Is this happening because I have not imported
WOF
data of the same region?Steps to Reproduce Steps to reproduce the behavior:
label
andname
for each location is same:Expected behavior
label
should have more details than just storing only thename
See the response from Mapzen's Pelias live site:
Environment (please complete the following information): Docker
Pastebin/Screenshots pelias.json config that I'm using:
Additional context My only guess is that either it is a bug or I also need to import WOF data.