CurlingMan13's Comments
| Changeset | When | Comment |
|---|---|---|
| 160044261 | 12 months ago | Structure in name is descriptive and should be removed. |
| 160044261 | 12 months ago | proper capitalization should be used.
|
| 160408915 | 12 months ago | What spurce did you use? |
| 160436939 | 12 months ago | What source did you use? |
| 161222531 | 12 months ago | What source did you use? |
| 160457944 | 12 months ago | Is it a memorial or is more of an information board? |
| 161040534 | 12 months ago | What source did you use for this info? |
| 160761884 | 12 months ago | Changeset reverted. We use access tags to denote it is private access and not publicly accessible. You can read more here:
|
| 160814129 | 12 months ago | Changeset reverted. We use access tags to denote it is private access and not publicly accessible. You can read more here:
|
| 160835916 | 12 months ago | Changeset reverted. We use access tags to denote it is private access and not publicly accessible. You can read more here:
|
| 160736103 | 12 months ago | Hello. You got rid of the building? That doesn't seem right. |
| 157060093 | 12 months ago | What jhaluska80 said. It's very frowned upon to snap/connect landuse/landcover to roads. makes it a PITA to update. |
| 160804382 | 12 months ago | Looks like some railway tags were left on an orchard relation line: |
| 160646674 | 12 months ago | Changeset reverted. We use access=private to denote a road as private. |
| 113168728 | 12 months ago | When adding business names, do not describe what they make in the name. Unless of course, it is their official name. I know, old changeset. But I'm just noticed it. :) |
| 160327226 | 12 months ago | Good golf edit!
|
| 160327993 | 12 months ago | Don't add tennis courts as buildings
|
| 160329662 | 12 months ago | "Lollipopping" has been fixed. Use multi-polygon relations.
|
| 160328451 | 12 months ago | Do not add tennis courts as buildings. This is not just a whiteboard for your golfing game. This is a real map we use. |
| 160330097 | 12 months ago | Please don't lollipop ways. If something has a "hole" in it, then a multipolygon relation should be used.
|