pelias/api - api - CogtoSrc

Author	SHA1	Message	Date
Diana Shkolnikov	c415b96ead	Named admin_parts adminParts which caused problems	9 years ago
Diana Shkolnikov	928597e029	Fix admin parts parsing without spaces after delimeters	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
Diana Shkolnikov	500835a4c1	Update addressit module to not strip 0s from zipcodes	9 years ago
Julian Simioni	59b70f7c7e	Rename helper/query_parser to helper/text_parser	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
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
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	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	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	e57d0b38ed	keys -> key It's easy to misread and think keys contains a collection of some kind	9 years ago
Harish Krishna	95c0e7461d	TESTS!	9 years ago