This doesn’t take the place of exports, but it’s more the kind of thing that can be done with exports, and making the results easier for people to use.

The site itself is young, not sure where exactly it’ll go, but it’s open source and I believe fairly easy to work with (an appropriately small codebase).

The idea is to start with requiring lat/lon as the input but, if there’s demand, I don’t see a reason why the service couldn’t also accept an address and return lat/long + geographies. Good idea on the accuracy; would returning an annotation that “point is near a boundary line for __ geo” + including in the metadata for each boundary set the geocoding success rate be enough?

On this thread, we’re also thinking about returning overlapping boundaries for a polygon input, but there’s significantly more development involved in that. In the beginning, it will be just points.

Additional information: if the input is anything other than a lat/lon pair, then you need to give feedback on how the input string was geocoded, hopefully how accurate the geocoding is considered, and possibly a list of alternative possible answers?