Peter Johnson

re: elasticsearch https://github.com/geopipes/elasticsearch-backend

Check out http://geogig.org/ "GeoGig is an open source tool that draws inspiration from Git, but adapts its core concepts to handle distributed versioning of geospatial data."

This 'fixes' it: ```diff diff --git a/test/util.js b/test/util.js index 500aad5..fc53365 100644 --- a/test/util.js +++ b/test/util.js @@ -61,8 +61,14 @@ function strip (line) { const withoutNestedLineNumbers = withoutLineNumbers.replace( /, :\$LINE:\$COL\)$/, ')'...

Thanks for your response, I'm just trying to understand the implications of downstream consumption of the data. From what you've said, it's unfortunately too hairy to use for any commercial...

Note that the `regenerate` dependency can be removed in favour of the pattern it generates, namely: ```js [\u0300-\u036F\u1AB0-\u1AFF\u1DC0-\u1DFF\u200D\u20D0-\u20FF\u3099\u309A\uFE00-\uFE0F\uFE20-\uFE2F] ```

"ẹ"

I noticed that you're not seeing any results in the demo due to the query filters being applied, the request being sent to the backend is: ``` sources=openaddresses focus.point.lat=37.7701981 focus.point.lon=-122.4522257...

Hi @generalpiston, the demo seems to be down at the moment. Is there anything we can do to help?

We would accept a PR similar to this one which has been full tested and shown to be working correctly on a countrywide build. https://github.com/pelias/interpolation/pull/274

We wouldn't accept a PR to select a version of TIGER as proposed in 2. of this issue description. Supporting multiple vintages is a maintenance headache with little benefit.