Changes between Initial Version and Version 1 of Ticket #24741, comment 3


Ignore:
Timestamp:
2026-06-01T18:08:34+02:00 (3 weeks ago)
Author:
PPete2

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #24741, comment 3

    initial v1  
    11Replying to [comment:1 GerdP]:
    2 > What if the relation starts or ends with a roundabout but is not a roundtrip or if there is a gap after/before a roundabout? We could either add the full roundabout or nothing. I guess omitting the roundabout is safer.
     2> What if the relation starts or ends with a roundabout but is not a round-trip or if there is a gap after/before a roundabout? We could either add the full roundabout or nothing. I guess omitting the roundabout is safer.
    33
    4 In this case I would tend to also include the (full) roundabout, caused just this would reflect the situation of the OSM-route. Further advantage: If a mapper added the roundabout at start/end of an OSM-route by mistake we will see this situation by its GPX-export and are able to correct it (by removing the roundabout within OSM-route) if necessary.
    5 Regarding gap: I don't quite understand. OSM-routes often have gaps (mostly because somebody edited/splitted/deleted ways of the route and forgot about proper consideration of routes on this ways). In this case JOSM should still export just 1 GPX-track ''<trk>'' - but consiting of multiple GPX-segments ''<trkseg>''
     4In this case I would tend to also include the (full) roundabout, cause just this would reflect the situation of the OSM-route. Further advantage: If a mapper added the roundabout at start/end of an OSM-route by mistake we will see this situation by its GPX-export and are able to correct it (by removing the roundabout within OSM-route) if necessary.
     5Regarding gap: I don't quite understand. OSM-routes often have gaps (mostly because somebody edited/splitted/deleted ways of the route and forgot about proper consideration of routes on this ways). In this case JOSM should still export just 1 GPX-track ''<trk>'' - but consisting of multiple GPX-segments ''<trkseg>''