Is there any information available regarding which data from which date is exactly used currently for the Geocoding API?
E.g.
WOF bundles (https://dist.whosonfirst.org/bundles/) or SQL databases (https://dist.whosonfirst.org/sqlite/)?
Date of the OSM dump used for adresses and streets layers
etc.
No, it’s not. It’s roughly 1.5 months old. We decided to update every 2 months.
Why is it interesting if WOF bundles or DB? Is there any difference in coverage or update cycles? It’s DB btw.
No, it’s not. It’s roughly 1.5 months old. We decided to update every 2 months.
Thanks for your reply. Maybe it would be possible to set up a changelog for the geocoder, which shows when the data have been updated, something like https://openmaptiles.com/changelog/?
Why is it interesting if WOF bundles or DB? Is there any difference in coverage or update cycles?
Yep, DB are updated more frequently. There are no bundle updates in 2019, see: dist.whosonfirst.org
Would it be possible that you share your Pelias configuration (import settings)? I’m currently playing around with Pelias and your API Playgound is very useful to try some things out with different settings to understand what is going on. I’ve got some unexpected reverse geocoding results and curently investigating if this is a data issue or related to the configuration/code.
BTW, could you please take a short look at Reverse Geocode API playgound - street layer not selectable, I guess this would be easy to fix.
BTW, could you please take a short look at Reverse Geocode API playgound - street layer not selectable, I guess this would be easy to fix.
Ping @amandus or @amoncaldas for this.
Maybe it would be possible to set up a changelog for the geocoder, which shows when the data have been updated, something like https://openmaptiles.com/changelog/?
Realistically I wouldn’t want to do this. Geocoding is veeery much a complimentary product for us and this would add another small maintenance document. Yes, tiny, but want to avoid this in any case.
Would it be possible that you share your Pelias configuration (import settings)?
Sure. We’re not using Docker. Also not yet ES 5, though I gotta do the migration soon it seems…
{
"logger": {
"level": "info",
"timestamp": true,
"colorize": true
},
"esclient": {
"hosts": [
{
"host": "192.168.2.71",
"port": 9200
},
{
"host": "192.168.2.72",
"port": 9200
},
{
"host": "192.168.2.73",
"port": 9200
},
{
"host": "192.168.2.74",
"port": 9200
}
]
},
"elasticsearch": {
"settings": {
"index": {
"number_of_replicas": "0",
"number_of_shards": "24",
"refresh_interval": "1m"
}
}
},
"schema": {
"indexName": "pelias_20190626"
},
"interpolation": {
"client": {
"adapter": "http",
"host": "http://localhost:3100"
}
},
"imports": {
"adminLookup": {
"enabled": true,
"maxConcurrentRequests": 1000
},
"geonames": {
"datapath": "/srv/pelias_importer_ext/data/gn",
"countryCode": "ALL"
},
"openaddresses": {
"datapath": "/srv/pelias_importer_ext/data/oa",
"files": []
},
"openstreetmap": {
"download": [
{
"sourceURL": "https://planet.openstreetmap.org/pbf/planet-latest.osm.pbf"
}
],
"datapath": "/srv/pelias_importer_ext/data/osm",
"leveldbpath": "/srv/pelias_importer_ext/tmp",
"import": [
{
"filename": "planet-latest.osm.pbf"
}
]
},
"whosonfirst": {
"datapath": "/srv/pelias_importer_ext/data/wof",
"importVenues": false,
"importPostalcodes": true,
"sqlite": true
},
"polyline": {
"datapath": "/srv/pelias_importer_ext/data/polylines",
"files": [
"road_network.polylines"
]
}
}
}
Cool, thanks a lot @nils !