Your approach looks good to me. In regard to tags : I understand that the intent of the IUCN categories is that class I areas are generally reserved for scientific and research purposes or very limited visitation by non-scientific personnel. However, in some places including South Australia, some category I areas appear to be accessible by the general public. I have never noted any class II, III, IV etc areas that have not been available for leisure (except short-term such as fire emergencies). I suggest all reserves except class I are probably eligible for leisure=nature_reserve but class I areas should be tagged that way only if separately confirmed that they are available to the general public for leisure purposes.
In regard to abbreviations, OSM generally avoids abbreviations and I think it is probably safest to avoid abbreviations unless there is good reason to do otherwise and the abbreviation is clearly understood by all users. An instance where it is probably appropriate is the operator of national parks in New South Wales self-identifies as "NSW National Parks and Wildlife Service" and I think we should use its own way of identifying itself even though it abbreviates the name of the state as "NSW". It sometimes uses "NPWS" but this is only after first using its full name and, in isolation, the abbreviation would not be understood by all users and I think "NPWS" would be inappropriate in OSM. Looking forward to seeing the 2016 data. On Sat, Mar 18, 2017, at 02:04 PM, Andrew Davidson wrote: > Using the 2014 CAPAD data I have created example osm files for > Queensland for your perusal and comment. The files are available here: > > https://drive.google.com/drive/folders/0B7Y8oxDzqhyNMkFCRWhLQmIwZzQ?usp=sharing > > The whole state is in capad2014_qld.osm.gz and I have attempted to split > the data up into geographical clusters with the view to using this as a > mechanism to split the import task up so that more than one user can > work on it at a time. The method for splitting up the data needs a > little refinement as it is making them rather uneven. You can see from > this list of the number of nodes, ways, and relations: > > capad2014_qld_batch00.osm.gz : 6904 94 19 > capad2014_qld_batch01.osm.gz : 11156 183 36 > capad2014_qld_batch02.osm.gz : 0 0 0 > capad2014_qld_batch03.osm.gz : 42331 946 110 > capad2014_qld_batch04.osm.gz : 39632 996 124 > capad2014_qld_batch05.osm.gz : 4323 122 15 > capad2014_qld_batch06.osm.gz : 0 0 0 > capad2014_qld_batch07.osm.gz : 173 9 1 > capad2014_qld_batch08.osm.gz : 8976 152 9 > capad2014_qld_batch09.osm.gz : 6276 150 15 > capad2014_qld_batch10.osm.gz : 42624 595 52 > capad2014_qld_batch11.osm.gz : 51852 1231 131 > capad2014_qld_batch12.osm.gz : 16943 259 40 > capad2014_qld_batch13.osm.gz : 0 0 0 > capad2014_qld_batch14.osm.gz : 6694 143 31 > capad2014_qld_batch15.osm.gz : 22411 334 46 > capad2014_qld_batch16.osm.gz : 40351 1719 42 > capad2014_qld_batch17.osm.gz : 3507 94 20 > capad2014_qld_batch18.osm.gz : 4519 91 20 > capad2014_qld_batch19.osm.gz : 2071 47 8 > > that some batches are going to be a lot more work than others. > > Some notes about the tagging: > > * I made up the tags very quickly so think of them as preliminary. > * Turns out that the unique identifier is also unique to the edition of > CAPAD ie: ref in 2012 is not the same as in 2014, hence capad2014:ref. > * The note:capad on some ways is not intended to stay in OSM but has > been added so that users can tell why some ways have been split in their > batch (it's required for an area in the adjacent batch). > * The nodes with a note tag have been added as JOSM complains if a > segment is longer than 15km (also the note needs to be worded better). > > Thing left to do: > > * Develop a tagging plan. Needs to wait for the 2016 edition to get > published so we can see what data will be available. Also need to think > about which IUCN categories get a leisure=nature_reserve tag. > * Sanity check the names of the areas (eg: some states use > abbreviations) and the operators. > * Come up with a way of task managing (only a problem if there is more > than one mapper working on the import ;-) ). > * Figure out how to do QA (or more correctly QC). > * Write up a import wiki page. > * Run the gauntlet that is the Imports mailing list. > > _______________________________________________ > 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
