Mashin's Comments
| Changeset | When | Comment |
|---|---|---|
| 159473871 | about 1 year ago | That's great. I am glad to hear that.
|
| 159473871 | about 1 year ago | Hi,
|
| 159473871 | about 1 year ago | Thanks for replying. I see several problems here. 1) You didn't follow any of the steps from the import guidelines. At minimum, please create an import documentation page on osm wiki where you detail where you downloaded the data from, how were they processed, where you asked for permission and if the license is compatible. Then post an announcement message to the community forum and answer any comments there might be. This is all outlined in the guidelines linked by Mateusz. 2) The license message you linked is from year 2020. They might have given permission at that time, but we cannot assume it is forever. Please double check that the license is public domain or CC0. 3) The message says that Westchester County GIS needs to be credited. I don't see their name anywhere in the source tag or nor even in the comment message. 4) After you've gone through that all imports have to be marked in this list: osm.wiki/Import/Catalogue If you have some questions you can contact us on Slack or Community forum. |
| 159675717 | about 1 year ago | This changeset was corrected.
|
| 159675810 | about 1 year ago | Hi,
In this case it was this node: node/9008446356
Cheers |
| 159473871 | about 1 year ago | Hi,
|
| 159483086 | about 1 year ago | Sure. I also think that the current values scale very poorly for large countries like US, but how does it justify to do such dramatic change that will make the trails disappear from some maps? I missed discussion about this. What is the idea for network values for the rest of the hiking trails countrywide? Are those values going to fix the hierarchy issue? Does that mean that global hiking map project will have to hardcode network values in order to infer hierarchy?
|
| 159538517 | about 1 year ago | ok. Thanks for clarification. |
| 159483086 | about 1 year ago | Hi Quincy,
|
| 159504192 | about 1 year ago | Hi,
|
| 159538000 | about 1 year ago | Hi,
You can see it clearly if you switch the background imagery to 'CT ECO Orthoimagery (2019)' or 'Esri World Imagery (Clarity) Beta'. https://learnosm.org/en/hot-tips/imagery/#changing-the-background-aerial-imagery |
| 159538275 | about 1 year ago | Hi,
|
| 159538517 | about 1 year ago | Hi,
|
| 159546248 | about 1 year ago | Hi,
|
| 159546265 | about 1 year ago | Hi,
|
| 159226480 | about 1 year ago | When you switch the background, you will see that this parking lot has still some hidden parts that are obstructed by trees. |
| 159226480 | about 1 year ago | Welcome to OSM and thanks for editing!
1) When drawing a parking lot area, try placing new nodes at every corner of the parking lot and make sure the line traces the outline precisely. Try to avoid cases where the line would cross grass, buildings or other objects that are not part of the parking. 2) I suggest you switch from the default background to 'CT ECO Orthoimagery (2019)'. It was made in spring when the tree leaves are gone and you can see the parking lot outlines under tree canopies better.
Let me know if you need help.
|
| 159069334 | about 1 year ago | Thanks for checking |
| 158825125 | about 1 year ago | Thanks for the pointers. I briefly read through the discussion there and the arguments there pretty much summarize my thoughts. In the mean time I have moved Storrs-Mansfield to offical_name. |
| 159069334 | about 1 year ago | Hi,
|