aharvey's Comments
| Changeset | When | Comment |
|---|---|---|
| 173560368 | What's there now? If it's a construction site best to use landuse=construction. |
|
| 171733352 | Where was the data for these sourced from? relation/2386039 already exists so node/13133160273 is a duplicate. |
|
| 171737236 | Nice work! |
|
| 171751210 | you can add service=driveway to specify the type of service road and also driveway=pipestem to mark it as a shared driveway. |
|
| 170135554 | sorry my mistake, you've already applied that to the true boardwalk sections |
|
| 170135554 | sounds like it should also have bridge=boardwalk |
|
| 171271345 | reverting since this doesn't look right and no comment or justification was given. relation/9487066 is the route_master |
|
| 155918880 | fyi note/4618878 regarding node/7911236708/history |
|
| 166756700 | Thanks! Yes that was my mistake, fixed now. |
|
| 91082783 |
from what I can see, there's no restrictions on walking or cycling over the ford so I'll remove those access tags you added. |
|
| 170133918 | I've restored the way but changed the tags to be a private driveway rather than public street. |
|
| 170089204 | reverted |
|
| 170088980 | reverted |
|
| 170085698 | could you please provide further information about why the field is no longer there? if you provide this in the changeset comment it helps other mappers understand why the changes were made, without this justification and due to the dragged node I've reverted this changeset. it can also be helpful to map out what's there instead (if the field is no longer there). |
|
| 170085729 | I've reverted this as the only change was to drag the node, going by your changeset comment it seems like you knew something went wrong, why did you proceed to upload it then? |
|
| 169982256 | your changes resulted in a number of overlaping ways, so I've cleaned this up, however I'm not sure about the tags for each of the resulting segments. |
|
| 169898047 | Unless I'm mistaken, the data extracted for the quest only records these as "tower" so it doesn't specify if it's a chimney or a communications tower, many of the other data points are for chimneys so I think it's very likely this one is for the chimney. On the Esri imagery the shadows cast to the west, so if there was a comms tower there you'd expect to see a shadow but there's none, only the chimney. On Bing to me it just looks like some stockpiled equipment on the ground. Either way if in doubt probably best to not map it and leave a note or fixme. |
|
| 169898337 | same comment as changeset/169898102 In this case I believe it would be best to mark the comms tower as a node, and per the wiki this is likely to be man_made=mast not man_made=tower. |
|
| 169898287 | industrial=communication is considered a sub-tag of landuse=industrial, it further specifies the type of industrial landuse, so you need landuse=industrial as well. |
|
| 169898102 | Unless the tower footprint has significant area, I think it's best to map the tower as a node. The area you've traced out here should be a landuse=industrial and potentially with industrial=communication. The whole area isn't a building so shouldn't have building=yes, there does appear to be something within the site, it might be a building or it might be industrial equipment, but if you wanted you could trace it as building=yes or building=service. |