Invalid route flagged but no data provided that is triggering the invalid route.

[drkludge]

I have two route relations, 4547782 and 4547783, among others relations that I have used osmi_inspector maintain validity. On 4/6/2021 I corrected a "stop not on way" error for both routes. It appeared that I mixed up two stops at a bus station via cloning of the routes. Thank you for this additional check. However, today, 4/7/2021, the routes are marked as invalid but no error text has been provided.

• I checked that the two stops and platforms are in the correct order.
• These nodes are at the beginning of the route relation table.
• The nodes have either stop or platform as the role in the relation.
• The route has no gaps or members out of order.
• The last update to the osm wiki page is 2017.

There is no information to tell me how to fix this invalid state. Is this a bug or are there some documentation items missing from the wiki page to tell me how to fix the reported issue with these relations?

layer:	ptv2_routes_invalid
rel_id:	4547783
from:	
to:	
via:	
ref:	SR 51 OB
name:	bus SR 51 Rapid OB
route:	bus
operator:	Valley Metro Org
error_over_non_rail:	             <===== Nothing listed.
error_over_rail:	
error_unordered_gap:	
error_wrong_structure:	
no_stops_pltf_at_begin:	
stoppltf_after_route:	
non_way_empty_role:	
stop_not_on_way:	
no_way_members:	
unknown_role:	
unknown_route_type:	
stop_is_not_node:	
error_over_non_ferry:	

[drkludge]

I wonder if relations 4547782 and 4547783 are being marked invalid because the same nodes are also used in routes 39 south and north bound. The stops/platforms used in 39 SB and 39 NB are marked as 'stop not on way'.

[drkludge]

An error is reported for route relation 4499177. The error reported is that the stops are out of order. However, they are listed from the first stop to the second stop. Only two stops are added to the relation at this time. There are no gaps in the relation. Normally the gap in the route order is the issue that I have to deal with.

layer: | ptv2_error_nodes
4499177
186 WB
bus 186 WB
bus
0
5224102453
stop included in wrong order

[drkludge]

So after experimenting I think I understand the problem. The wiki page says that the osmi_pubtrans3 software does not enforce the order of stops. It appears that the software now tests the order of the stops starting around April 2021. The order of the stops must now match the order of the route i.e. north to south route members must have the stops as north to south stops. The issue is that there is no error text in the route feedback list to say this. The clue is that you have to go and look at each individual stop for the error condition and then map the stop order issue to the correct route.