When a user's first change is to a way, it can't be geolocated

[iandees]

Since the plugin only tracks minutely diffs and doesn't make any other API queries, it does not have any lat/lon coordinates to reverse geolocate on when a user's first change is made to a way or relation.

For the case of a way, we should probably query the API for that way (using e.g. /api/0.6/way/<id>/full) and reverse geocode using the first node in that way.

For relations, we probably shouldn't attempt to reverse geocode it.

[Firefishy]

Why not do the same for relations?

[iandees]

Which node (from which way) would we use? Just the first I suppose.

[Firefishy]

Yeah, just the first node. Sure relations can be silly large, but just looking for an estimate.