Hi there,

I see you added the address unit of A, but you put the tags on the building. Does the urgent care occupy the entire building?

Normally the fishing tag would go on the ways, not the relation, so that the ways can be split at the places where fishing is restricted.

Bullet 3A of https://www.flipsnack.com/sdgamefishparks/2024-south-dakota-fishing-handbook/full-view.html?p=24 says there's a section in SD that prohibits fishing in the winter.

No response, reverted in changeset/156522530

Hi there,

Thanks for the edits! Just so you know, while it's allowed to create tags like "xc trail", it's best to look for an alternative that already exists, otherwise no one else will be able to understand it.

In this case, in order for others to understand that there are trails here, you need to map the trails separately, and add the correct tags to the trails.

You can map the trails as highway=path (highway=path), and if you want to create the loops, you can do that as a route relation (route=hiking)

Hope this helps, let me know if you have any questions!

(and other tags)

Thanks, according to wikipedia the J1772 is a type1 charger, i fixed the tagging

https://en.wikipedia.org/wiki/SAE_J1772

Hi there,

This golf course you've created has several incorrect things, that are documented here: leisure=golf_course#Common_mapping_pitfalls as well as the wiki pages for the respective tags

1. Golf holes, tees, fairways, and pins should not have a descriptive name, they should have a ref only
2. different golf objects (fairway, rough, green) should not be overlapping
3. The golf=hole needs to be connected to the pin, if the pin is a node

Also, there's several errors elsewhere:
1. The highway multipolygons are tagged with both area:highway=footway and highway=footway, the highway=footway tag is incorrect if you're using it to represent the area of a highway

2. All of the golf=hole appear to be duplicated, for example way/1314296837 and way/1314659185
3. Some features are wrong, for example relation/18001533 is not a rough.

Could you please go back and fix these things? Thanks!

Hi there,

for node/12140867636, the capacity tag is the number of stalls, not the output. The output is specified as socket:<type>:output, where <type> is the type of charger, probably one of these: socket:*=*#List_of_socket_types

Would you mind fixing this? Thanks!

whoa, my bad, forgot a bbox on the overpass query

Hi there,

For way/1312929580 and the rest of the parking spaces, did you mean "access=customers" instead of "customers_only"?

Hi there,

Thanks for the edits! In OpenStreetMap, we always expand and write the full name of the roads, so would you mind expanding these to "Pheasant Lane" and "North Indiana Avenue"? Thanks!

Hi there,

For way/368356351, "elevation" is not a valid tag, the correct tag is "ele" (ele=*), would you mind fixing that? Thanks!

Yeah, in the grand scheme of things it's not a huge deal i guess, but it would be nice for "ele:datum" (and "ele:accuracy" as well) to be documented somewhere so that others can understand what they are.

In that case, i'm wondering what the ele:datum tag is in relation to the ele value. Are you saying that the value in ele is from that datum, rather than the standard EGM96 that ele is normally in?

So you're saying this was not an automated import?

Hello,

Was this import discussed anywhere before being imported?

Hi there,

Can you please give a source for this? I cannot find a school in this area with the name "Alamando Private Area Schools"

Hi there,

I've fixed this one for you, but in the future please pay closer attention to the rules of the maproulette task, which say if you delete the building tag from the node, you need to replace it with a more fitting tag.

Hi there,

You tagged way/9146800 as a bridge, could you please go back and split it so only the bridge over the highway is tagged as a bridge? Thanks!