geocoding.query.parsed_text
field of the response seems to always assume admin area is the last word of the query. https://maps.earth/pelias/v1/autocomplete?text=seattle%20target
focus.point
bias strength. For this project I want to be able to bias very strongly if the user is zoomed in to like z15 or something and bias a lot less if they're out at z8. There was a way to do that in Photon and I'm hoping something like that could be implemented for Pelias. I don't mind being the one to go do it but I would like guidance on where the relevant parts of the codebase are if possible :)
placeholder
perhaps? Looking specifically for whether parts of the query may make sense as coarse locations.
Hi all,
I've a question regarding the answers of a simple geocoding search.
When I search this : "12 Bd Richard Lenoir, Paris", it finds the location.
When I search this : "12 Bd Lenoir, Paris", it finds the location.
But when I search this : "12 Bd R. Lenoir, Paris", it does not find the location.
Same for this searches :
"12 avenue philippe auguste, Paris" works
"12 avenue ph. auguste, Paris" doesn't find anything...
Is there a way to tweak Elasticsearch to make the searches work when one of the word is not complete ?
Thanks in advance.
2022-10-23T22:29:55.234Z - error: [dbclient-whosonfirst] esclient error message=Request Timeout after 120000ms, status=408, displayName=RequestTimeout, stack=Error: Request Timeout after 120000ms
at /home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:397:9
at Timeout.<anonymous> (/home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:429:7)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
2022-10-23T22:29:55.238Z - error: [dbclient-whosonfirst] invalid resp from es bulk index operation
2022-10-23T22:29:55.239Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:56.091Z - error: [dbclient-whosonfirst] esclient error message=Request Timeout after 120000ms, status=408, displayName=RequestTimeout, stack=Error: Request Timeout after 120000ms
at /home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:397:9
at Timeout.<anonymous> (/home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:429:7)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
2022-10-23T22:29:56.091Z - error: [dbclient-whosonfirst] invalid resp from es bulk index operation
2022-10-23T22:29:56.091Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:56.117Z - error: [dbclient-whosonfirst] esclient error message=Request Timeout after 120000ms, status=408, displayName=RequestTimeout, stack=Error: Request Timeout after 120000ms
at /home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:397:9
at Timeout.<anonymous> (/home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:429:7)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
2022-10-23T22:29:56.117Z - error: [dbclient-whosonfirst] invalid resp from es bulk index operation
2022-10-23T22:29:56.117Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:56.143Z - error: [dbclient-whosonfirst] esclient error message=Request Timeout after 120000ms, status=408, displayName=RequestTimeout, stack=Error: Request Timeout after 120000ms
at /home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:397:9
at Timeout.<anonymous> (/home/user/Softwares/whosonfirst/node_modules/elasticsearch/src/lib/transport.js:429:7)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
2022-10-23T22:29:56.143Z - error: [dbclient-whosonfirst] invalid resp from es bulk index operation
2022-10-23T22:29:56.143Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:56.567Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:56.568Z - error: [dbclient-whosonfirst] transaction error invalid bulk payload length. Payload received: []
2022-10-23T22:29:56.584Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:56.584Z - error: [dbclient-whosonfirst] transaction error invalid bulk payload length. Payload received: []
2022-10-23T22:29:59.559Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:59.559Z - error: [dbclient-whosonfirst] transaction error invalid bulk payload length. Payload received: []
2022-10-23T22:29:59.560Z - info: [dbclient-whosonfirst] retrying batch [500]
2022-10-23T22:29:59.567Z - error: [dbclient-whosonfirst] transaction error invalid bulk payload length. Payload received: []
The above was the issue that occured for me
openstreetmap
and layer is postalcode
. Is OpenStreetMap used at all for admin lookup? That feature seemed on hold for now: pelias/pelias#389
Hello, on a fresh planet index build I am getting 53 regressions but I am able to replicate these 'regressions' on pelias.github.io.
Aggregate test results
Pass: 608
Improvements: 18
Expected Failures: 109
Placeholders: 0
Regressions: 53
Total tests: 788
Took 47101ms
Test success rate 93.27%
FATAL ERROR: 53 regression(s) detected.
ERROR: 1
Here is one example regressions
✘ regression [7] "/v1/search?sources=wof&text=Città del Vaticano, Vatican": score 3 out of 6
diff:
name
expected: Vatican City
actual: Città del Vaticano
locality
expected: Vatican City
actual: Città del Vaticano
country
expected: Vatican City
actual: Vatican
But comparing this output to https://pelias.github.io/compare/#/v1/search?sources=wof&text=Citt%C3%A0+del+Vaticano%2C+Vatican I see that the same 'regression' exists
"properties": {
"id": "101914185",
"gid": "whosonfirst:locality:101914185",
"layer": "locality",
"source": "whosonfirst",
"source_id": "101914185",
"country_code": "VA",
---> "name": "Città del Vaticano",
"confidence": 0.1,
"match_type": "unknown",
"accuracy": "centroid",
---> "country": "Vatican",
"country_gid": "whosonfirst:country:85632187",
"country_a": "VAT",
"region": "Vatican",
"region_gid": "whosonfirst:region:85688891",
"region_a": "VA",
---> "locality": "Città del Vaticano",
"locality_gid": "whosonfirst:locality:101914185",
"continent": "Europe",
"continent_gid": "whosonfirst:continent:102191581",
"label": "Città del Vaticano, VA, Vatican"
Is this something I should crate a bug report for?
Hi there, i installed Pelias Planet build on my server with prepare extracts from Geoearth rather than preparing myself but i got some errors when i ran test script. What can be it reason? I shared test result.
Pass: 503
Improvements: 14
Expected Failures: 101
Placeholders: 0
Regressions: 138
Total tests: 756
Took 19113ms
Test success rate 81.75%