Warin61's Comments
| Changeset | When | Comment |
|---|---|---|
| 147289353 | Bus stops added to PTv2 must have tags "public_transport=platform" and "bus=yes"... those added to bus route 290 'Epping - City' don't have these tag - thus fail PTv2. |
|
| 147210968 | Bus route 166 (to) Frenches Forest. What I have done.... Placed the ways into the correct sequence, they run from start to finish. Stops placed into the correct sequence - from start to finish. All stops placed at the beginning of the relation. If you don't know how to do this .. find out. I don't used Id, I did use it once or twice when I first started with OSM, but was told that if I wanted to do complex stuff I was better off using JOSM. I have been using JOSM since then.
|
|
| 147128820 | Moved bus stop in relation for 166 route to correct position in the relation. In PTv2 ALL bus stops are placed before the ways. All of them. None of them go after the ways. |
|
| 147046310 | Existing bus stops already in OSM probably meet the PTv1 requirements. For PTv2 you have to add tags "public_transport=platform" and probably "bus=yes". The real headache is getting the dam things in sequential order.
|
|
| 147046310 | A 'bus stop' is beside the road. A bus 'stop_position' is on the road - where the bus actually stops. For PTv2 a "bus stop" must be tagged as "public_transport=platform" Node: Santa Maria del Monte, The Boulevarde (2877493994) changed back to "public_transport"="platform" |
|
| 147046310 | Out of sequence bus stops without roles in the route relation removed from the relation. Step 1) place them in sequential order
|
|
| 147040364 | Fix?
???????????????
Or will you leave it like relation/2792531? |
|
| 147009773 | Hi,
|
|
| 144783896 | Hi,
|
|
| 146937754 | Hi,
|
|
| 147007012 | The one member residential relation is not a replacement for the residential relation that was altered to the point of making no contribution (no outer way as it has been deleted) as it does not cover the area south of Stringybark Reserve One member relations should be removed with the tags simply moved to what was the outer way of the relation. If the one member relation has no outer way then it makes no sense. |
|
| 140297967 | The sign a the top is legal access=no ... While people might break the law OSM should not encourage it??? |
|
| 146897585 | Bus stops out of sequence and without roles removed from relation. |
|
| 146981992 | Out of sequence bus stops without roles removed from relation/3766951. Ways have been re-sequenced. |
|
| 146987654 | Hi,
To fix it - make a new way for the hole. Enter the new way into the relation with the role 'inner'. See osm.wiki/Relation:multipolygon#Multipolygon_created_by_only_one_polygon |
|
| 146850025 | I did not say it was 'your work'. What do you think of the 'taxilane' tag? It does distinguish between one control area and another control area... |
|
| 146927629 | relation/3766951 has stop in wrong order. I have removed the stop from the relation. |
|
| 146560953 | We map and tag in OSM. The renders draw the way they want to, they can exclude some things etc. We map and tag according to the 'rules' what the renders do is up to them ... The 'green areas' are used by pedestrians, so they are part of the pedestrian are as are the roof area - people walk under than for shade.. If you object to way something is drawn - take it up with the renders. |
|
| 146850025 | See
Thank you for moving some of the 'gates' inside the terminal buildings. also see for more on taxiway taxilanes...
I have raised the 'parking_position' being used as a way on the tagging list. Lets see what the tagging experts think? I note there has been on proposal on the 'parking_possition'. |
|
| 146560953 | That is a rendering issue.
A 'national park' is tagged as a boundary and is drawn as a line around the outside - no fill. See relation/6110851 |