Comments (5)
Since we are now fully converted to suggest_plus_mget
approach, we could do something fancy with the tokens after the comma.
When using /search
, this could be pretty easy, simply querying against the admin fields with the remaining text and boosting the results accordingly.
Doing it in /suggest
is another story completely...
I'm planning on allowing the suggester FST to be filtered by alpha3, which could at very least support querying alpha3 values after the comma, still that's not very user-friendly.
In the future we could also have context suggester
entries for common abbreviations.
ref: pelias/schema#25
from api.
How about we use the context suggested and instead of the category be one
of the datasets, could we have dataset and alpha3? For ex, geoname:US
, locality:IT
And in the query you could maybe use wildcard character *
to match on
things??
from api.
Should be closed in light of newer issues.
from api.
We could close this in favour of:
That ticket only covers one of the issues and only partially, plus it doesn't have as clear a description as this.
from api.
this issue has been resolved
from api.
Related Issues (20)
- duplicate invalid param 'text' warning for /v1/search HOT 4
- Get population value from reverse geocoding result HOT 1
- Region not returned in results for Algeria (DZ) if using multiple layers HOT 2
- Search for federal states of Germany in German language HOT 9
- Pelias: Updating the street data
- Pelias: Updating the street data
- Pelias: Updating the street data HOT 7
- Indexing and normalisation of Cyrillic characters HOT 2
- Curious behavior of Pelias with house number suffixes in answer HOT 3
- fix: test case fails for diffPlaces HOT 3
- Query filters for parent data fields HOT 3
- Geoname features not returned when queried together with osm source. HOT 2
- Increase MAX_SIZE limit for Pelias API HOT 1
- Layers and sources ignored results in ignored sources only
- T
- Can't find result for "97200", neither in local nor geocode.earth
- libpostal label 'state'
- TypeError: Object.values(...).flat is not a function
- API - missing Elasticsearch plain text authentication HOT 3
- Missing search result despite record being available in Elasticsearch HOT 19
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from api.