<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jun 21, 2018, at 6:16 AM, Christoph Hormann <<a href="mailto:osm@imagico.de" class="">osm@imagico.de</a>> wrote:</div><div class=""><div class=""><br class="">Then why do you object to Frederik's idea of separating the tagging <br class="">presets from editor development and give up control over the decisions? <br class=""></div></div></blockquote><div><br class=""></div><div>I offered to do exactly this a few years ago:</div><div><a href="https://github.com/osmlab/editor-presets/pull/2" class="">https://github.com/osmlab/editor-presets/pull/2</a></div><div>Nobody cared, so it sat and eventually went stale over a few months.</div><div><br class=""></div><div>I wouldn’t do it today. </div><div><br class=""></div><div>Looking back on the <a href="https://github.com/openstreetmap/iD/blob/master/CHANGELOG.md" class="">iD changelogs</a> (and scanning through the still open issues) there are lots of usability items that affect the preset system.</div><div>Some recent examples of things I couldn’t do (quickly) if the presets were an external project:</div><div><br class=""></div><div>* We changed all the icons to support <a href="https://github.com/openstreetmap/iD/issues/3025" class="">multiple iconsets</a> and this meant that I needed to change all the icon names in all the presets.</div><div>* We implemented a check to support <a href="https://github.com/openstreetmap/iD/issues/5043" class="">min and max field values</a>, and it meant that I needed to go through all the presets and add some properties to certain ones.</div><div>* We renamed the field label from <a href="https://github.com/openstreetmap/iD/issues/5019" class="">“Phone” to “Telephone”</a> so that a user can type either value in the Add field dropdown.</div><div><br class=""></div><div>Usability and speed of development are very important to me, and these are things that would suffer if I split the presets off into a separate project.</div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">I am glad you work on improving possibilities for choice of presets and <br class="">this could over time be used to allow alternatives - like converting <br class="">the JOSM presets (which already includes a lot of specialized add on <br class="">preset collections) or managing diverse independent preset collections. <br class="">This is IMO the best way to go ahead here.<br class=""></div></div></blockquote><div><br class=""></div><div>Yes allowing people to override the presets at runtime is something I want to add. (I almost built it at the hackathon.)</div><div><br class=""></div><div>For the curious, the somewhat tricky part about this is the bootstrap process. Currently, presets in iD are ready at startup and translations are loaded in later. If a user specifies a replacement preset file, we need to delay some code until the browser has fetched everything.</div><div><br class=""></div><div><br class=""></div><div>Just going to cut my reply off here. There was some vague stuff in your message about “poisoning OSM” that didn’t seem to be a serious question. Also for the record, I’m fine with either method of mapping runways (I prefer to map them as a 2 node way myself). iD supports both methods (drawn as a linear way or as a closed way area). </div><div><br class=""></div><div>If you don’t use iD, I encourage you to try it out..</div><div>Please report any specific bugs for feature requests on our issue tracker: <a href="https://github.com/openstreetmap/iD" class="">https://github.com/openstreetmap/iD</a> </div><div><br class=""></div><div><br class=""></div><div>Thanks, Bryan</div><div><br class=""></div></div></body></html>