pelias/api - api - CogtoSrc

Author	SHA1	Message	Date
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
Diana Shkolnikov	cb59e305b0	log number of streets to be interpolated	7 years ago
Stephen Hess	05da79923f	wrap interpolation service call to intercept errors	7 years ago
Stephen Hess	bfa8475443	fix @missinglink's typo	8 years ago
Stephen Hess	cf167ce933	map sources from helper/type_mapping.js	8 years ago
Stephen Hess	41831ab7a0	converted middleware/interpolate to use injected service	8 years ago
Diana Shkolnikov	e46c17a84a	Sort interpolated results to show address first	8 years ago
missinglink	3a4d26077a	interpolation: fix: source_id mapping	8 years ago
Peter Johnson	69be6e062a	service: interpolation: tests	8 years ago
Peter Johnson	576d1a1809	interpolation: integration v1	8 years ago