Hi,
thanks for edits! Just noticed that you forgot to split the sidewalk at Fairfield Avenue and tag it as crossing.

Cheers

Welcome to OSM!
Just wanted to make sure that the data is used with permission from their owner. OSM has a strict policy on which data can be imported and license compatibility.

Cheers.

Checking the UPSP ZIP code lookup there is now recommended city name "STORRS MANSFIELD" though "STORRS" is still accepted.

So this could be potential value to change. The question is if this name is actually used locally when sending mail. UConn website for example still suggests Storrs:
https://studentmail.uconn.edu/properly-addressing-packages/

Welcome to OSM and thanks for your edits.
Just to note, general agreement is to label roads as private access only in cases when there is a gate or a No trespassing sign.
If there is just a private road sign, we add ownership=private and access is set to permissive or yes.

Cheers

Name tag is for common local name. And Storrs is the most common name for this community/CDP in CT.
If the Storrs-Mansfield is an actual official name (although it seems it only appears in USPS documents) then it can be used in official_name tag.

Hi,
Given the prior discussion (changeset/158825125) and discussions on Wikipedia, please refrain from any further changes to Storrs and Mansfield names and addresses.
Thanks.

I fixed tags for the survey point

node/13449219098

Hi,
When looking at NH GIS parcel map, I can see the street labeled there. Are you sure that the street does not exist?

Hi,
are those trail physically gone?

That is just how it is implemented in one map project. You have to look at our OSM documentation, because that is what other map projects will use as a reference:
osmc:symbol=*

"waycolor - Name of the color in which the route path itself should be painted."

And yes there are maps that use it:
* https://osmapp.org/
* https://mapy.com
* OSMAnd app
* https://www.wanderreitkarte.de/
etc.

Thanks for the explanation. That first part of osmc:symbol tag is to indicate what color the route should be "painted" on a hiking map.

Since this tag is supposed to be machine readable and not interpreted directly by humans, can we stick to the underscore "_"? I introduced this character because it is already used as a value separator in the tag itself and hyphen adds another complexity.

Hi David,
just a question. What is the purpose of changing "white_black" to "white-black" in osmc:symbol?

Well the problem here is that you are "tagging for renderer". You are bending the established rules of mapping so that something appears on a particular map.
Route relations are used for marked trail, not just for any path in a forest.

route=hiking

osm.wiki/Tagging_for_the_renderer

Hi David,
I think this is not correct. Those trails are not marked as a route in the terrain. This just creates confusion for users.

Sorry, I haven't inspected the changeset properly.

That seems to be just grass growing differently due to different condition of nutrients.
For historical data we have https://www.openhistoricalmap.org/ though.

Hi,
there are no signs of any road on the street level imagery, just a regular lawn. It's better not to add the driveway, but you can mark that the sidewalk does not have a curb.

You are correct that we can add information about things we see around us.
The problem here is that you took the information from a database that does not allow this and you corrected the position using another restricted source (streetview).

Folks on Slack seem to agree that this will unfortunately have to be reverted. Sorry that your work will be affected, but we just have to be careful so that OSM will not be accused of stealing data.

The link is public, but the use of the data might not be. Can you please contact them and ask them is it is allowed to use their camera information in OSM?

On their website there are some restrictions stated:
https://ctroads.org/termsandconditions

"Copyright Notice – Copyright and other relevant intellectual property rights exist on all content relating to ctroads.org’s services and the full content of this website. ctroads.org, including all content, is protected by American and worldwide copyright laws and treaty provisions. You agree to comply with all copyright laws worldwide in your use of this website and to prevent any unauthorized use of the content."

"... however, that you may not, directly or indirectly:
....
Sell, reproduce, modify or attempt to modify the content in any way or reproduce or publicly display, perform, or distribute or otherwise use the content for any personal, public or commercial purpose, including without limitation use of the content on any other website;
....
Use any robot, spider or other similar kind of automatic program or device, or manual process to monitor, copy, summarize, or otherwise extract information from this website;"

"A link may be established to the following home page of this website: http://www.ctroads.org Links may not be established to any other pages on this website without ctroads.org’s prior written permission."

Thanks for replying.
Assuming it is under public license then it should be fine.
Could you them please add that public database name as a source before submitting your changesets.

Also google streetview is not allowed for adding data to OSM. You are free to use Bing streetside though.

Cheers