Our mappers "map what's on the ground" and use "one feature, one OSM element". I agree as OSM matures and the detail of these remote areas is surveyed, we should be distinctly mapping natural features vs administrative boundaries as separate entities. I've helped with detailing natural areas in the Victorian Alps, and I can say unpicking natural tags from administrative boundaries is a lot of work! (and prone to accidentally breaking the odd poly or two in the process, sorry about that)!
It's worth the effort though, and we end up with detailed outdoor maps like https://www.openstreetmap.org/#map=14/-37.1194/146.6790 Also, we used to have one massive natural=wood polygon stretching hundreds of kilometres from the outskirts of Melbourne up to the NSW border, which meant any breakages during editing would lose half a state's worth of tree cover. Chunking this down into several polys has made localised natural features detailing far more manageable for editors. On the topic of natural features, can anyone advise the recommended largest size on what a multipolygon can be? I remember some editors and renderers used to struggle with thousands of members in the relation, but I can't seem to find the recommended maximum anymore https://josm.openstreetmap.de/ticket/11101 You can also use Overpass Turbo to query natural features, eg https://overpass-turbo.eu/s/1bRC Regarding administrative boundaries, developers, is it possible for the ones that were imported many years ago to be re-validated somehow? Some form of scheduled script to check that the OSM data still matches the official open source dataset to prevent editing drift? ..Brendan On Fri, 8 Oct 2021 at 16:35, Kim Oldfield via Talk-au < talk-au@openstreetmap.org> wrote: > On 8/10/21 2:17 pm, Andrew Harvey wrote: > > On Fri, 8 Oct 2021 at 09:22, EON4wd <i...@eon4wd.com.au> wrote: > >> Question, How can I identify this person so that I can contact them to be >> able to find out what they are thinking? >> > If you're using the default iD editor, select a feature, then in the > bottom left there is a link to view on OSM, which shows in the left panel > who changed it last, but you can select "View history" at the bottom of the > panel to see what and who changed it. > > > Or, when looking at openstreetmap.org, click the "Query features" arrow, > then click somewhere in the Grampians, for example > https://www.openstreetmap.org/query?lat=-37.20902&lon=142.51812 > Under Enclosing features, click on "Protected Area Grampians National > Park" which takes you to https://www.openstreetmap.org/relation/2703380 > You can click "View History" at the bottom of the relation page. > > To see a nicely formatted table of the changes you can put this relation > ID into OSM Deep History which takes you to > https://osmlab.github.io/osm-deep-history/#/relation/2703380 > Here we can see that it was initially natural=wood, which was removed on > 15/1/2013, restored on 8/11/2015, and removed again on 12/12/2018. This > most recent changeset can be viewed at > https://www.openstreetmap.org/changeset/65393733 . Before making changes > read the change comment and discussion as you aren't the first to query > this change. > > Regards, > Kim > > _______________________________________________ > Talk-au mailing list > Talk-au@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-au >
_______________________________________________ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
