OpenStreetMap
Gregory Peony's Comments
| Changeset | When | Comment |
|---|---|---|
| 152917389 | Thanks for the comment and source. This building has square corners, Well done.
|
|
| 152917347 | Thanks for providing a source and comment. Press q to square corners.
|
|
| 152917316 | No source. Press q to square corners.
|
|
| 152917241 | Thank you for providing a change-set comment and a source. please press q to square corners, this shouldn't move the nodes associated with the 45 degree wall as it is significantly off-square. Idealy write full sentences in your change-set comments.
|
|
| 152917172 | No source. Assuming that the imagery is well geo-referenced. This building's footprint should be moved to the NW, because even though the building is casting a shadow on itself, it is possible to see both its North and West sides from this imagery. You are mapping the building's footprint i.e. where its walls touch the ground. Although the roof can help you to get the right shape you are not mapping the roof per se. The parts to the SE of the roof should be added before the entire footprint is moved to the NW. You added an unnecessary node to the SE of this footprint, and in this case it appears that it will result in that wall not being straight when rendered on the map. Please press q to automatically square the corners of buildings as it more practical and accurate than drawing 90 degree corners by eye.
|
|
| 152916339 | No source. The park and sidewalk in the SW share a common node that I think you added accidentally. Generally highways and boundaries/areas like this should not share common nodes. Hold ctrl when adding nodes in ID if you want to avoid them snapping to other features.
|
|
| 152916266 | No source.
|
|
| 152916228 | You did not provide a source for this change-set.
|
|
| 152916212 | It's good that you modified this POI, instead of deleting it and adding a new one in its place. This way the history of that node/POI is easier to follow.
|
|
| 152916152 | Good practice when submitting changeset comments is to include the location of the feature you edited, for example the country and city, or state. It can help other mappers keep track of local edits.
|
|
| 152916133 | It is accurate to delete features that no longer exist. Your change-set comment is informative: thank you for submitting one. It's also good that you included a source. Just know that local knowlege can refer to things like 'my friend told me that a resturaunt I know of shut down', If you have actually seen for yourself that the buisness is no longer opperational, then you can state your source as "survey" instead which carries more credence.
|
|
| 151274695 | Why did you revert and modify these building footprints?
|
|
| 150012776 | a significant portion of way/531395324 is a waterway. you added a highway across it but not the bridge/culvert. other crossings should be marked as ford=yes. The waterway is intermittent
|
|
| 150012776 | The highway-highway crossing warning simply means that highways are intersecting and do not share a common node. |
|
| 150012776 | This is not the correct way to use the crossing key. The key is intended to mark the crossing of ways with varying traffic e.g. a train and a motor vehicle. Different values of highway sharing a node do not count, intersecting ways intended for the same transport mode do not count: these are junctions. Reference osm.wiki/Crossings. |
|
| 151886895 | Please, write a changeset comment before the hashtags. Intersecting highways must share a common node unless they are on seperate layers i.e. physically seperated, one above the other.
|
|
| 151886662 | Highway junctions must share a common node. Please, write a changeset comment before the hashtags.
|
|
| 151886526 | The nothern way you added created a highway/highway overlap. Please add ways accurately. Please write a changeset comment stating what you did before the hashtags
|
|
| 151885821 | You created highway/highway overlaps without common nodes. Please write a changeset comment (ideally before the hashtags).
|
|
| 151885450 | You created intersecting highways which do not share common nodes. Navigational software may/will not recognise the junction and so will not route correctly or in the most efficient way. The highways should be better alligned to imagery.
|