Suggestion: new category for trees? #8324
Comments
|
I find this difficult and we may need help from a botanist as there are some common trees that are not easy to identify specific species |
I don't understand. We would use already identified species. If someone tagged a tree as species=Ginkgo biloba, NSI would suggest to add leaft_type=broadleaved and/or leaf_cycle=decidous and/or species:wikidata=Q43284 If someone tagged a species=Ginkgo biloba as leaf_type=needleleaved it would suggest to fix it with leaf_type=broadleaved and so on. |
|
This is a duplicate of #94. I see what you mean about the incomplete tagging creating work for StreetComplete/Every Door users. But are we sure that NSI-generated iD presets are the best solution for that issue? For most if not every species, the leaf cycle and leaf type are always the same across all individuals of the species, so an automated mass edit or MapRoulette challenge would be just as accurate and much more efficient. Ginkgo biloba and palm trees probably deserve their own special presets in id-tagging-schema just because they’re so unusual. That is, if anyone can agree on how to tag palm trees… |
This is probably a reference to common names like, say, “pine” or “banana” that can refer to various species in a genus or family. |
This is a good point, and something we could do with NSI right now, if people would find it useful. Here are the current common Under our current practice of collecting values used more than 50 times, we'd collect about 1500 species from the OSM planet file, then volunteers would need to match these to their appropriate Personally, scrolling through this list, I don't know what most of this stuff is, so I can't judge whether the tag values are useful or not. For me, it's not like brands or transit operators where I can look up what these values are. But I'm definitely open to the idea of adding a "species" tree to NSI if other people want to do the work. |
Isn't this true also for brands? An automated mass edit could add brand:wikidata to every McDonald's without it. The problem is that automated mass edits have guidelines to be followed, and MapRoulette challenges of this kind are considered automated edits as well.
Let's take the most used value, species=Acer platanoides. Just adding this NSI entry would affect 60091 elements! Only 678 elements have both species:wikidata, leaf_type and leaf_cycle, it's the 1.2% of the total. And this is 1 species value alone. Imagine the improving this check could have on the database in trees mapping. |
Maybe 50 occurrences is too low a threshold for a tree, but even with 1000 occurrences, it's 10 pages (it seems that standardizing 200-300 plants in the early stage of the project is an acceptable amount of work)? |
|
I have 50 entries ready (more will follow in the next days according to my free time) to start populating the database in case the suggestion will be implemented: species;species:wikidata;leaf_cycle;leaf_type edit: 8 more: Acer palmatum;Q269224;deciduous;broadleaved |
This isn’t true for all brands. Just look at all the NSI entries that require locationSets or disambiguators in their names. Anyways, I’m not arguing against pairing
Would it be only one NSI entry? What would be the preset’s name (since this is the name suggestion index)? If the preset is simply named Acer platanoides, no one but a botanist would find it. If we name it “Norway maple”, then only English speakers would find it, while Spanish speakers in Spain would see English all over the preset list. |
and others
Hi, I noticed there are many trees that have species=* and/or species:wikidata=, but don't have leaf_type= and leaf_cycle=* tags yet. Often this makes a quest appear on StreetComplete, or such trees are marked as incomplete information on Every Door ecc. wasting contributors time to add an information that is - potentially - already there.
Do you think it could be a good idea to have a new category for trees, that based on species=* and/or species:wikidata=* values could suggest the correct leaf_type and leaf_cycle?
This could also help finding errors, such as a species=Ginkgo biloba tagged as leaf_type=needleleaved ecc., so it could serve as QA as well.
The text was updated successfully, but these errors were encountered: