OpenStreetMap
ZLima12's Comments
| Changeset | When | Comment |
|---|---|---|
| 119553965 | Changeset looks good, but in the future, for driveways and swimming pools on private property, please add access=private.
|
|
| 119553865 | It's been a little while since I've been on this trail. What exactly does this part look like? Does the wood carry the trail over some kind of water? If so, maybe it should be bridge=boardwalk or something similar.
|
|
| 119357341 | Are you sure? It looks like it extends past where you truncated it to.
|
|
| 119315588 | Thanks, good changeset. Just know that if you're sure the name is incorrect, you can also delete the corresponding "tiger:" tags. This helps keep things clean.
|
|
| 51242467 | Hi, You added destination:street=Croton Avenue, but this is not signed. |
|
| 110635274 | Hi, Please don't put this kind of thing in the name. Instead, on the ramp, you should put "destination:ref=I 95 East". Thanks! |
|
| 119197604 | Good, just not sure about the overlapping baseball and soccer fields. This is a pretty common scenario, so I wonder if there's an accepted tagging approach.
|
|
| 99411186 | Hi, I think you've been drawing your guardrails backwards. The wiki says: Guard rails along roadways typically have an inner and outer surface; the inner surface is smooth and faces the roadway, while the outer surface is typically where vertical struts are connected (see example picture in info-box). If there is a clear inner/outer demarcation to the guard rail, construct the line so that the right side is inner and left side is outer. You seem to reliably be drawing it in the opposite way. Was this coincidental, or maybe you misinterpreted the wiki page? Also, if you're going to be adding guard rails like this, please make sure that they're not glued to things beneath it, and make sure to set the layer tag on the guard rails. |
|
| 115544744 | I see now that you were doing this because you wanted to show that those parts of the path were covered. I get that, but the wiki page says "Do NOT use [covered=yes]...For objects in tunnels or passing under linear bridge features where vertical ordering is established by layer=* in combination with a suitable tag such as bridge=* or tunnel=*.". I see that you reverted the covered=yes tagging, but left the nodes glued. I'll unglue them.
|
|
| 115544744 | Please do not glue together things on different layers. You glued the I-990 bridge to Ellicott Creek Trailway.
|
|
| 119175343 | Hi, This is definitely an improvement, but the correct tag (or at least the tag that is vastly more common) is just leisure=swimming_pool (no water tag).
|
|
| 118279536 | highway=construction is meant for things that are currently being worked on by a construction team. If it's just closed, and not being worked on, other tags would be more appropriate.
|
|
| 118283224 | Good changeset, but it looks like you left the `building:flats` tag on the exterior way. This is duplicate now that it's on the relation.
|
|
| 119093331 | Disregard my previous comment; it was an issue with a library iD uses, which I have now submitted a fix for.
|
|
| 115446690 | ||
| 115446690 | Fixed in changeset/119140030 |
|
| 115446690 | That's certainly an issue. Not too familiar with iD these days, but I'll look into this. |
|
| 115446690 | Something fishy seems to be happening with this; I've seen several mappers all make this change. |
|
| 115446690 | Why did you change `operator` to `Worchester County` on relation/10039511 ? |
|
| 118650404 | Hi, Looks like you placed two nodes on top of each other. Try to make sure that you're not duplicating like this in the future.
|