Stephen Hess
6f4ec874fe
added special override condition for libpostal query/housenumber mixup
8 years ago
Stephen Hess
876782ed3a
enabled all scores and filters
...
adjusted tests to account for new querying strategies, renamed all existing test fixture files to `*_original`. pointed query module to a PR for testing.
8 years ago
Stephen Hess
484af8c044
changed from `text_parser` to `text_parser_addressit`
...
this ensures that `clean.parsed_text` is correctly converted to query as expected
8 years ago
Stephen Hess
e01ef7ac4d
copied the existing search query logic back in
8 years ago
Stephen Hess
85dab16869
refactored search sanitiser tests
...
the tests removed were testing far more than was appropriate since the functionality of the individual sanitisers is tested elsewhere. in this case, the test has been reduced to just testing that all the sanitisers were actually called.
8 years ago
Stephen Hess
01d0338486
added text_parser that uses addressit format for autocomplete
...
rather than wholesale converting to libpostal in one release, the decision was made to only use libpostal for /search and not /autocomplete. Until such time that libpostal can be used for parsing autocomplete queries, text_parser_autocomplete.js will contain the converter between addressit and internal parsing format.
8 years ago
Stephen Hess
0aebf81ace
support new querying model
...
add support for FallbackQuery and GeodisambiguationQuery from the pelias-query module. GeodisambiguationQuery is used when the text-analyzer returns a single administrative area field. FallbackQuery is used otherwise.
8 years ago
Stephen Hess
5821ae6e81
libpostal changes
...
- updated for libpostal interface
- added tests for text_parser
8 years ago
Stephen Hess
0166940e1a
added debug
8 years ago
Stephen Hess
ab9b1dbafa
commented out deprecated AddressIt code
8 years ago
Julian Simioni
c5e5bbcf56
Add boundary.country filter to /v1/autocomplete
8 years ago
Diana Shkolnikov
127137f427
Add category filter to reverse query
8 years ago
Diana Shkolnikov
1df1a0765c
Add categories filter to search query
8 years ago
Peter Johnson
7f18561595
remove focus.viewport API
8 years ago
Julian Simioni
aa7942cbb9
Set up layer filtering for autocomplete and reverse
...
This was missed by me when working on https://github.com/pelias/api/pull/580 , but caught by the acceptance tests!
Unfortunately it was caught after going to production.
8 years ago
Alec Vulfson
31adf09870
Using new layers view to filter layers
8 years ago
Peter Johnson
5964e57faa
change ngram analyzer used in /search to peliasQueryFullToken from peliasIndexOneEdgeGram. this will have a positive effect on performance due to less tokens being produced
8 years ago
Peter Johnson
d3cd14e304
disable focus for single token queries, use constant_score for ngrams matching
8 years ago
Peter Johnson
52c35cb37d
allow single non-numeric chars, change boost_mode to 'replace' for function_score queries
8 years ago
missinglink
cb35f37312
focus minimum set to 0km instead of 1km
9 years ago
Julian Simioni
c9d87f7b0c
Add a separate default distance for coarse reverse
9 years ago
Julian Simioni
4acbc2a001
Change default reverse radius to 1km
...
Its a little more work to support different unit types, 1km is still
fine.
9 years ago
Julian Simioni
d7eacaf59e
Fix mistaken order of parameters
...
peliasAdmin was supposed to be a parameter to the multi match view, but
instead it was being sent to the score view and ignored.
Thanks to @trescube for catching this.
9 years ago
Peter Johnson
dd5215cbae
upgrade to ES2+
9 years ago
Julian Simioni
373a08e79b
Set all admin boosts to 1
...
They seem to interfere with the new multi_match query. More tweaking in
the future is definitely warranted.
9 years ago
Julian Simioni
ab19a12e1c
Use multi_match query for admin fields
9 years ago
missinglink
979aab1ac3
ensure that problematic single grams are removed from the query
9 years ago
missinglink
ee73774c89
add tokenizer, refactor how we determine if a token is 'complete' or 'incomplete'
9 years ago
missinglink
e093a09a8d
remove search related improvements from this PR
9 years ago
missinglink
0c67347c27
enable borough for search
9 years ago
missinglink
9dbed08884
remove duplicate entry for borough
9 years ago
missinglink
da4c666538
reduce admin:borough:boost from 800->600
9 years ago
missinglink
2398f05f8d
fix borough matching for both autocomplete and search endpoints
9 years ago
missinglink
b862fc8833
refactor pop_subquery to be config driven
9 years ago
missinglink
ca0c51b0fd
don't strip single digits from query
9 years ago
missinglink
01a3233a7b
add a view to boost exact matches
9 years ago
Julian Simioni
f8af354e71
Base admin fields on placetypes
9 years ago
Julian Simioni
028ab1d889
Add search config settings for borough
9 years ago
missinglink
25ab63c3b3
change search analyzer to be more similar to what we had before the autocomplete_refactor milestone
9 years ago
missinglink
e40c9ef326
increase focus weight from 10->40 and simplify population/popularity subview
9 years ago
missinglink
3a789b4a93
increase autocomplete 'phrase:slop' setting from 2->3
9 years ago
Peter Johnson
aa3e764e49
update analyzers to work with https://github.com/pelias/schema/pull/109
9 years ago
Peter Johnson
63301afeac
wow this is easy to get wrong, added a unit test
9 years ago
Peter Johnson
7d71e32104
bugfix: enable support for ?sources= filtering on /reverse
9 years ago
Peter Johnson
0abda099a6
bugfixes and more tests
9 years ago
Diana Shkolnikov
0917a84988
Update property names in query defaults
9 years ago
Diana Shkolnikov
f3ba492e05
Remove all usage of alpha3/admin0/admin1, update query building to reflect new names in pelias-query
9 years ago
missinglink
67449dcae0
Tweak weights for focus
9 years ago
missinglink
ce292baeaf
fixes for focus.point to work with wof integration
9 years ago
Julian Simioni
ef78b2e0fd
Filter source and layer by new fields
...
This is functionally the same code as before, except that it uses the
new source and layer mapping.
9 years ago