User defined preset?

[bagage]

Since there are many issues related to preset, this one might be a duplicate of one I could not find.

The idea is that adding a preset to iD requires:

1. git / github skills to clone the repository, commit the new preset, do a merge request, etc.
2. development skills to run a local instance to ensure that the preset works as expected, etc.
3. patience! The preset, once merged in master, will be available in next release (usually 1/2 months).

Finally my last arguments (but I am unsure there are valid one ;-)):

1. Some preset maybe culture specific/country specific/not useful for the all users.
2. If you map something specific (let's say fire hydrants), usually you use "fire hydrant" preset + you set the fire_hydrant:type + ref. To save a clic, one could have 2 presets pillar fire hydrant and underground fire hydrant. Also usually ref key has a specific value per region (PK01, PK02, etc), so it could be pre-filled with a pattern (here PK).

Finally my idea would be to have a Save as custom preset button in the preset form, that would save the current preset form locally on user local storage with a user chosen text. Then a new main category could be shown on the left sidebar User presets, as the existing ones.

I did not evaluate the technical complexity of that idea, but in a first place I would like to know if anyone find this useful/if it could be integrated in iD.

[bhousel]

#5049 will allow users to replace the presets at runtime. Once that is implemented, you could define your own presets in a .json file somewhere and use them instead of the builtin ones.