Use grid to get country code in place of Nominatim

[hlaw]

PR further to #2258, with the tiles checked in and amendments made. Using iD.Context rather than the UI to track movements. The Makefile points to osmlab rather than my repo for tiles update, assuming the repo name is country-code-grid.

Thank you!

[cschwarz]

As this approach is not async anymore, you can remove the init event and isInitialized.

Otherwise it looks nice and opens up many possibilities. 👍

[hlaw]

In relation to what I have been thinking of at #2254, if we support retrieval of a list of nearby cities / towns / suburb from nominatim for the addr:city / town fields etc as specified in the country specific rules (rather than rely on the data currently loaded into iD), then the async code might be needed again very soon. It might perhaps be useful to keep this for the expansion?

[jfirebaugh]

The downside to using the current center of the viewport for the address format is if you are editing near a border, you get the address format for the neighboring country instead. The old approach based the address format for a feature on the location of the feature itself, rather than the map center. Can we continue to do this?

[hlaw]

Sure. Since it would be useful to maintain a global state on the country for general use, I would suggest the following implementation -

(a) when any object is selected, the location of the centroid of the selected object is used;
(b) otherwise when hovering, keep track the location of the mouse pointer.

The address format displayed during hovering and selection would then be based on the location of the feature.

[bhousel]

This PR has gone stale.. @hlaw are you still interested in merging this? I noticed that country-code-grid never made it over to osmlab..

[bhousel]

Closing as stale - besides the nominatim lookups work pretty well and including this country code grid would drastically grow the size of the iD distribution.