According to Taginfo:
`genus=*` has 1,486,071 uses, vs `taxon:genus=*` with 6,446.
`species=*` has 1,948,089 uses, vs `taxon:species=*` with 2,462.
`family=*` has 3,666 uses, vs `taxon:family=*` with 55,815 total; minus the 54,925 `taxon:family=Arecaceae` which were almost all added in just two changesets, leaves just 890.

In other words - `taxon:*=*` is much like `contact:*=*` in that its usage is orders of magnitude less common than the non-prefixed, entirely synonymous, much more popular alternatives.

The Wiki page clearly describes taxonomic tagging with the use of the `genus=*` and `species=*` tags and explains in the section about palms that neither of those keys would be accurate because "palm" is a family, not a genus or species.

From my understanding, the way I have tagged the palm trees (`family=Arecaceae` + `family:en=Palm` + `family:wikidata=Q14080`) is the most accurate approach.

Refer to this thread on the forums, where these tags were discussed: https://community.openstreetmap.org/t/leaf-type-palm-is-anything-wrong-with-it/109646

Hi @user_5359 - is there some issue you're pointing to, or are you just sharing additional info?

Hi AndreaDp271 - please note that any changes to large relations (such as the United States, as this changeset modified) necessarily result in world-spanning bounding boxes and it is impossible to avoid this, so leaving changeset comments suggesting to use smaller bboxes does not make sense.

Apologies for the duplicate replies - OSM was returning a Network Error when I clicked Comment and not showing that it had been posted. :l

I haven't checked every node that was removed, but in general I agree with @Ponderosopine here - @bdiscoe, you should not recklessly use the Simplify tool to reduce the detail of someone else's contributions. There's an argument to be made for using a value of 0.01 m to remove truly redundant nodes, or using the tool on imports with "fake" accuracy / interpolation geometry, but 0.3 m is definitely high enough to be destructive of accurate contributions.

I haven't checked every node that was removed, but in general I agree with @Ponderosopine here - @bdiscoe, you should not recklessly use the Simplify tool to reduce the detail of someone else's contributions. There's an argument to be made for using a value of 0.01 m to remove truly redundant nodes, or using the tool on imports with "fake" accuracy / interpolation geometry, but 0.3 m is definitely high enough to be destructive of accurate contributions.

I haven't checked every node that was removed, but in general I agree with @Ponderosopine here - @bdiscoe, you should not recklessly use the Simplify tool to reduce the detail of someone else's contributions. There's an argument to be made for using a value of 0.01 m to remove truly redundant nodes, or using the tool on imports with "fake" accuracy / interpolation geometry, but 0.3 m is definitely high enough to be destructive of accurate contributions.

Hi, and welcome to OpenStreetMap!

It seems like this changeset includes moving some artwork in Seattle away from its actual location, even though the majority of your edits are in a completely different area.

This is a pretty easy error to make - while navigating around the map, sometimes things get accidentally moved. That's ok - we all make mistakes, especially when starting out!

I have fixed the location in changeset/169875001

Happy mapping!

Thank you for providing the details on what caused the issue! :) We all make mistakes, and that's okay.
Happy mapping!

I'm not sure how the bridge went from `surface=wood` to `surface=asphalt` in my changeset changeset/166766038 - thanks for catching and fixing that. :) Happy mapping!

I check with this opening_hours evaluation tool: https://openingh.openstreetmap.de/evaluation_tool/ (and ignore all of the public holidays warnings)

Hi! I noticed that this changeset was tagged for review.

Seems good to me - `opening_hours=*` format here is valid.

An aside - I added some additional details in changeset/166090218

Happy mapping!

I think `utility=electric` is probably close enough of an unneeded duplicate / typo to warrant a simple global fixup edit like this, so I see no need to revert it.

Hi! Hmm - do you know what the default speed limit for these links is if it is not signed?

Correct changeset comment is: Add fire hydrant, bollards, guard rail, and sign.
Source: Bing Aerial Imagery;King County Orthoimagery;Mapillary;Bing;data.seattle.gov

Hi! I made some additional changes in changeset/165782342 - once the routers update, they should hopefully no longer route pedestrians north/south across this intersection using the roadways, and instead direct people to the intersection to the west. Hope that's helpful. Happy mapping!

Note - due to an issue with JOSM, this changeset caused version bumps of some elements with "phone"/"contact:phone" tags that did not actually receive any tag or geometry changes.

Hi! Interesting - the street to the north is named "2100 South" in OSM and all of the street name signs I could find nearby only say "2100 S" but then I also now see that the Tiger 2023 overlay names this road "East 21st South" - quite confusing for someone in the armchair, so I'm glad there's a local mapper to help clarify things. Thanks! Happy mapping :)

Hi, and welcome to OpenStreetMap! :)

It's great to see you getting started contributing, and thanks for using the "Review Requested" feature!

I took a look at your edit, and it does need a bit of touching up - playgrounds are mapped with the tag "leisure=playground" rather than "leisure=park" + "name=Playground", so go ahead and update those tags by removing the existing two and adding the corrected one.

There's an OSM Wiki article on playground mapping here: leisure=playground

and I use TagFinder to help me figure out what the correct tags for a feature are: https://tagfinder.osm.ch/

Try to avoid "descriptive naming" (there's a very exhaustive explanation here: osm.wiki/Names#Name_is_the_name_only)

Again, welcome - there's a lot of depth to OSM editing, and it'll take a while to learn the ins and outs - thanks for participating, and happy mapping!