Hi I see that you added "Blue Star Memorial Highway" to the name tag of I-35. This is not the actual name of this highway and should not be used in the name tag. You will notice that there was already a `official_name` tag with the same appellation. This is the generally approved way to use these memorial names.

Are you sure this is correct location for this beach? There doesn't appear to be much sand on any of the imagery.

There does seem to be a beach about 200 yards NE of this location at the end of a service road.

Hi, I noticed that you upgraded CR 70 to trunk (along with CR23 and MN 50 in other changesets). In the original discussion of mapping a trunk network that was had among Minnesota mappers (see osm.wiki/Minnesota/Minnesota_highway_classification#Trunk_highways for a summary) this route was not included. Was there a subsequent discussion that came to a consensus to add this section as trunk?

Fixed

Thanks for the note, after some digging I changed the name to Hamlin Lake, based on the name of the dam from authoritative US Army Corps of Engineers site: https://nid.sec.usace.army.mil/#/dams/system/NC01383/summary

I would recommend adding cycleway=shared_lane for these streets if they are signed as designated for bicycles (without bike lanes) and add the correct speed limit (maxspeed=X) as this would be more useful for bike routing.

Looks good!

I would probably use the newish tag footway=link osm.wiki/Proposal:Tag:footway=link

Alternatively, use a unmarked crossing.

One more suggestion would be to add curbs (barrier=kerb) where the pathways enter roads/parking lots.

Hi, I was curious about your adding the name Khemnican to this node. A brief internet search suggests that this was a name used for a band of Dakota present in the area in the 19th century. However, I've not seen any evidence that the name is used for the city. I think such a name would be acceptable if the Prairie Island Community used it officially to refer to the city, but a quick search of their website sees no reference to its use. I apologize if I have missed any references.

I was just about to add this cyclepath. Nice!

Looks great! One minor suggestion, the address:state tag should use the capitalized state abbreviation, i.e. MN.
Thanks for improving the map!

Thanks for adding to the map. This is an great edit, but I would change a couple tags, based on your great changeset comment. If access is not allowed, I would change the access tags from "permissive" (which means access generally allowed, but over private property) to "private" which means that only the property owner (BNSF in this case) or those they give explicit permission to can pass.

Second minor comment is that the "opening_hours" tag is probably reversed (since the gate is basically always closed) and given the access tags, is not needed.

Thanks for improving the mapping of the trails along the river. I think some of the parts of the main trail where you have two separate ways (one cycleway and one footway) may actually be better represented as one way using cycleway=yes, foot=designated, segregated=yes as noted on the wiki: osm.wiki/Key:segregated

I deleted the spurious way

I don't know the details of this particular establishment since I haven't visited, but many businesses will sign details about owners' identities. In the US it is perfectly legal to do so, as is creating databases about such information.

I posted a question here and tried to be as fair as possible for someone with a point of view! https://community.openstreetmap.org/t/how-to-tag-the-surface-of-highways-that-are-compacted-crushed-limestone/101824/1

Seems like a good idea.

I don't feel like you understood my previous post. The surface tag represents a condition of a surface. The condition is the outcome of both a process and a material and that can vary. surface=crushed_limestone is a material and doesn't represent the surface well. as a sole tag surface=compacted is better.

Adding additional information for the.surface is accepted for other surface tags, like stepping_stones and gravel, so I don't see why the same wouldn't be true for compacted.

The reason I included both tags is that the `surface=compacted` reveals a process, while the `compacted=crushed_limestone` refers to a material. The combination of material and process gives more information than either alone. Regardless, surface=compacted is correct and more commonly used. It is also important for routers to know that condition.

Would you feel better if I used a different tag, such as`compacted:material` to indicate that the compacted material is crushed_limestone?

Why did you make this change, especially without notifying the original editor (me)? `surface=compacted` is the correct tag for these roads. While `compacted=*` is not a currently accepted tag, it does not do any damage to add a detail to the accepted tag on these types of roads.

Regardless, if I (or someone else) is incorrectly tagging something, it is polite to alert that person rather than just mechanically change things to your preference.