Tom Hughes

Because nobody's written it - patches welcome.

Well I wasn't taking "use achavi" literally, aside from anything else I have absolutely no idea how it works but presumably it has some parallel database that we wouldn't want/need...

As a matter of policy we don't normally link to third party services like that - there are dozens of changeset analyzers that people have built and if we link...

Well that only helps if a small number of changesets are viewed repeatedly, which doesn't seem likely. It sounds like all of this is irrelevant until we have our own...

It's on the wish list.

I believe all endpoints are passed through the geocoder - fixing that will not be trivial.

The line you pointed to won't have any (significant effect) unless you really want centimetric precision.

Yes https://github.com/openstreetmap/openstreetmap-website/blob/999b9c69e1af252610a2ad338d33d16273fcc22f/app/assets/javascripts/index/directions.js#L69 is the real problem because it passes the value through the geocoder which likely snaps to the nearest place it knows about.

We are now expiring at the metatile level, yes. The idea of the length limit was really twofold, to reduce the amount of time we spent re-rendering tiles and to...

Thanks for all the fixes... I think this is probably good to merge now.