Mashin's Comments
| Changeset | When | Comment |
|---|---|---|
| 118177208 | Sorry, there was a recent road reclassification in CT and I am just trying to prevent it from getting mixed up again.
|
|
| 117919249 | Hi and thanks for editing OSM! Just a few corrections on the way you are editing the data:
2) Don't add hole number into name for golf=hole objects. Those belong to ref= tag. 3) When you are drawing buildings, please trace the exact building shape from aerial imagery and press Q to adjust the corner angles. Don't just draw a random quadrangle at the building location. 4) When editing an object, adjust its shape by dragging existing nodes or adding new nodes. Don't delete whole objects and replace them with new shapes. Not complying with community standards of mapping will result in blocking of your account.
|
|
| 117997018 | Hi zzmzzm,
|
|
| 117589566 | Thanks Andrew! |
|
| 117853638 | I assume you are talking about this map from Hamden GIS: https://server2.mapxpress.net/webdata/Hamden/Zoning_Map/Hamden_Zoning_Map.pdf Most likely those parcels are left for a possible extension of the exiting roads in case of a further residential development in the area. This is a bit of a controversial topic with many discussions (osm.wiki/Talk:Parcel). I've mostly seen people being against including parcel/zoning data into OSM, because how much effort it takes to keep it up to date.
|
|
| 117867478 | fixed it. |
|
| 117853638 | Hi David,
|
|
| 117744738 | Hi,
|
|
| 117589566 | Hi Andrew, thanks for the great work on hiking trails. CT is starting to look really good.
Current idea is that if the trail does not exist, don't map it. If it exists and has sign prohibiting use, add `access=no`. If path is clearly not made for official use mark it `informal=yes`. More in depth information is summarized on this wiki page osm.wiki/United_States/Trail_Access_Project cheers |
|
| 117581724 | Hi zzmzzm. Actually the path is there. You can also check on Maxar premium imagery, which is the most up to date. Cheers |
|
| 117373881 | Sorry I was restoring some of the relations that you deleted before and in the process I converted some blazed trails to relations. But moved all the information to relation so there is on data loss. |
|
| 117282596 | Makes sense, thanks for explanation. Yeah there is no good documentation and a boundary between area where people live and a forest is often blurry. I'd say that if there is a big chunk of wooded area or other land use, it's better exclude it. |
|
| 117282596 | Hi kylenz!
What are you trying to achieve? Is this some kind of larger project? |
|
| 116884624 | Perfect thanks! Do you know by any chance where is that historic district located? |
|
| 116884624 | Hi and thanks for your edits. Just a question, why do you think it is necessary to remove "Woodstock Hill Historic District" and all the address points? |
|
| 116645557 | Hi Erik, nice job! Though just mind that you accidentally turned Elm Street into a driveway. :) I already fixed that. |
|
| 116407978 | Hi and thanks for editing!
I would say that if there is another road (or object) that leads over the casino, then more safer is to split the road into fragments and assign layer=1 to the fragment that goes over the building. This way we would avoid having above/below conflicts at other parts of the large objects.
|
|
| 116199354 | Immediately stop deleting any objects!!!
|
|
| 116000097 | Hi and thanks for editing. Just a few comments from what I noticed. golf=green should not be overlapping with golf=fairway. This can be done by making fairway a multipolygon. There is a picture here that explains is a bit better: leisure=golf_course#Common_mapping_pitfalls
|
|
| 115809731 | Hi dkwolf and thanks for editing! When you removed the old school shapes you also deleted tons of other tags like address, contact phone, website... Are those information outdated or are they still ok? Also I saw that sometimes you change names from e.g. XYZ Elementary School to XYZ School. Do you think it would make sense to keep those old names as alt_name? |