Please support superroutes

[robhubi]

CyclOSM does not render the Austrian part of the EV9, see also discussion on reddit "EuroVelo 9 disappeared?". Is this because cyclOSM does not support super routes?

In Austria, the local operators have decided to run the EV9 exclusively on existing routes. For this purpose, the existing routes were adapted and the ends were connected. The signposting also underlines this common aspect:

Examples of signposting in Austria (source: Mapillary).

The superroute EV9 part Austria consists of the following routes:

(Sub-)Section	Name (Relation)	Typ	Network	Ref
part Austria	EuroVelo 9 - Baltic-Adriatic - part Austria (2766147)	superroute	icn	EV9
[AT]_1	Břeclav-Wien (13527283)	route	rcn	-
[AT]_2	Weinviertel-Radweg (13529622)	route	rcn	-
[AT]_3	Laxenburg-Radweg (13529749)	route	rcn	-
[AT]_4	Thermenradweg (NÖ, 120611)	route	rcn	-
[AT]_5	Thermenradweg (Stmk, 48137)	route	rcn	R12
[AT]_6	EuroVelo 9 - Baltic-Adriatic – [AT]_6 (13533913)	route	icn	EV9

Sections 1 to 5 are local cycle routes that are entirely within EV9. Section 6 is covered independently of the local cycle routes.

Some considerations on sub-relations can be found e.g. at Waymarked Trails.

Related Issues: #586, #530, #221, #101

[Phyks]

This issue has already been discussed in the past. Superrelations are fancy OSM tagging which is not supported by much tools in the OSM ecosystem: https://wiki.openstreetmap.org/wiki/Relation:route#Creating_super-relations_for_routes.

In particular, most of renderings, except when doing custom pre-computation or complex SQL queries, will not support it as they rely on osm2pgsql for the OSM to Postgresql data import and osm2pgsql does not support them. The same stands for imposm3 as far as I know.

I would, for sure, welcome any contribution for supporting and rendering super-relations. This however is not a small task and I'm not sure it is CyclOSM's goal to be the first render to tackle this task.

[robhubi]

It was important for me to show that superrelationships can add real value in some cases. So I am very happy to read that contributions to the support and rendering of superrelations are welcome. I am also sure that the task will be complex and difficult to solve.

The first step towards implementation would be to leave the issue open so that ideas, applications and opinions can be collected.

Unfortunately, the race for the first place "who renders superroutes" is already over:

Fig. 2: Rendering of superroutes "2" and "EV15" (circled in green) in Waymarked Trails, cycle.travel and cyclOSM. (c) Map data: OpenStreetMap and contributors

In the example above, the Rhein-Route - Etappe 4 (149204) with ref="2;EV15" is a member of two superrelations:

1. Rhein-Route (8497) with ref="2" and
2. EuroVelo 15 - Rheinradweg - Teil Schweiz (2769483) with ref="EV15"

Waymarked Trails suppresses the rendering of section 4 of the Rhine route because it is considered non-autonomous (same network tag). cycle.travel displays all routes, cyclOSM only the basic route.

Finishing first is no longer possible, but finishing is also a nice result. Isn't it?