pelias/api - api - CogtoSrc

Author	SHA1	Message	Date
Julian Simioni	59b70f7c7e	Rename helper/query_parser to helper/text_parser	9 years ago
Julian Simioni	8f1c8f4d89	Add helpful comments in various query parser locations	9 years ago
Julian Simioni	8b1037d7c8	Separate real layers and alias layers into separate objects	9 years ago
Julian Simioni	68c9661c70	Remove all mappings other than helper/type_mapping	9 years ago
Diana Shkolnikov	553f9780c5	Remove admin matching when address is not parsed	9 years ago
Diana Shkolnikov	c069933d5b	Refactored layers and sources into a common targets module	9 years ago
Peter Johnson	22322eaa32	change param:input to param:text	9 years ago
Julian Simioni	139cb22127	Remove layers limiting on queries with few tokens Primarily as a performance optimization, but also to attempt to return more relevant results, only admin and POI layers were queried when the text input consisted of only one or two tokens, and there weren't any numbers. However as shown in #194 that is a bit too optimistic, mostly in contries other than the USA. Fixes #194	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	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
Julian Simioni	0adc2821d2	Remove seemingly unhelpful comment	9 years ago
Julian Simioni	1fae622c39	Remove layer configuration based on address parsing This code doesn't seem like it will be triggered very often (due to it comapring space delimited words with comma delimited words from the text field), and also has the potential to cause quite a bit of weird behavior.	9 years ago
Julian Simioni	e71fb7cfd4	Whitespace	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
Julian Simioni	e42cb4a746	Remove seemingly unhelpful comment	9 years ago
Julian Simioni	ad8db9b8e9	Remove layer configuration based on address parsing This code doesn't seem like it will be triggered very often (due to it comapring space delimited words with comma delimited words from the text field), and also has the potential to cause quite a bit of weird behavior.	9 years ago
Julian Simioni	fb0cf514e9	Whitespace	9 years ago
Harish Krishna	fae9aae3d3	moving the logic for each of the three parsed addresses out into their own function	9 years ago
Harish Krishna	495c3251a4	moving all query parsing logic into its own helper. Tests to come	9 years ago
Harish Krishna	a8c090252a	if the query has a number - search addresses	9 years ago
Harish Krishna	346f187c3e	updateing isNumber regex	9 years ago
Harish Krishna	e1f3cfa0d3	no need to hit address parser if the input has just one token or two and no numbers Ex: new, new york, minneapolis etc dont need address parsing but 'starbucks 10010' might need it	9 years ago
Harish Krishna	ebd4a5a08a	splitOnDelim first followed by a space tokenizer	9 years ago
Harish Krishna	a4d09f8e12	no address parsing required if there are only 2 or less tokens	9 years ago
Harish Krishna	bdffe758d4	commenting out the overkill	9 years ago
Harish Krishna	96a21570be	fixing layers related bug - adding a default_layers_set flag to clean obj.	9 years ago
Harish Krishna	042772cf3b	only do address parsing when necessary	9 years ago
Harish Krishna	1d24890b27	introducing target_layer that gets set part of input_parsing - if input is less than 3 characters -> only hit admin layers - if input suggests that its not a street address -> avoid hitting address layers	9 years ago
Harish Krishna	5accecfa6c	adding postcode support for usa	10 years ago
Harish Krishna	46cc1a6569	disabling parse-address	10 years ago
Harish Krishna	0b5b1dce85	address parser initial pass - breaks 68 tests! (ignoring tests for now)	10 years ago
Harish Krishna	176f580215	using is-object	10 years ago
Harish Krishna	d2d76be8fa	changing a commented line to reflect reality	10 years ago
Harish Krishna	a003b7b9bf	strip out leading and trailing whitespace if any	10 years ago
Harish Krishna	84a9b3e20e	splitting on comma (trying to find/assume admin values)	10 years ago
Harish Krishna	32275aca56	split sanitizers into reusable pieces. renaming sanitise to suggest. using suggest sanitizer for search. adding reverse sanitizer. updating tests..	10 years ago