Common iD customisations

[geohacker]

I was chatting with @bhousel the other day about the recurring needs of people outside openstreetmap.org who use iD. I'm starting a list here, and hopefully we can turn some of them into actionable tickets into iD. These are not very well thought through:

• Presets - all the time. Currently most forks just overwrite presets.json. What if we allow a configurable URL hook?
• Imagery - all the time. Same as above.
• Validation rules - not very common. Should we think of validation rules in a pluggable way? Before the changeset gets pushed we run it through a set of functions that are extendable?
• Editing zoom levels based on density of features - not very common. But I've seen forks that try to change the default z16 to turn on editing mode based on how much data is in the view. The feature filters are great, but perhaps we can add this?
• Position the tool bar - move it around.

[1ec5]

• Help – Tools such as the HOT Tasking Manager provide accompanying documentation specific to the task at hand, but mappers have to flip back and forth between tabs to consult it. How could iD make it easier to embed custom documentation directly inside the Help flyout?

[bhousel]

Agree with everything above.. I think making a list of public forks of iD (and trying to stay more engaged with teams that have made them) would be a good first step to knowing really well what people actually need for customization.

[geohacker]

@bhousel - I'd love to do a quick survey/calls with people who run their own forks. How have you discovered them previously?