[sumo-user] duckOSM Studio — build a SUMO network from OSM in the browse

[khoshkhah@xxxxxxxxx]

Hello all,

Many SUMO scenarios start with the same step: turn OpenStreetMap data
into a network, usually via netconvert's OSM import or osmWebWizard. I
have built a free, open-source alternative for that first step, and I
would value this list's feedback on whether its SUMO output is right.

duckOSM Studio (v0.3.0) is a web page, nothing to install. You choose
an area, it builds the driving, walking and cycling networks from OSM
data in your browser, and you can fix problems in the OSM data — a
disconnected road, a turn rule, a bridge or tunnel at the wrong level
— and rebuild in seconds. Monaco builds in under a second. Each edge
has length, speed and travel time, turn restrictions are applied, and
each road keeps a stable edge_id across builds (written as text in the
files, as the ids are 64-bit numbers).

The SUMO export is a zip with the plain XML files — .nod.xml,
.edg.xml, .con.xml — plus a README with the exact netconvert command
to make the .net.xml. Details are on the manual's export page.

- Try it: https://khoshkhah.github.io/duckosm-studio/
- SUMO export, in the manual:
https://khoshkhah.github.io/duckosm-studio/manual/manual/export/
- Source code (MIT): https://github.com/Khoshkhah/duckosm-studio
- Short demo video:
https://www.linkedin.com/feed/update/urn:li:ugcPost:7525731236737110016/

My questions for SUMO users are specific:

1. If you export an area you know and run the netconvert command, does
it complete cleanly? Any errors or warnings that point to a problem in
my exporter?
2. How do the connections and turn restrictions compare with what you
get from netconvert's direct OSM import?
3. Is plain XML the right thing to export, or would a direct .net.xml
export be more useful to you?

Thank you,
Kaveh Khoshkhah