Preset support of alternative preset items
Some of the recent patches to JOSMs default preset have included elements for what are essentially presets for "similar" objects. Example: 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 This would seem to be to me quite interesting information to capture, however the specific unstructured way of handling this would seem to be a bit sub-optimal. In particular this makes it difficult to present this in a reasonable fashion without restoring to ad hoc hacks. In the hope (though very very very small) that JOSM might some time in the future adapt an extension to support this better, before I implement this (see http://vespucci.io/tutorials/presets/#extensions for other extensions), I'm soliciting input on the preferred way to do this: - add an attribute to the preset_link element, example - introduce a new element, example - introduce a new element as a container, example In any case I will add this to the xslt transforms to re-create a JOSM compatible variant of https://github.com/simonpoole/beautified-JOSM-preset as I currently do, so this wouldn't create an incompatibility with use in JOSM. Simon signature.asc Description: OpenPGP digital signature
Re: OSM-SVN shut down, JOSM copy takes over
On 16/08/2020 19:21, Dirk Stöcker wrote: With "svn relocate" it's possible to switch an existing working copy to the new URL without a full re-checkout. For those of us with only basic SVN experience, perhaps your could provide the full command string for this operation. Thanks!
Re: Preset support of alternative preset items
On 17.08.2020 16:29, Simon Poole wrote: Some of the recent patches to JOSMs default preset have included elements for what are essentially presets for "similar" objects. This would seem to be to me quite interesting information to capture, however the specific unstructured way of handling this would seem to be a bit sub-optimal. Can you elaborate a bit more in what way you wish this to be more structured? It is there to list similar tags. Do you want to structure the level of "similarity"? - add an attribute to the preset_link element, example > So what else besides "alternative" do you suggest? - introduce a new element, example I do not see the difference here. besides "link" for generic links, this "preset_link" already is a link specific for alternative presets. What would a new one differentiate? - introduce a new element as a container, example All references to "similar" presets are already known by the presence of "preset_link". As you would have either one "alternatives" in case there are links, or zero if not, what is the benefit of another container level? Stephan
Re: Preset support of alternative preset items
Am 17.08.2020 um 22:40 schrieb Stephan Knauss: > > Can you elaborate a bit more in what way you wish this to be more > structured? > > It is there to list similar tags. Do you want to structure the level > of "similarity"? To avoid any misunderstandings this is not about individual tags, but about the real world objects complete preset items describe. The typical use of linked presets (and where they make most sense) is to add "sets" of tags that would overload the preset in question if added as individual tags. One of the frequent use of them in JOSM is for address and contact fields. This is semantically something totally different than suggesting an alternative preset item (because the current one might be a common mistagging, the alternative might be a more specific object, etc). And because it is semantically different it should be presented differently. > >> - add an attribute to the preset_link element, example > >> > > So what else besides "alternative" do you suggest? > >> - introduce a new element, example >> > I do not see the difference here. > besides "link" for generic links, this "preset_link" already is a link > specific for alternative presets. What would a new one differentiate? See above, that is not actually how the majority of the linked presets are used. The concept is a recent introduction (if it wasn't, please explain why the "Similar but different tags:" text is necessary). > > >> - introduce a new element as a container, example > All references to "similar" presets are already known by the presence > of "preset_link". As you would have either one "alternatives" in case > there are links, or zero if not, what is the benefit of another > container level? > Again, see above. > Stephan > > signature.asc Description: OpenPGP digital signature