automatic update for imagery entries

[bastiK]

Automatic update (based on file name) is already working for tagging presets and map styles and should be implemented for imagery entries as well.

E.g. recently max zoom for Mapbox has been changed from 17 to 19. However, the imagery entry in my preferences is stuck at 17 even after refresh of the imagery list. You have to remove the entry and re-add it manually, this is not very user friendly.

One problem with this is, that we do not have a stable identifier:

• URL can change when the server is moved or reconfigured
• Name entry changes for various reasons

---

Possible solution: Introduce new attribute id.
This can be optional at first. It is of course slightly redundant w.r.t. the name attribute, but would have multiple uses:

• automatic update of imagery entries
• stable cache id, nicer directory name for file cache
• more suitable entry for the changeset source tag

Note, that the iD imagery database is originally based on JOSM's list and they have decided to add an id attribute: ​see here
This is used in the changeset comment (imagery_used=...), e.g. ​here.
If we adopt this scheme and synchronize the ids with iD, this would be nice for statistical analysis.

[Don-vip]

+1 for the id solution :)

[stoecker]

If we use such an id, we need to change the server code verification, so that it is ensured, that really each entry has another id. Otherwise we'll have copy&paste problems.

[bastiK]

In any case we have to check on the client, that the ids are unique. If not, you'd get a warning on the console and the second entry is skipped. Maybe this is enough. (Server check would be even better of course.)

[bastiK]

In 7177/josm:

see #9914 - add id to schema file

[bastiK]

In 7186/josm:

see #9914 - automatic update for imagery entries using id

[bastiK]

In 7203/josm:

fixed #10088 - Can't use custom TMS layer anymore (see #9914)

[Don-vip]

is there still something to do on this ticket?

[bastiK]

Automatic update is complete. The two other ideas in the first post are independent projects, so can be closed for now.