Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Search: confidence often just 0.6 although more accurate data resides in elasticsearch #4

Open
dr0i opened this issue Jun 4, 2019 · 1 comment
Open

Search: confidence often just 0.6 although more accurate data resides in elasticsearch #4

dr0i opened this issue Jun 4, 2019 · 1 comment
Assignees
@dr0i

Comments

@dr0i
Copy link
Member

dr0i commented Jun 4, 2019

Following hbz/lobid-organisations#419: why there are 2k inaccurate lookups.

Opened an issue at pelias/api#1309.
@dr0i dr0i self-assigned this Jun 4, 2019
dr0i added a commit that referenced this issue Jun 25, 2019
@dr0i
Tweak pelias.json
1f42138 
See #4.
@dr0i dr0i mentioned this issue Jun 25, 2019
Merged
@dr0i
Copy link
Member Author

dr0i commented Jun 25, 2019 •
edited
Loading

While curl -G 0.0.0.0:4000/v1/search --data-urlencode "layers=venue,street,address" --data-urlencode "sources=osm" --data-urlencode "text=Zentralplatz 2, 56068 Koblenz, DE" is since pelias/api#1309 of confidence 1, a change in the house number (from "2" to "1") yields 0.6. There is a obviosuly a problem with interpolation (pip-service).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dr0i dr0i

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dr0i