tms13's Comments
| Changeset | When | Comment |
|---|---|---|
| 141347753 | about 2 years ago | Thanks - fixed. |
| 132506108 | over 2 years ago | Thanks - that's great, and it makes OSM Inspector (Areas) much happier! |
| 132506108 | over 2 years ago | What's the purpose of relation/15475169, which has only a single "inner" member that duplicates the tags of the relation? Something is clearly wrong there, but I'm not sure of the appropriate corrective action (and aerial photos don't clarify it for me). |
| 137615379 | over 2 years ago | This change has seriously broken the heath area relation (relation/13417952). Can you fix that? |
| 136645299 | over 2 years ago | Yes, that's exactly what I mean about ways that start off identical and then diverge. I've not used an editor that adds to multiple ways simultaneously - I didn't know that there are some that can do that. I'm certainly seeing unintended overlaps and gaps between areas. And also linear features that clearly ought to be the delineation between areas (fences, walls, hedges, etc) getting out of sync with their respective areas. I always understood it to be best practice to use these boundary ways to form the areas.
|
| 136645299 | over 2 years ago | It's a judgement call whether the scrub is a single feature or not - feel free to separate into smaller relations if necessary. |
| 136645299 | over 2 years ago | The duplicated edges tend to fall out of sync when edited so that abutting areas end up overlapping or not quite meeting. This particular area was highlighted by OSM Inspector due to touching rings, so I fixed up some of its duplicated boundaries whilest editing. |
| 130152396 | almost 3 years ago | Here's how I fixed the ones you introduced here:
E.g. see the history of Loch Shiabhat:
|
| 130422061 | almost 3 years ago | Ah, great. :) |
| 130422061 | almost 3 years ago | Not sure what you mean there. Both of those stand alone and share no path with any other ways as far as I see. Which ways do you think duplicate them? |
| 130152396 | almost 3 years ago | You seem to be creating relations that are missing their outer ways. I've fixed up dozens of them lately. Any idea what's causing that? |
| 129548769 | about 3 years ago | Thanks for fixing this before I spotted what I'd broken! :-) |
| 129359632 | about 3 years ago | Yes, identical coordinates, as reported on OSMInspector. 1 metre threshold, I think. |
| 129359632 | about 3 years ago | The main reason was the numerous duplicate points in the way. The easiest way to remove those was a simple Douglas-Peucker reduction. |
| 124009084 | about 3 years ago | Fixed - thanks |
| 122763694 | over 3 years ago | Ah, yes, that's more appropriate. Thanks for improving that. |
| 111875731 | about 4 years ago | It was marked proposed:highway=no, so I removed on that basis. Feel free to resurrect it if that was wrong! |
| 69131288 | over 4 years ago | Fixed that, and a few others I found in the area. Thanks for the correction. |
| 17688175 | over 4 years ago | Looks like the track was added 3 years later, and not routed through the gate. I'll move the gate onto the track where it belongs. Thanks for the prod! |
| 108125504 | over 4 years ago | That's not an area, just an address way, for houses that all share the same postcode: osm.wiki/Addresses The car-park is just the large layby near the phone box (which no longer has a phone in, I noticed last week): node/266854132 |