Hi folks. I want to cache results from geocode.earth, since Google's Geocoding API does not permit caching (beyond lat/lon) of any sort. Is there anything in your terms that would disallow this? I cannot find anything, other than potential requirements for attribution when data is taken from one of the many data sources. I work for a company that uses geocoding and autocomplete in support of our product, but it is not a significant feature of the product.
hi @ian-axelrod. Best place for geocode.earth questions is hello@geocode.earth, but our terms do not prohibit caching. benefits of open data :)
Thanks! I figured that was the case. I realize geocode.earth is more appropriate for this next question as well, but I figure I'd ask here anyway just in case anyone else happens to be searching for a similar answer. I'll shoot the question to hello@geocode.earth as well. You would not happen to know if attribution is necessary if I use pelias/geocode.earth as part a system that powers our autocomplete for job search (my employer is themuse.com -- we are looking to move away from Google's geocoder)? Most TOS for major providers imply that this is a requirement, but from what I can tell no website for any of the major providers (mapbox, tomtom, here) actually does this. Rather, they only display attribution for maps.
So either every site I've looked at is violating TOS... which could very well be ... or I am misinterpreting the TOS.
It does seem quite awkward to display attribution for autocomplete functionality. I am not really sure where you would display this in a way that is both prominent but aesthetically acceptable. With maps, you can attribute inside the map itself in one of the corners.
Is there any job or command I should run in order to get it working properly in kubernetes?
there is any script what you have or way for keep updating the docker with all databases (openstreetmap,etc)
Hi. I'm deploying a pelias Docker build on a server. The thing is that ElasticSearch is running on another server. I modified pelias.json to include the correct URL in esclient.hosts and created the pelias index on that server successfully using pelias elastic create. Yet when I run pelias import all I get the following error. Note that the index still exists when I hit {elasticsearch_url}/_cat/indices
ERROR: Elasticsearch index pelias does not exist
You must use the pelias-schema tool (https://github.com/pelias/schema/) to create the index first
For full instructions on setting up Pelias, see http://pelias.io/install.html
/code/pelias/whosonfirst/node_modules/pelias-dbclient/src/configValidation.js:39
throw new Error(`elasticsearch index ${config.schema.indexName} does not exist`);
^
Error: elasticsearch index pelias does not exist
at existsCallback (/code/pelias/whosonfirst/node_modules/pelias-dbclient/src/configValidation.js:39:15)
at respond (/code/pelias/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:368:9)
at /code/pelias/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:396:7
at Timeout.<anonymous> (/code/pelias/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:429:7)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)Any reason why this could be happening? Maybe I'm missing an important step? Thanks a lot :)
repost: Is there any option/feature/API in Pelias which will search bulk places? Such as I am finding for 10-20 places in JSON format. I want to get every first search result of each place keywords. Such as I have a json like this
"places": ["New York", "San Francisco", "Dallas", "Detroit", "Chikago", "Washington", "White House"]. Which will return all the first search result without calling API multiple times.
-gracehttp.log false but i'm getting flag provided but not defined: -gracehttp.log
wof-libpostal-server github says that ☝️
Hi folks, I am currently setting up Pelias for the whole planet and noticed some poor coverage at some countries in the world like China, India or Africa. Source: https://pelias.github.io/scripts-geocoding-coverage
Do you have any suggestions on how I can get results or at least some normalized data to get some data for those cases.
I am trying to map existing address data (street, city, country, coordinates more or less existing) and came across that.
I thought about something like a parsed libpostal + normalized data response.
My goal is to check equality of existing address data.
Do you have any suggestions on how I can get results or at least some normalized data to get some data for those cases.
I am trying to map existing address data (street, city, country, coordinates more or less existing) and came across that.
I thought about something like a parsed libpostal + normalized data response.
My goal is to check equality of existing address data.
@oli1605 unfortunately we haven't updated that page in a couple years. its on our todo list since some details about data coverage could be great to share.
the good news is open data is growing rapidly, and a lot of people are working hard to help it grow, seeking out new data all the time. but you are definitely right there are some areas like China where there is a real lack. if you find anything, we all want to know :)
Hi, I'm setting up pelias on my own server and I want to access the API via nginx.
I want to access it by typing https://someserver.com/pelias/v1/search?text=New York. is this possible?
If I got to https://someserver.com/pelias, the server always redirects me to https://someserver.com/v1
I want to access it by typing https://someserver.com/pelias/v1/search?text=New York. is this possible?
If I got to https://someserver.com/pelias, the server always redirects me to https://someserver.com/v1
one more question..when doing a query on pelias and I use 2 hyphens instead of 1 hyphen I get the exact match...I think this might be a matter of the tokenizer in pelias and ES....how can I modified that in the docker for pelias?
Hello, I have run all planet build of Pelias in Docker container. I have run this script: https://github.com/pelias/docker#quickstart-build-script only replacing "cd projects/portland-metro" by "cd projects/planet". After build completed everything works properly and elastic index is there. But after approximately 3 days, elastic search index is removed, I dont know what is happening I have only remained Pelias running in background. I mean it just suddenly replace content of docker/projects/planet/data/elasticsearch directory with a new indices and indices created by Pelias Docker script are not there. Is this standard behavior and I must do something else to retain indices created by Pelias Docker script? Or am I doing something wrong?
@rwrx probably a "Meow" attack: https://arstechnica.com/information-technology/2020/07/more-than-1000-databases-have-been-nuked-by-mystery-meow-attack/
Hi. I am trying to do the docker build for pelias with elasticsearch v7.10. However it throws an error "Invalid apiVersion "7.10", expected a function or one of _default, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.8, 5.6, 7.7, 7.x". Is there no support for es version>7.7 ?
I am experiencing the same issue as @rwrx with smaller regions (not the full planet). I followed the steps described in https://medium.com/@mohammedayub44/yet-another-awesome-geo-coder-open-sourced-spatial-search-c295970a8226 and I get it up and running. However, after a few days the elasticsearch index is removed and I have to import everything again. Any clues of what I may be missing?
@rwrx @albertors90 indices disappearing suddenly is very concerning. I can't think of anything that would cause it, but Elasticsearch can definitely do weird things. The Elasticsearch logs are confusing and verbose, but there might be something in there that gives hints as to what happened
Hey Pelias Team, I was wondering if there was any interest in kicking off the work on getting Pelias to support better units
pelias/pelias#861 ?
There appears to be a bunch of PRs that are reasonably close but have never been merged for various reasons. If there is anything I can contribute let me know :)
pelias/pelias#861 ?
There appears to be a bunch of PRs that are reasonably close but have never been merged for various reasons. If there is anything I can contribute let me know :)
Hi there! We have set up pelias.json imports to use data from OSM, OA, WOF for our country (Czech republic). We run prepare & import and start the containers, and everything seems OK. But when we run the same search request for an eg. street name using Pelias Compare Tool against official api.geocode.earth vs. our service, we are getting slightly different results (our service return less and also worse results - on the same request). It seems it returns less polylines points than official API. Any idea what could be causing this?
5 replies
https://pelias.github.io/compare/#/v1/search?text=QwERRR%2C+Ahmedabad&debug=1 Why this returns 0 results? It should match on Ahmedabad, India. While this https://pelias.github.io/compare/#/v1/search?text=313+QwERRR%2C+Ahmedabad&debug=1 works.
Hello everyone! Really struggling getting this working on a windows machine; Has anyone managed this that can run through it with me? I've read and tried the comments here but haven't succeeded yet - pelias/docker#124