Warin61's Comments
| Changeset | When | Comment |
|---|---|---|
| 126327357 | Hi,
|
|
| 104919331 | Redfern Train Staion: Train lines are at layer 0. Platforms should be at the same layer. The walk ways go over the train line .. so they should be at layer=1 - same as the road way and cycle way ... I have attempted to change this to where it should be. |
|
| 113926674 | Hi Building levels should be integer numbers not 'elevator'. There are at least 20 of these, I've only looked along the Richmond line .. I expect more of them with a complete search. ... I'll simply delete the lot? |
|
| 117349831 | Hi
Ways 1030893405 & 1030893306... |
|
| 126968374 | Perfection is hard to achieve, and even harder to maintain! As long as it is a reasonable representation of what is there I'd call it good. |
|
| 126968374 | Hi,
First the tag 'building=yes' says that the entire area is a building. Second a multipolygon relation outer ways cannot share segments. This feature does not require a relation; simply map the outside of the area and label that with the name, shop and possibly 'landuse=retail' The layer key is used to indicate that something is physically higher or lower than something else... there is none of that here. A comment: when you alter something look for the existence of the tag 'source=*' .. if you are using a different source .. simply delete the tag 'source=*' |
|
| 126718947 | Strange! It did show as an 'outer' see relation/6836233/history ...
|
|
| 124719504 | Thanks Nev .. re entered. It maybe a very small field within the cricket circle in the bing imagery... but too hard to make it out. |
|
| 124719504 | Hi,
|
|
| 125208959 | This and other edits have broken train route relations. Learn how not to break the relations by fixing the many that you have broken! |
|
| 123975783 | I have set this to a site relation. This avoids the error of shared segments in a multipolygon relation outer ways. Been ~2 months since the error was noted. |
|
| 126718947 | Hi, An error in the relation 6836233 - wood. Way: Lake Elizabeth (198991852) should have the role 'inner' inside the relation. I'll let you fix it so you can examine it. |
|
| 125958988 | Keep mapping, humans make errors and I think we all learn best by fixing our own mistakes. |
|
| 46387901 | Hi, I have changed some boundaries of adjacent parks to what I think is more correct DCS Base Map boundaries.. approximately.
|
|
| 126419593 | I have used JOSM validator to further check this changeset: Highways crossing barrier fences ... 4 in this changeset but others also evident from past entries. These need to have the barriers removed from the highway .. or some gated entry provided. Barrier Way: 1096276941, Way: 1096276939 and Way: 1096276960. Highway Way: 1096276958 connected to building, Way: 1096276959 |
|
| 126419593 | Past messages about errors have been ignored, this one will probably be the same? The building way self intersects ... you should fix this. Note: The iD reported warnings of "crossing highway/waterway" and "impossible one way highway" are worth investigating. |
|
| 117374302 | Err ... 'australian_football' ... looks like rugby to me. Altered. |
|
| 126319485 | Hi, There has been some dragging of at least 2 nodes by this changeset... node/7429152706 dragged south east, makes build way cross it self
Bit mystified as to why... looks like the nodes were changed without realizing they were 'inuse'??? |
|
| 126298299 | Hi
I would suggest you delete the relation and place tag 'building=residential' on the remaining 3 ways. I'll leave it to you to correct the situation? |
|
| 52775305 | Arr
|