mirror of
https://github.com/a-b-street/abstreet.git
synced 2024-12-25 15:33:44 +03:00
planning for lanes
This commit is contained in:
parent
37b3909596
commit
808e0f26fa
16
TODO.md
16
TODO.md
@ -44,10 +44,18 @@
|
||||
- look for current stop sign priorities
|
||||
- https://gis-kingcounty.opendata.arcgis.com/datasets/traffic-signs--sign-point/
|
||||
|
||||
- driving lanes
|
||||
- parking
|
||||
- sidewalks
|
||||
- bike lanes
|
||||
- roads -> lanes
|
||||
- driving lanes
|
||||
- parking
|
||||
- sidewalks
|
||||
- bike lanes
|
||||
|
||||
- in an experimental branch...
|
||||
- make map_model create several "roads" per road proto
|
||||
- add an enum type and an index-from-center
|
||||
- plumb through in all layers
|
||||
- rename these lanes
|
||||
- only have cars on the driving lanes
|
||||
|
||||
## Code cleanup
|
||||
|
||||
|
@ -8,3 +8,10 @@ It's time to model more things:
|
||||
|
||||
These have a geometric aspect (which seems similar / derivable the same way as
|
||||
roads) and a graph / usage aspect.
|
||||
|
||||
Where should the expansion of roads into lanes happen? In the initial map
|
||||
conversion, adding an index and type to the current road proto? Or better, in
|
||||
map_model::new, to defer it a bit.
|
||||
|
||||
And actually, there isn't really much use in having roads and lanes. Get rid of
|
||||
the concept of road after the proto.
|
||||
|
Loading…
Reference in New Issue
Block a user