"places": ["New York", "San Francisco", "Dallas", "Detroit", "Chikago", "Washington", "White House"]. Which will return all the first search result without calling API multiple times.
Hello all,
I'm afraid my Pelias installation (AWS EC2, m5a.2xlarge, Amazon Linux) using the docker setup (the north america project) is running into some issues.
Forward geocoding works fine when querying cities, states, countries and neighborhoods (generally this means that libpostal is the parser). However, when I include streets, housenumbers, and subjects I receive the error:"[query_shard_exception] [match_phrase] analyzer [peliasQuery] not found, with { index_uuid=\"D1zpHeeARdyoDe_CzAO6uQ\" & index=\"pelias\" }"
When I try to access the analyzer through Elasticsearch, it cannot be found.
The other issue I am having is with reverse geocoding. Take this query that is directly from the doc:/v1/reverse?point.lat=48.858268&point.lon=2.294471
When I try to GET, I recieve:"[query_shard_exception] failed to find geo_point field [center_point], with { index_uuid=\"D1zpHeeARdyoDe_CzAO6uQ\" & index=\"pelias\" }"
When I look at my mapping in Elasticsearch, the center_point field is defined as follows:"properties": {
"lat": { "type": "float" },
"lon": { "type": "float" }
}
Any idea what might have gone wrong in my setup, and how I might be able to fix it?
Thanks.
Creating extract at /data/placeholder/wof.extract
converting /data/openstreetmap/centralohio.osm.pbf to /data/polylines/extract.0sv
/code/pelias/placeholder/node_modules/pelias-blacklist-stream/parser.js:11
throw new Error( 'file not found' );
^
Error: file not found
at load (/code/pelias/placeholder/node_modules/pelias-blacklist-stream/parser.js:11:11)
at /code/pelias/placeholder/node_modules/pelias-blacklist-stream/loader.js:26:48
at Array.map (<anonymous>)
at loader (/code/pelias/placeholder/node_modules/pelias-blacklist-stream/loader.js:26:31)
at Object.<anonymous> (/code/pelias/placeholder/prototype/wof.js:6:60)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Module.require (internal/modules/cjs/loader.js:848:19)
wrote polylines extract
-rw-r--r--. 1 1001 1001 1.7M Oct 19 18:14 /data/polylines/extract.0sv
/code/pelias/whosonfirst/node_modules/pelias-blacklist-stream/parser.js:11
throw new Error( 'file not found' );
^
Error: file not found
at load (/code/pelias/whosonfirst/node_modules/pelias-blacklist-stream/parser.js:11:11)
at /code/pelias/whosonfirst/node_modules/pelias-blacklist-stream/loader.js:26:48
at Array.map (<anonymous>)
at loader (/code/pelias/whosonfirst/node_modules/pelias-blacklist-stream/loader.js:26:31)
at blacklistStream (/code/pelias/whosonfirst/node_modules/pelias-blacklist-stream/index.js:22:15)
at fullImport (/code/pelias/whosonfirst/src/importStream.js:16:11)
at /code/pelias/whosonfirst/import.js:36:3
at getDBList (/code/pelias/whosonfirst/src/bundleList.js:56:3)
at Object.getList [as generateBundleList] (/code/pelias/whosonfirst/src/bundleList.js:61:12)
at Object.<anonymous> (/code/pelias/whosonfirst/import.js:15:9)
Hi. Out of nowhere I started to receive the following error on my Pelias planet build when running pelias elastic stats:
{
"error" : {
"root_cause" : [
{
"type" : "index_not_found_exception",
"reason" : "no such index [pelias]",
"resource.type" : "index_or_alias",
"resource.id" : "pelias",
"index_uuid" : "_na_",
"index" : "pelias"
}
],
"type" : "index_not_found_exception",
"reason" : "no such index [pelias]",
"resource.type" : "index_or_alias",
"resource.id" : "pelias",
"index_uuid" : "_na_",
"index" : "pelias"
},
"status" : 404
}I know that dropping and creating the index again (imports included) should solve the problem. But is there a reason why this happened out of nowhere, or any way to prevent it from happening again? Thanks!
Hi @orangejulius thanks for the help. I will add security to the server so that not everyone can have access. For the time being I deleted the index and re-created it, and ran import again. After that I got the following error
{
"error" : {
"root_cause" : [
{
"type" : "illegal_argument_exception",
"reason" : "Fielddata is disabled on text fields by default. Set fielddata=true on [source] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead."
}
],
"type" : "search_phase_execution_exception",
"reason" : "all shards failed",
"phase" : "query",
"grouped" : true,
"failed_shards" : [
{
"shard" : 0,
"index" : "pelias",
"node" : "gFoLazB0SaSeC5KTRqOCpA",
"reason" : {
"type" : "illegal_argument_exception",
"reason" : "Fielddata is disabled on text fields by default. Set fielddata=true on [source] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead."
}
}
],
"caused_by" : {
"type" : "illegal_argument_exception",
"reason" : "Fielddata is disabled on text fields by default. Set fielddata=true on [source] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.",
"caused_by" : {
"type" : "illegal_argument_exception",
"reason" : "Fielddata is disabled on text fields by default. Set fielddata=true on [source] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead."
}
}
},
"status" : 400
}Any ideas what might have caused it? I imported my own csvs alongside all OpenAdresses, OpenStreetMap, etc. data
Hello. I am trying to install the Pelias portland-metro example on CentOS. I am seeing the following error when running pelias elastic start:
Caused by: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data"
I have seen multiple issues about running as root may cause this. So I created a separate user but am seeing the same issues. I made sure to chown the DATA_DIR to the pelias user. Am I missing something? It may be worth noting that I have successfully ran this demo locally in Windows WSL shell.
1 reply
Hi, I have a working setup of pelias and can query the pelias for addresses. which responds correctly. for all. layers except the postalcode..
working request example -
https://mydomain.com/pelias/api/v1/search?text=2429&layers=address&boundary.country=AUSbut when i request with layer postalcode like below -
https://mydomain.com/pelias/api/v1/search?text=2429&layers=postalcode&boundary.country=AUSthen it responds with below error -
"errors": [
"'postalcode' is an invalid layers parameter. Valid options: coarse,address,venue,street,locality,neighbourhood,county,localadmin,region,macrocounty,country,macroregion,borough,macrohood,marinearea,disputed,dependency,empire,continent,ocean"
]I did imported the postalcodes as well when i have downloaded the wof data for postalcodes..
does anyone have any idea on why i am facing this issue?
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 :)
"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
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 :)
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
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 :)
