Re: [sumo-user] Scale-Dependent Edge Formation in netconvert with Differ

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

The difference occurs, because osmGet.py retrieves all OSM roads ("ways") that intersect with the bounding box even when they are not fully within.

In your case, way 36777680 touches the small bounding box at it's northern end is included, whereas way 1098784137 is excluded.

For this reason, way 36777680 is built without junction 10060631529 (the side road 1098784137 is missing).

In the large bounding box, many side roads are included which causes the way to split at multiple junctions.

It follows from this, that an edge must be fully within the bounding box to ensure that it doesn't change when increasing the bounding box.

A possible solution to ensure stability, is to always download a larger bounding box and remove any edges that do not intersect with the original (small) bounding box (netconvert --keep-edges.in-geo-boundary).

regards,

Jakob

Am Di., 12. Aug. 2025 um 16:29 Uhr schrieb Manohara C V via sumo-user <sumo-user@xxxxxxxxxxx>:

Dear SUMO Team,

I am experiencing inconsistent network topology generation when using netconvert with OSM data across different bounding box sizes. The same roads produce different edge structures depending on the area size.

Problem:

• Small bounding box: Roads form as connected single edges (desired behavior)
• Large bounding box: Same roads fragment into multiple short edges with many intermediate junctions (undesired behavior)

Test Bounding Boxes (osmget.py): 

• large area - '77.288818359375,12.769113855469314,77.74200439453125,13.149194131932646'
  
  
• small area - '77.56663933167825,13.005436732714667,77.56823663763048,13.005741560926017'

Issues like :- edge id "36777680#0" having forming differently 

Current netconvert command:

netconvert \
--osm-files input.osm \
--ramps.guess \
--junctions.join \
--junctions.scurve-stretch 1.0 \
--tls.guess-signals \
--tls.join \
--tls.uncontrolled-within \
--geometry.remove \
--output.street-names \
--output.original-names \
--keep-edges.by-vclass passenger \
-t typemap.xml \
--output-file output.net.xml

Attempted Solutions (all failed):

1. Disabled all heuristics: --geometry.remove false --junctions.join false --ramps.guess false
2. Used fixed thresholds: --junctions.join-dist 10
3. Removed typemap completely
4. Added --roundabouts.guess false and --edges.join false

Question: Why does netconvert produce different edge topologies for the same OSM roads when the bounding box size changes? Is there a scale-dependent algorithm that can be disabled to ensure consistent edge formation regardless of network area?

Expected Behavior: Identical road topology regardless of bounding box size - same OSM ways should always produce the same SUMO edge structure.

Environment:

• SUMO Version: 1.23.1
• OS: windows
• Data Source: OpenStreetMap

Thank you for your assistance.

Best regards,

Manohar 

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user