pelias/api - api - CogtoSrc

Commit Graph

Author	SHA1	Message	Date
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
Julian Simioni	0ee1fdb4d9	Remove obsolete Geonames ID tests These are fixed now with our better source/layer mapping	9 years ago
Julian Simioni	fa07ba9ddc	Add much needed whitespace	9 years ago
Julian Simioni	cdd00af6bc	Build responses with new source and layer fields There is no longer any ambiguity in the source field and the layer (which is stored as _type), so a lot of logic to compute them can simply read from the elasticsearch document. Hooray!	9 years ago
Stephen Hess	d1dc88cefd	added tests for `default` schema	9 years ago
Stephen Hess	0f6059c05a	Refactored to use a function for looking up value for a label The reason for this switch is that special case logic is needed to determine the US state name to display. All other fields can be looked up by name. The burden of fallback functionality is now in `helper/labelSchema` so the burden of unit testing is now in `test/unit/helper/labelSchema.js`	9 years ago
Stephen Hess	431fe44f05	converted labelSchema to .js with module.exports this is in preparation to introduce functions into the schema instead of strings	9 years ago
Stephen Hess	08f414b3d5	fixed encoding error that came from master	9 years ago
Stephen Hess	f7260c63a0	added tests for USA local and regional fallbacks for label generation	9 years ago
Stephen Hess	5456632cdf	Added flag to not include `default.name` in label when source=`geonames` or `whosonfirst` and layer=`region` This will stop, say, a search for "New Mexico" resulting in the label "New Mexico, NM, USA"	9 years ago
Stephen Hess	3e11e6687c	added `country_a` to label for all USA results	9 years ago
Stephen Hess	3e8d1bfd9b	broke country-specific label tests out to own file for easier testing	9 years ago
Julian Simioni	0e78167f17	[/place] Accept any valid layer for geonames Instead of checking if the source/layer combination for geonames is valid, always use the geoname type if the source is set to geonames, regardless of which layer is in the gid. This helps us better handle the case where people directly take gids from our API responses. Note: this functionality shouldn't be permanent and should be removed once our new source/layer mapping system is in.	9 years ago
Julian Simioni	18de8b5699	Remove unused test examples	9 years ago
missinglink	6711aa45e0	simplify pass 1	9 years ago
missinglink	3b4d566b11	add unit test	9 years ago
Diana Shkolnikov	df93be7543	Fix deduping for non-ascii strings	9 years ago
Peter Johnson	db5a78623a	disable viewport scale	9 years ago
Peter Johnson	f1ead56e60	disable viewport scale	9 years ago
Julian Simioni	87f6f32985	Use tape's throws where appropriate	9 years ago
Julian Simioni	fcc9237993	Use tape's doesNotThrow where appropriate	9 years ago
Julian Simioni	b5be8dea42	Remove duplicate test	9 years ago
Julian Simioni	5a84afa539	Add test of parsing hit with no address object In #369 I said I wouldn't bother testing for the case of the address object on hit being absent, but it turns out that does sometimes happen.	9 years ago
Diana Shkolnikov	9fa5fc5a77	calcSize became middleware (exposed and fixed bug in query defaults)	9 years ago
Diana Shkolnikov	42d940f8c8	Add simple normalizer (lowercase + remove punctuation)	9 years ago
Diana Shkolnikov	54187dde67	Add dedupe middleware Dedupe middleware removes __exact__ dupes and truncates the results to the specified size.	9 years ago
Diana Shkolnikov	500835a4c1	Update addressit module to not strip 0s from zipcodes	9 years ago
Peter Johnson	49d37eafed	one config per query	9 years ago
Peter Johnson	4e43310288	german street/number naming convention	9 years ago
Julian Simioni	db895c05b7	Rename `from_address_parser` key to `from_text_parser`	9 years ago
Julian Simioni	b188a2046c	Fix mismatching name of types preference parameter The parameter in clean.types being set by `helpers/text_parser.js` was "from_address_parsing", but the code in `helper/types.js` was expecting "from_address_parser". This commit makes both use "from_address_parser" and adds a test.	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
Julian Simioni	0e8f4253c0	Return multiple results in place when osm node and way share an id It turns out the _type parameter to the Elasticsearch [multiget](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-multi-get.html) API does not allow an array of possible values. We were depending on its ability to search multiple types to allow searching for OSM nodes and ways. But, since this doesn't work we essentially have to do it ourselves. There is also the problem that OSM nodes and ways share an ID space. So a gid such as `osm:venue:5` could in theory correspond to 2 records. It seems like the only nice thing to do in that case is return both results. This PR "unrolls" such queries. For example, in the case of `osm:venue:5`, the sanitisers will return the following array of objects to be turned into multiget queries: ``` [{ id: 5, types: ["osmway", "osmnode"] }] ``` Before, this would turn into a multiget query with only one entry, like this: ``` { "docs": [ { "_index": "pelias", "_type": [ " osmnode", "osmway" ], "_id": 5 } ] } ``` now it would look like this: { "docs": [ { "_index": "pelias", "_type": "osmnode", "_id": 5 }, { "_index": "pelias", "_type": "osmnode", "_id": 5 } ] } TLDR you might get back more records from /place than the number of ids you specified, but at least you will definitely get back what you are looking for.	9 years ago
Peter Johnson	85a51bc48a	more usa test cases	9 years ago
Peter Johnson	d93f9c1803	more new zealand test cases	9 years ago
Peter Johnson	7cf8638795	more australian and thai test cases	9 years ago
Peter Johnson	5cc432ae50	more indian test cases	9 years ago
Peter Johnson	b5b8647f0c	more label improvements	9 years ago
Peter Johnson	8ceac4cbb0	change modifier function from sqrt() to log1p() and adjust max_boost	9 years ago
Peter Johnson	2ce249ad30	adjust balance between population/popularity and focus	9 years ago
Peter Johnson	481a65a4f9	population twice as important as popularity	9 years ago
Peter Johnson	cb679888ff	better population and popularity boosting	9 years ago
Peter Johnson	56591abe97	remove all references to tiebreaking groovy scripts	9 years ago
Stephen Hess	4be987045e	updated tests to reflect master type_mapping	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	fef92bd34b	Remove the geoname _type from all layers except venue We can't distinguish between geonames of different layers due to an ambiguity in our Elasticsearch schema that we unfortunately won't be able to fix for a few weeks. So, while it's technically true that there are countries, cities, etc contained in the geonames dataset, it's still better for now to remove geonames from these layers. We have good coverage of most coarse layers from quattroshapes alone, so the impact isn't too bad.	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
Julian Simioni	06b44e5355	Disallow specifying both focus.point and focus.viewport	9 years ago
Julian Simioni	9dcc296a70	Add focus.viewport rect sanitizer to search	9 years ago

... 4 5 6 7 8 ...

699 Commits (e761f9942239167592ae31d658ad41a5eda87db1)