pelias/api - api - CogtoSrc

Author	SHA1	Message	Date
Stephen Hess	52a6ec68ff	added support for coarse reverse geocoding several things are in this commit: - coarse reverse controller / pip service - inject "conditional execute" predicate into search service to shortcut execution conditions - added coarse reverse controller to precede standard reverse controller - lots of tests!	8 years ago
Stephen Hess	ac0776e2be	match error handling to controller/search	8 years ago
Stephen Hess	6425cc6444	added request retries for ES request timeouts	8 years ago
Stephen Hess	8c249c26f4	initialize esclient in routes/v1, eliminating need for src/backend	8 years ago
Julian Simioni	2557c68368	Use index name from config in controllers	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
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
Stephen Hess	cb7d22df91	switched ES lookup field from "type" -> "_type", fixes issue with /place lookup on Eiffel Tower gid	10 years ago
Julian Simioni	2505e92a62	Expect an array of types from _ids sanitiser This doesn't have any effect by itself but allows for the 3-part gid sanitiser to possibly return multiple types (i.e. in the case of osm:venue:1000)	10 years ago
Julian Simioni	aabca1569c	Fix old reference to /doc endpoint	10 years ago
Peter Johnson	348d2e70e2	more conformance	10 years ago
Diana Shkolnikov	db0e063d8c	Refactor controllers to be simple midddleware Refactor search and doc controllers to allow for post-processing middleware to handle geojson and response sending. Allows for a much more flexible routing scheme.	10 years ago
Julian Simioni	167547a6c1	Rename doc endpoint to place	10 years ago
Julian Simioni	2fce64f75a	Move files	10 years ago
Julian Simioni	4e74e9b681	Whitespace	10 years ago
Harish Krishna	0e9af3b9b8	adding controller tests to test details=true test case	10 years ago
Harish Krishna	c99c5f712a	adding a parameter called details (defaults to false for all endpoint except reverse) + fixing tests	10 years ago
Peter Johnson	ff757decb4	deprecate 'type' property, see PR notes	10 years ago
Harish Krishna	a53a6fd6d8	no query needed	10 years ago
Harish Krishna	be39fb5a8f	adding tests for the doc controller	10 years ago
Peter Johnson	6efa0aa510	expose id/type/layer	10 years ago
Peter Johnson	27e2c4e5b8	migrate outputGenerator from pelias/suggester-pipeline	10 years ago
Peter Johnson	17134105d5	geojsonify /search and /reverse FTW	11 years ago