jmapb

Depending on how you calculate "nearest," that approach may or may not give good results. For the node in my example, [way 241845974](https://www.openstreetmap.org/way/241845974) might in fact be the nearest object...

Yeah, I swapped the order of the `id` & `info` url params for easier pasting of way ids! 😉 ...For good or bad, OSM doesn't have a lot of top-down...

Thinking again, the all-nodes-in-or-on check could still give false negatives when complex buildings abut. What would probably do best is some kind of polygonInPolygon function that would return the percentage...