Sub-regions, repeated data and .geojson hosting about country-coder HOT 1 CLOSED

We have the following projects which work this way now:

• osm-community-index (probably has about as many custom geojsons as it needs)
• name-suggestion-index (potential for many custom geojsons)
• id-tagging-schema (needs few if any custom geojsons)
• and then there's background imagery 🤣 the less we say about that, the better.

I'm ok with just leaving the features/ folders in the separate projects for right now, without trying to establish a central place for them. Each project should just bring the minimal amount of geojsons that it needs. The goal is to ship less stuff with core iD, then pull it in only as needed. I'm not too worried about duplicating kilobytes of geojson. iD is already pretty data heavy, but most of that cost comes from downloading geodata from OSM and imagery tiles from wherever.

We also use a few tricks on the iD side to work with data when the browser is idle. For example, the community index gets downloaded and setup in the background while the user is either preparing their changeset comment or waiting for the upload to finish - so even if it got bigger or had redundant data in it, nobody would notice.

from country-coder.