This relation is still incorrect!

See https://tools.geofabrik.de/osmi/?view=areas&lon=143.66725&lat=-38.01783&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

Hi,

The Mosque ...
Way: 957793571 building:part=yes ... umm would that not be part of the roof? If so building:part=roof? And also the location would be in the center of the building?

Simply changing the tag 'public_transport:version=1' to 'public_transport:version=2' is not enough to make these PTv2.

Hi,
I have restored relation/7079456 add parts of this changeset to that relation.

Try to work with the existing tree relations rather than making new ones.

relation/15571536 - water - has he roles 'inner' and 'outer' wrong.

Please look at it and fix it.

This error remains... The roles 'inner' and 'outer' are mixed up in relation/15406000

Adding the PTv2 tag to a relation does not make the relation compatible with PTv2 requirements.

Hi,
This route does not meet the requirements for a Public Transport Route version 2 ... see https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=144.76857&lat=-37.97780&zoom=12&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

Hi,

This building has a problem..
See https://tools.geofabrik.de/osmi/?view=areas&lon=151.06917&lat=-34.01403&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

Don't know.

One error visible here - site updates about every day and comes up with more slowly
https://tools.geofabrik.de/osmi/?view=areas&lon=115.83510&lat=-32.06858&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

Other QA tools ..
https://www.keepright.at/report_map.php?zoom=12&lat=-33.88489&lon=151.1875&layers=B0T&ch=0%2C30%2C70%2C120%2C380&show_ign=1&show_tmpign=1
https://www.keepright.at/report_map.php?zoom=12&lat=-33.88489&lon=151.1875&layers=B0T&ch=0%2C30%2C70%2C120%2C380&show_ign=1&show_tmpign=1

------------
I am not an ID user so I cannot help you with that editor.

YOU can see the problem for the next few hours on https://tools.geofabrik.de/osmi/?view=areas&lon=147.20206&lat=-42.53316&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

Hi,
Ar a node was deleted by you in changeset/133653203. This fixed the problem.

You do need to work on those errors/warnings.

In this area JOSM validator reports some 16 errors and 121 warnings...

Errors (16)
Duplicated ways (1)
Highway duplicated nodes (10)
Multipolygon is not closed (1)
Multipolygon ring contains segment twice (3)
Overlapping highways (1)
Warnings (121)
area on a relation (1)
Crossing building/highway (7)
Crossing highways (60)
highway=footway together with foot=no (1)
highway=footway together with maxspeed=40 (1)
missing tag - man_made=tower without tower:type (1)
Mixed type duplicated nodes (23)
node connects highway and building (3)
Route scheme is unspecified. Add public_transport:version (2=public_transport; 1=legacy) (1)
Self-intersecting polygon ring (1)
Unconnected nodes without physical tags - No tags (2)
Unnamed ways (12)
Way end node near other highway (8)

Hi,

relation/15577991 does not make sense? natural=wood;heath err no. It is either heath or wood. And both members are 'outers' yet one is inside the other.
Looks to me like way/1152292927 should be tagged natural=wood (as it was before this changeset) and then have the role 'inner' in the relation. The relation should be tagged natural=heath

See what you think.

Hi,
Golf is a problem in OSM...

Relation 14005754 - "self intersects" where grass crosses the sand bunker

Other 'golf problems' can be found on https://tools.geofabrik.de/osmi/?view=areas&lon=143.84688&lat=-39.89667&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

Hi,
The JOSM validator would have issued the warning message "crossing ways' ...There is only one, way/435781531. Would you please look at it and correct it?

Similar issue here

Way are not in sequence order.

For other errors see https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=151.28155&lat=-33.84362&zoom=9&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

For basic hints on PTv2 see @Warin61/diary/45106

Hi,
This does not meet the PTv2 rules...

Does not start with the stops.

Role 'stop' is not used for stops.

Are the stops in sequenced order?
Are way in sequence order?

Changeset reverted to restore the above 2 train routes. Looking at the past non response this is the easiest thing for me to do.

You have not responded to any changeset comment in the past 4 months. Are you getting these comments??? Please respond.