pelias/api - api - CogtoSrc

Author	SHA1	Message	Date
Stephen Hess	02cfa36d24	switched structured query tests away from fixtures	7 years ago
Diana Shkolnikov	fe38d2336d	feat: allow postalcode-only structured queries	8 years ago
Stephen Hess	be2a336038	updated naming from component to structured	8 years ago
Stephen Hess	7aad07368d	modified tests to accommodate changes to ComponentFallbackQuery	8 years ago
Stephen Hess	d2c32b5afd	added unit tests for component_geocoding query started folder structure for fixture as it's getting unwieldy	8 years ago
Stephen Hess	08f4aa4b95	renamed files to be more indicative of what the function is	8 years ago
Stephen Hess	d03a8c4586	added support for component geocoding - created `/component` route - broke out trimByGranularityComponent but could conceivably be combined with existing - added `address` support to text_parser - added `component` sanitizer wrapper	8 years ago
Stephen Hess	df6bd50645	unrolled loop tests	8 years ago
Stephen Hess	acb669b7b3	added support for optional country	8 years ago
Stephen Hess	b8bd6c1252	enabled city/state only inputs for fallback queries	8 years ago
Diana Shkolnikov	9ff383cc2b	change the query module interfaces back to simple functions	8 years ago
Diana Shkolnikov	3888ae0385	change query module interfaces to allow for additional meta data	8 years ago
Stephen Hess	c841ed8121	limited fallbackQuery usage to analysis with `street`	8 years ago
Stephen Hess	cc5c9f8468	disable calling GeodisambiguationQuery	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	c257eb5fc3	added tests for new queries left in place but commented out tests that will be supported when boundary, focus, and sources/layers issues are resolved.	8 years ago
Stephen Hess	8c12452fff	added hardcoded values in tests where text-analyzer was being used before	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
Peter Johnson	cb67dd58d8	refactor boolean query filtering as per: https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_query_dsl_changes.html#_literal_filtered_literal_query_and_literal_query_literal_filter_deprecated	9 years ago
missinglink	2398f05f8d	fix borough matching for both autocomplete and search endpoints	9 years ago
Stephen Hess	bd3b8e7bbe	switched to pelias-text-analyzer package since that responsibility has been moved to there	9 years ago
Peter Johnson	0abda099a6	bugfixes and more tests	9 years ago
Diana Shkolnikov	e9ceb25ca0	Fix crash when dedupe was comparing arrays as stings for parent properties	9 years ago
Diana Shkolnikov	af8044ef29	Fix all unit tests	9 years ago
Peter Johnson	db5a78623a	disable viewport scale	9 years ago
Peter Johnson	f1ead56e60	disable viewport scale	9 years ago
Diana Shkolnikov	9fa5fc5a77	calcSize became middleware (exposed and fixed bug in query defaults)	9 years ago
Julian Simioni	59b70f7c7e	Rename helper/query_parser to helper/text_parser	9 years ago
Stephen Hess	d732021d5e	fixed tests	9 years ago
Peter Johnson	56591abe97	remove all references to tiebreaking groovy scripts	9 years ago
Stephen Hess	dcadc7832e	add focus:scale to /search requests with just viewport.*, calculated from bounding box diagonal, minimum of 1	9 years ago
Julian Simioni	57fb960471	Set centerpoint of viewport in search query This simply reuses the focus:point:{lat\|lon} variables, but sets them using the centerpoint of the viewport. Eventually we should calculate a radius and use that here.	9 years ago
Peter Johnson	82ab899ecc	progress commit	9 years ago
Julian Simioni	f3acf3b308	Check for numeric value of lat/lon to avoid null island bug Using the check-types module, check that lat/lon values are numbers, instead of checking their truthyness, to ensure that queries for null island work correctly.	9 years ago
Julian Simioni	190304b039	Use flat structure for focus.point.{lat\|lon} in query/search.js	9 years ago
Julian Simioni	4260442f59	Change boundary.circle params to flat string structure	9 years ago
Stephen Hess	a4c43ee482	added fixture for boundary.country in query building	9 years ago
Julian Simioni	040871cbe4	Whitespace	9 years ago
Peter Johnson	d568c031a3	move stringify logic to tests, code clean up	9 years ago
Peter Johnson	2f8169ac10	remove unused sort conditions	9 years ago
Peter Johnson	22322eaa32	change param:input to param:text	9 years ago
Harish Krishna	86424b8bbe	Rename `/search?input`, replacing it with '/search?text' parameter instead changing parameter name input to text https://github.com/pelias/api/issues/172 Rebased by @orangejulius	9 years ago
Julian Simioni	6f92189519	Remove default_layers_set flag! After refactoring, this flag is no longer needed, as all areas of the code that care about layers do so by setting a key within clean.types, and then the types helper intelligently combines those together later.	9 years ago
Julian Simioni	7a6ac8541b	Separate concerns of address parser 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
Peter Johnson	f5e182c63b	fix tests, clean by moving fixtures to fixtures dir	9 years ago
Julian Simioni	3ff1752434	Remove default_layers_set flag! After refactoring, this flag is no longer needed, as all areas of the code that care about layers do so by setting a key within clean.types, and then the types helper intelligently combines those together later.	9 years ago
Julian Simioni	b9152dbe29	Separate concerns of address parser 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
Peter Johnson	776b0ce1e1	update unit test	9 years ago
Diana Shkolnikov	49d439425e	Use address_weights.js in tests instead of hardcoding boost values	9 years ago