OpenStreetMap logo OpenStreetMap

Changeset When Comment
180614399

HI,
way/675830594 (forest) crosses it self.
See red bits in https://tools.geofabrik.de/osmi/?view=areas&lon=176.15680&lat=-38.52285&zoom=16&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

Make it a multipolygon relation - one outer way and one inner way?

180436686

Hi.
Mulptipoygon outer ways cannot share segments.
See blue segments in https://tools.geofabrik.de/osmi/?view=areas&lon=176.25120&lat=-38.14064&zoom=19&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

157523295

And leaving behind a broken relation/2749751.

180444953

Opps
"The stop comEs first then it's associated platform "

180444953

The order of stops need to be combined with the platforms...
The stop coms first then it's associated platform .. then the next in sequence stop/platform pair or single.
See https://osmand.net/blog/guideline-pt/

180497274

relation/7898026 - residential is in error!
See the blue line in https://tools.geofabrik.de/osmi/?view=areas&lon=151.32559&lat=-33.43893&zoom=17&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

As there are no 'holes' in the areas a relation is not needed.
Make each way a closed way - not separate segments but an area. Then delete the relation and tag each closed way with 'landuse=residential'.

180497274

I have separated the relation into 2 relations - one has the area you are making changes in .. the other covers a larger area so at least that will render while the other is sacrificial.

Better mapping?
It would be good if you could add one single way from north to south rather than these small areas. That would then enable the relation to use it as a replacement for the sections involving both residential areas and the Brisbane Waters NP...

180497274

I'll wait till your done!

These ways added immediately adjacent to tree relation/16051399 should be incorporated into it...
The relation/16051399 is now not being rendered as it is broken by these edits. Tis results in a large tree area as a blank space on the map.

180394157

Ok... your trying to adding tree segments outside the tree relation/16051399

The difficulty is that the tree relation uses some of the Brisbane Water NP..

I have made corrections and added your segments to the tree relation. takes a bit of work but can be done. Not an iD user sop cannot help with that.

115587099

Hi
Multipolygon relation/13618251 parking

Better mapped?
Ways 1017013456, 1017013457, 1017013459 and 1017013458 can al be deleted - they have the wrong rolls anyway and can be replaced by ways 1017013452 and 1017013453 (gardens inside the parking area.)

See relation/13618251 for rolls ...
And way/1017013452 way/1017013453 for the gardens.

159684835

It is a bit of a mess, insn't it!

relation/2724782 scrub is well and truly broken .. should it be deleted?

Way: 1338514652 and Way: 1338953826 should be combined into one way... There are probably a lot more confused things here.

180394157

Why???

The creation of Way: 1492540715 trees

and then excluding it from Relation: 16051399 tress ... ignore the hole in the trees Way: 552876396

The trees boundary cannot be seen in the DCS base map .. it does not show trees.

Relation: 16051399 is now broken.

180093844

Stops do not go at the end of the relation,
As a group they go at the very beginning of the relation, and they go in sequence from the start to the end of the route. Then the ways follow in the relation, again in sequence fro the start to the end of the route.

In this changeset you added a stop at the very end of relation/2033217 India Pacific from Perth to Sydney.
Note the stop already exists as a node where the train stops - you added a platform. That is not required ...

131001117

This multipolygon is now fixed.
No share segments.

I have also combined ways so now only 3 members - reduced data bloat.

137370859

Relation roles corrected

137464827

Relation roles corrected

137442201

Roles in relation/15980981 corrected.

179609274

HI
The roles in relation/20304766 are incorrect..

The outside has been given the role 'inner' and the inside has been given the role 'outer'.
See https://tools.geofabrik.de/osmi/?view=areas&lon=178.16222&lat=-38.47227&zoom=19&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

177245114

Hi,
What feature is relation Rotorua Central Mall (20086689), v1 trying to map?

An indoor corridor?
A building?
A shop?

It is tagged for all 3 ...

I think it should be mapping the shop=mall as

Each building has a separate way .. and they are separate buildings? So tag the separate ways as such .. this enables each to have different heights, colours, materials roofs etc.

The corridor would not take all of the internal space.

Next problem: there are shared segments between outer ways... see https://tools.geofabrik.de/osmi/?view=areas&lon=176.25138&lat=-38.14068&zoom=19&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

Simply create a new way that incorporates all of these buildings and put that way into the mall relation.

179881363

Good .. that fixed the razed bit for the Syd 2 Melb XPT.

Niggle .. the ways were not in sequential order .. I fix that for the Syd 2 Melb XPT.
You may want to check the others? I use to find problems:
https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=144.94284&lat=-37.80718&zoom=15&baselayer=Geofabrik%20Standard&overlays=ptv2_routes_valid%2Cptv2_routes_invalid%2Cptv2_error_ways%2Cptv2_error_nodes%2Cptv2_routes_valid%2Cptv2_routes_invalid%2Cptv2_error_ways%2Cptv2_error_nodes