mirror of
https://github.com/a-b-street/abstreet.git
synced 2024-12-25 07:25:47 +03:00
4ef04f5bd1
"rise / run" calculation used the trimmed road center-lines, which don't match up with the elevation at each original intersection point. Also handle infinity in the output and reduce the resolution of the query from every 1m to every 5m. Regenerate all maps due to the map format change. Try bringing in elevation data for all of Seattle using the LIDAR source, since the data quality assessed in eldang/elevation_lookups#12 seems to be similar, and LIDAR is way faster than contours. |
||
---|---|---|
.. | ||
src | ||
Cargo.toml | ||
README.md |
SUMO interoperability
The purpose of this crate is to explore possible interactions between A/B Street and SUMO. Some of the ideas:
- Convert SUMO networks to ABST maps, to make use of SUMO's traffic signal heuristics and junction joining
- Convert SUMO demand to ABST scenarios, to leverage all of the existing demand generation techniques
- Prototype a new SUMO frontend by gluing ABST UI code to TraCI
Usage
A quick SUMO primer. To convert an OSM file into a SUMO network:
netconvert --osm-files data/input/us/seattle/osm/montlake.osm --output.street-names --keep-edges.components 1 -o montlake.net.xml
To generate random trips and compute the routes for them:
/usr/share/sumo/tools/randomTrips.py -n montlake.net.xml -r routes.xml
To simulate these in SUMO:
sumo-gui -r routes.xml -n montlake.net.xml
To convert the network into an ABST map:
cargo run --bin sumo montlake.net.xml
To view it in ABST:
cargo run --bin game -- --dev data/system/zz/sumo/maps/montlake.bin