mirror of https://github.com/pelias/api.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
7a6ac8541b
__BETA__
add-params-to-parser-logs
add-status-code-logging
address_search_using_ids
autocomplete_boost_exact_matches
category
cb_sorting
configurable-boosts
county-fallback
coverage-test
cutoff_frequency
dedupe
dedupe-failing-test-case
dedupe_improved_parent_matching
default-500-err
dep-check
disable-dfs_query_then_fetch
es6-include
exact_matches_muted
experiments
faster
fix-test
focus-point-hard-distance-filter
force-libpostal-param
fuzzy
greenkeeper/addressit-1.6.0
improved-reverse
improved_bias
integration
inter_layer_deduping
libpostal_aus_unit_numbers
log-long-queries
master
max_character_count_layer_filter
modify-label-generation-for-wof
msv2
nodejs10
one-query-test
output-generator-tweak
output-generator-tweaks
phrase_slop_disable_tf_idf
placeholder-lang-param-with-timing
popularity_boost_locality
precision
production
production_patch_logging
query-for-venues-on-admin-only
remove_ngrams_from_search
reset-focus-point-settings
riordan/openaddresses-attribution
search-all-admins
search-suggest-categories
silence-error-logs-in-tests
size-bug
skip-language-service-when-defaulted
split-comma-admin-boost
staging
temp_ngrams_strip_housenumbers
test-focus-point-weight
test_focus
tmp_adjust_autocomplete_focus
travis-exp
trim_by_granularity
using-pelias-ngram
wip-improve-reverse
wof_focus_weighting
wrap-longitude#56
1.0.0
1.1.0
1.1.1
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.2.0
1.2.1
2.0.0
2.1.0
2.1.1
2.2.0
2.2.1
v3.0.0
v3.0.1
v3.0.2
v3.1.0
v3.1.1
v3.1.2
v3.10.0
v3.10.1
v3.11.0
v3.12.0
v3.13.0
v3.13.1
v3.14.0
v3.14.1
v3.14.2
v3.15.0
v3.16.0
v3.16.1
v3.17.0
v3.17.1
v3.17.2
v3.17.3
v3.17.4
v3.17.5
v3.17.6
v3.17.7
v3.17.8
v3.18.0
v3.18.1
v3.18.2
v3.18.3
v3.19.0
v3.2.0
v3.20.0
v3.20.1
v3.20.2
v3.20.3
v3.20.4
v3.20.5
v3.20.6
v3.20.7
v3.21.0
v3.21.1
v3.21.2
v3.22.0
v3.23.0
v3.24.0
v3.25.0
v3.26.0
v3.26.1
v3.26.2
v3.26.3
v3.26.4
v3.26.5
v3.26.6
v3.26.7
v3.26.8
v3.27.0
v3.27.1
v3.27.10
v3.27.11
v3.27.12
v3.27.13
v3.27.14
v3.27.15
v3.27.16
v3.27.17
v3.27.18
v3.27.19
v3.27.2
v3.27.20
v3.27.21
v3.27.22
v3.27.23
v3.27.3
v3.27.4
v3.27.5
v3.27.6
v3.27.7
v3.27.8
v3.27.9
v3.28.0
v3.29.0
v3.3.0
v3.30.0
v3.31.0
v3.32.0
v3.32.1
v3.32.10
v3.32.11
v3.32.12
v3.32.13
v3.32.14
v3.32.15
v3.32.2
v3.32.3
v3.32.4
v3.32.5
v3.32.6
v3.32.7
v3.32.8
v3.32.9
v3.33.0
v3.34.0
v3.35.0
v3.36.0
v3.37.0
v3.4.0
v3.4.1
v3.5.0
v3.5.1
v3.5.2
v3.6.0
v3.7.0
v3.8.0
v3.8.1
v3.9.0
${ noResults }
api/test
Julian Simioni
7a6ac8541b
The address parser currently does two things: 1.) make some intelligent guesses as to possible admin regions to explicitly search against to improve the quality of results returned 2.) make some intelligent guesses as to when no part of the query needs to search against anything other than admin regions. This somewhat improves the quality of results returned but mostly improves the speed of the Elasticsearch query since it's searching significantly fewer recoords. These two concerns are now split into two separate methods within the query_parser helper module. They are mostly independent today, but don't have to be in the future. |
9 years ago | |
---|---|---|
.. | ||
ciao | Update ciao tests for /v1 | 9 years ago |
unit | Separate concerns of address parser | 9 years ago |
ciao.json | ciao config | 10 years ago |