One big subset of the ‘temporary paths’ gotcha is cyclocross courses, as the riders overwhelmingly track and upload to strava, but they aren’t following anything permanent. Here’s a pretty good example from DCCX: https://www.strava.com/maps/global-heatmap?sport=All&style=satellite&terrain=false&labels=true&poi=true&cPhotos=true&gColor=blue&gOpacity=100#17.08/38.933247/-77.017565

Will this design system also cover cartographic design?

More importantly that PBF files, the OSM Database stores coords as integers multiplied by 1e7 thus that’s the most accurate way or representing them in any other file format too.

Here’s a styled Ultra query you could also use: https://overpass-ultra.us/#run&m=18.57/39.0821/-77.4732&q=LQhQGcBcE8BsFMBcoAELYENrwE7mWmsCjAA5IrjQC2ARgPayqFoCWAxvQHbD0BuuTKUQoMsAO5ZwzFh27BW1DAHMkMlimJLI7ABbqWxANqrIAGnTwMAMwD6ZeAF0DhYl3jwAJggQYBnlyIUeGp6ACtWRHgBHGUcDy57ePhAzWDQiMRPeHZWTwBXenzwJI9QEGBQLnpsoy4MSHycMQBeSGTHAAoAb27aBgAPAF8hgEoAblAiyEmgA

Yes I have @Kovoschiz. Just not sure what to make the user experience like. It might hook into the adding style layers feature mentioned in “what’ next?”

@Kovoschiz, nope. But I do have a prototype of a turbo2ultra bookmarklet I can clean up and formally release. I could also look into supporting #query=turbo:SHORTLINK_ID if there are appropriate CORS headers from the turbo backend.