Help: how to fix - empty route relation after complex CS one year ago

Help and support
,
1

This bus route relation Relation: ‪Bus 42: Bernex-Vuillonnex → Carouge-Rondeau‬ (‪13694830‬) | OpenStreetMap (version #20) is now empty, has no members after a complex edit (Changeset: 150252775 | OpenStreetMap) 1 year ago using JOSM (JOSM/1.5 (18940 fr)). Version #19 was OK

How can this be repaired w/o reverting the complete (old) Changeset?

How could JOSM upload this empty relation. My experiences: I cannot save a relation in JOSM’s relation editor if the list of members is empty.

BTW: I happened to do the same on bicycle route D11 in Germany 15 years ago.

2

In general the solution is to revert the changeset and then just upload the relation (throwing the rest away).

After a year that is probably going to require some work to get back to something correct though.

3

Yeah, maybe no easy repair scenario available.

Seems that the bus 42 (and others) haven’t been updated sind 2022? Their gtfs:route_id indicates ‘...-j22-...’. That is how Mentz codes the “season” into route_id, trip_id and shape_id. So there’s anyhow lots to do.

Also: current GTFS data indicates that this particular route 'from' = 'Bernex-Vuillonnex', 'to' = 'Carouge-Rondeau' does not exist (any longer)

public-transport gtfs ptna

Edit: Link to GTFS data with partly English text

4

I would at least contact mapper who broke it, though they seem barely active.

And depending on complexity of fixing nad mapper experience they may be unable to fix it.

5

It depends. I suspect a JOSM revert would need significant merging with changes made in the last year. I’d instead try and undo (using the Perl revert scripts or similar) just the changes to that one relation. That’ll likely fail, but it’ll help you compose a .osc file that will work. There may also be a “force” option to “only upload relation members that still exist”. Then check for relation integrity using tools such as http://ra.osmsurround.org/analyzeRelation?relationId=13694830.

6

I suppose to make a step backward:

Does it make sense to fix this route relation if the whole bus route ref=42 seems completely/partly outdated according to current GTFS data?
None of the existing route relations shows a good match with GTFS.
There are also 2 route_master relations for the same bus.

Let’s wait for the end of next week. There will be a change in timetables on 2025-12-14 and new GTFS data will be available, with updates (at least ‘…-j25-…’ changes to ‘…-j26-…’).
Let’s then fix the bus 42 completely.

1 Like