A couple of weeks back, see https://josm.openstreetmap.de/ticket/12412 , explicit support for multipolygons was added to the presets.
This is, in principle, a good thing, given that preset matching/application shouldn't be dependent on how an area is technically modelled . Alas the actually implementation seems to leave a bit to desire, in that instead of abstracting closed ways that are areas and multipolygons to one type, now both values have to be set. While it works in general, there seem to be some arbitrary differences being made between closed way defined areas and multipolygons (random example: swimming pools). Likely just oversights, however they do show that using 1.5 values for the same concept is simply error prone. I would suggest re-jigging things so that - "closedway" is used for closed ways without area semantics (roundabouts etc.) - a new type value "area" is used for closed ways with implicit and explicit (via area=yes tag) area semantics and multipolygons (this should be reasonably future proof) The other issue with the changes is that a lot of "relation" type specifications have been replaced with "multipolygon", which is clearly correct for landuse, natural etc., however stops matching with site relations for amenities and similar. Given that site relations are at least currently not that popular not a big issue, but still annoying. I haven't opened an issue yet since somebody might have a far better idea on how to resolve the issue. Simon
signature.asc
Description: OpenPGP digital signature
_______________________________________________ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
