As an example, if I wanted to find all points of interest in a specific area, I could do that with overpassAPI. Does this have the same functionality? And if not, curious as to whether it is due to a clear design choice or just a resource limitation. I see it does have the concept of places.
It describes the geocoder and reverse geocoder functionality.
Nice, didnt see that page although I did scour through the different repositories.
I guess I needed more clarification on the 'venues' portion.
A good example would be if I wanted to make a request targetting particularly OSM (but others as well if they have it) data on point of interest.
Something like 'all entertainment points of interest in a 50 mile radius of this point'
I can do that with the overpassAPI, I can understand the structure of the data and OSM has a whole wiki on POI.
From what ive seen you cannot do that with pelias.
However the reason I wanted to make sure is because the system in place could easily support this functionality given a bit of legwork, and this seems like a very well organized project!
Like I cant do 'waterfountains near london bridge' with the geocoder I dont think. Just wanted to confirm
Hello! With pelias-docker I would like to use my own openstreetmap pbf file. At the moment I just configured as import.openstreetmap.download.sourceURL a not existing URL. Then I copy my own pbf file into the directory before doing the pelias prepare all. While this works, it produces an error. I'm wondering if there is a better way of handling this situation?
I have noticed that when trying to forward geocode an address like this 10955 Old River RD , Komoka, ON, then pelias is not able to find/match the zipcode to the address.
Could someone advise me how I could include the candaian postal code geocode data from here: https://www.serviceobjects.com/blog/unique-us-canadian-zip-code-files-available-download/ into pelias ?
Could someone advise me how I could include the candaian postal code geocode data from here: https://www.serviceobjects.com/blog/unique-us-canadian-zip-code-files-available-download/ into pelias ?
and my total disk usage is staying more or less constant at around 163GB
not seeing any build output either
the odd thing is that my cpu is showing very low utilization.. but the script is still in a Interruptible Sleep state
I've got a North America build for Pelias and we've noticed some issues related to the source data (fields duplicated to incorrect fields, missing fields, etc.) and I was wondering if there was a way to identify and clean up such occurrences. Also, is there a preferred way to update the data? I can't seem to find any documentation addressing either of these questions.
@jcushner: Some are there and some are not. Missing zip codes are definitely one of the most common issues I'm seeing though.
I am also interested in a method to update the data
Yeah, I know I can certainly do a full re-download, then wipe the data from elasticsearch and re-import, but doing so would result in down-time, which is obviously problematic for larger datasets. I could also just try re-importing, but I am not certain if that will result in duplicated records.
Yeah, scrolling through the history here, it seems to have come up a few times. I'm not seeing any answers though. Definitely should be something mentioned in the docs, I think
Hello, I currently see pip-service loading only a small portion of features:
Is there any idea how to force loading more files?
"openstreetmap": {
"leveldbpath": "/tmp",
"datapath": "/share/data/osm",
"importVenues": true,
"import": [
{"filename": "*"}
]
"leveldbpath": "/tmp",
"datapath": "/share/data/osm",
"importVenues": true,
"import": [
{"filename": "*"}
]
this doesn't seem to work. i get an error that it "failed to stat pbf file: /share/data/osm/*
how do i use wildcards..
like if I only wanted a*, etc..
I see this param but doesn't make sense to me on how to use it imports.openstreetmap.import[0].filename
@jcushner: We have found that a large part of our data quality issues (particularly with autocomplete) are from the openaddresses us/fl/_loveland dataset. Have you noticed a similar pattern?
This dataset seems to be missing ZIP codes and has a very large number of occurrences where the house number and street name are the same number. Some spot checking finds that these are bogus addresses.
@AIDARXAN: I have not tried it myself, but I imagine you could remove the unwanted bits from docker-compose.yml
1 reply
help needed: I'm trying to download the global openaddresses dataset from AWS and if I use the docker file I get a 403 error, the same if I use wget. So I want to use S3, to avoid costs for OA but the aws-cli requires a bucket id and a key. What are they? There is not a single sample online I can refer to...
aws s3api get-object s3://v2.openaddresses.io/batch-prod/collection-global.zip --request-payer requester --bucket ?????? --key ?????
what do I need to put in the ???? part????
need is to put the 18 GB zip file on the Ubuntu server so that the Pelias docker stack can access it