otbutz

> Is there another guide explaining how to use interpolation with non US data? Here you go: https://github.com/pelias/interpolation#building-the-databases tl;dr: * create `street.db` from your polyline data * use your `street.db`...

I wholeheartedly agree that these kind of things can get messy very quickly. But the case at hand seems rather trivial. PIP should be able to solve this.

IMHO incorrect data should be fixed at their source. But overlapping postalcode shapes are indeed a problem. Suggestion: * use the postalcode of the address if it's already present *...

> A `street` is different from an `address` in that it can easily span multiple postal codes and streets don't commonly have associated postcodes. Correct. It *can* span multiple postal...

> Can PIP currently do this? I thought it was only Point in Polygon not Polygon in Polygon? I *think* it's not supported ATM but it would be a good...

So basically you want the results sorted by String similarity?

> As we had already noticed with `tltk`a general problem of python shared procedures seemed to be, that imported modules are not persistent between connections in PostgreSQL. Thus imports which...

Looks good. Some early benchmark numbers?

@giggls bbox support for relations got merged into osm2pgsql. see https://github.com/openstreetmap/osm2pgsql/issues/1284

@nosduco `copy-headers` works the other way round: > copy_headers is a list of HTTP header fields to copy from the response to the original request, when the request has a...