pelias/api - api - CogtoSrc

Commit Graph

Author	SHA1	Message	Date
missinglink	077bd3f78e	feat(dedupe): move canonical_sources config to pelias/config	6 years ago
Peter Johnson	c0a0663e21	feat(dedupe): treat all non-canonical layers and analogous to a venue, prefer non-canonical records	6 years ago
Peter Johnson	14e6c6303f	refactor middleware dedupe for readability	6 years ago
Julian Simioni	2a668612ed	feat(confidence): Add support for new query names	6 years ago
Julian Simioni	c548a73cb9	fix(confidence): Update query type names in confidence score code `4adf4b3dd7` renamed some queries to be quite a bit more informative, however it wasn't obvious that these query names were used elsewhere in the code. With those changes, no confidence score middleware was running, which this should help fix.	6 years ago
Julian Simioni	d681a114d6	feat(log): Remove most unstructured controller logs These are nose now, the structured logs have much better info	6 years ago
Julian Simioni	f5c6dcf882	feat(log): Add structured logs for interpolation service	6 years ago
Julian Simioni	92d15c6687	feat(log): Log structured data about Placeholder requests Structured logs allow later analysis with details like query parameters, request time, etc.	6 years ago
Peter Johnson	fa8257cd06	feat(debug): debugging info for interpolation service	6 years ago
Nuno Patronilo	6d7726ae42	Parse order on the label field for Portugal Added PRT to the array on var flipNumberAndStreetCountries	6 years ago
Julian Simioni	800eb8ca03	Move lots of logging from info to debug These are log lines that are not really useful in a production context, and just create a lot of noise.	6 years ago
Julian Simioni	10241047a6	fix(interpolation): Ensure proper sorting of streets with interpolated addresses In cases where several conditions are met, it is possible for results to be returned from the API that are not sorted as they were intended. These conditions are: * over 10 results total were returned from Elasticsearch * the interpolation middleware was called * not all street results end up with possible interpolated address matches, and some of those streets come before other interpolated address records, necessitating a re-sorting of the results in the interpolation middleware In these cases, the ordering of streets as defined by Elasticsearch, such as by linguistic match or distance from a focus point, will no longer be respected in the results. This is because Node.js's `Array.prototype.sort` uses an [unstable QuickSort for arrays of size 11 or greater](https://github.com/nodejs/node/blob/master/deps/v8/src/js/array.js#L670). The solution is to switch to a sorting algorithm that is always stable. This ensures that whatever ordering was specified in the Elasticsearch queries is observed, without any of that logic having to be duplicated, and then possibly conflict. Stable sorting is provided by the [stable](http://npmjs.com/stable) NPM package.	7 years ago
Julian Simioni	bb860b815d	fix(attribution): Use correct path for attribution endpoint	7 years ago
Julian Simioni	7122317f2a	feat(attribution): allow overriding attribution URL This url is used to show attribution information for Pelias data sources It was often not detected correctly if, for example, the API is proxied behind a load balancer.	7 years ago
Julian Simioni	204f5297de	Remove all leading newlines in files	7 years ago
Julian Simioni	02aac0c13e	Remove use stricts	7 years ago
Julian Simioni	8bccfc4fd2	Remove other instances of Mapzen	7 years ago
missinglink	e01fdb85c9	support aliases for label generation	7 years ago
missinglink	7a01e794cf	support aliases for name fields	7 years ago
Julian Simioni	e5e3b92af3	Fix extremely verbose, repeated error output In some error cases, a warning is repeated many many times. It turns out there is code checking against elasticsearch error codes, and warning _each_ time it fails to match aganst one of them. Many times, the error that is being compared is not from elasticsearch, and in any case, the [elasticsearch-exceptions](https://www.npmjs.com/package/elasticsearch-exceptions) module is 3 years old. We should rewrite most of this code and stop using that module. For now, this at least reduces log noise.	7 years ago
missinglink	1752875f11	feat: fix attribution link	7 years ago
Julian Simioni	5247ea575d	Give variable a better name	7 years ago
Julian Simioni	c966e6f6ae	Allow the minimum Elasticearch query size to be set per endpoint Reverse queries don't need as much deduping, for example	7 years ago
Julian Simioni	2e92f15a91	Whitespace	7 years ago
antoine-de	3489517da3	dedup osm/OA address linked to https://github.com/pelias/pelias/issues/541 and maybe to https://github.com/pelias/pelias/issues/541 but I cannot reproduce it. and to the fact that there are lots of dupplicates in france like: [20 rue hector malot paris](https://mapzen.com/search/explorer/?query=search&text=20%20rue%20hector%20malot%20paris) that returns 1 result from open address and 1 result from OSM now we first check which source has a zipcode and if both have, we prefer OA over OSM	7 years ago
Diana Shkolnikov	cb59e305b0	log number of streets to be interpolated	7 years ago
Stephen Hess	16e01b5049	remove unused require	7 years ago
Stephen Hess	759c0e0939	switched to lodash.extend over extend module	7 years ago
Stephen Hess	05da79923f	wrap interpolation service call to intercept errors	7 years ago
Diana Shkolnikov	40870c4e04	check for missing parent object in confidence score computation	7 years ago
Diana Shkolnikov	b60e0113b3	check for missing parent object in confidence score computation	7 years ago
Julian Simioni	a233e11d59	Remove Access-Control-Allow-Credentials header This header is only relevant if dealing with authentication via cookies or other methods in HTTP requests. The Pelias API intentionally doesn't deal with authentication at all, assuming anyone who wants authentication will deal with it using a service placed between Pelias and end users. Additionally the CORS spec [does not allow](https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Credentialed_requests_and_wildcards) specifying this header while setting a wildcard for `Access-Control-Allow-Origin`, so it can cause problems in some cases. Fixes https://github.com/pelias/api/issues/971	7 years ago
Adam Rousell	f86ee4a40f	Added postalcode rules for node-postal call and fallbacks	7 years ago
Stephen Hess	bfa8475443	fix @missinglink's typo	7 years ago
Stephen Hess	cf167ce933	map sources from helper/type_mapping.js	7 years ago
Stephen Hess	41831ab7a0	converted middleware/interpolate to use injected service	7 years ago
Stephen Hess	92d18af886	updated changeLanguage to injection model	7 years ago
Lily He	cafb7d9277	created new debug helper class and debug sanitizer	8 years ago
Stephen Hess	2e90892b25	info->debug to reduce log noise	8 years ago
Stephen Hess	775fd1f568	updated code+tests to findById name array output format	8 years ago
Stephen Hess	5a8ddd6268	added debug logging for sorting	8 years ago
Stephen Hess	238b49a0d8	added should_execute to sortResponseData	8 years ago
Stephen Hess	446d428292	don't reassign, sort works inline	8 years ago
Stephen Hess	5d7a467909	added response data sorting middleware	8 years ago
Stephen Hess	8429e0f22a	added response data sorting middleware	8 years ago
Diana Shkolnikov	a3e8f8d566	fix exception when no ids are found in placetype	8 years ago
Diana Shkolnikov	6cc53e4e0b	merge multiple hierarchies into arrays and use first ones	8 years ago
Kevin Ennis	512cec9945	Prefer openaddresses results with zip code	8 years ago
Julian Simioni	6b0b124d8f	Always query for a minimum of 20 results from Elasticsearch Fallback and interpolation queries rely on several results coming back from Elasticsearch to ensure the best result is returned. It was possible that queries with `size=1` would not return enough results from Elasticsearch. This change ensures even with `size=1` a sufficient number of results are returned. Fixes https://github.com/pelias/pelias/issues/562	8 years ago
Diana Shkolnikov	798363da1e	remove unwanted log statement	8 years ago

1 2 3 4 5

208 Commits (3535f9eae13f46def6e35087b6d12cefc8dfcdc2)