planning for lanes

This commit is contained in:
Dustin Carlino 2018-05-16 19:40:53 -07:00
parent 37b3909596
commit 808e0f26fa
2 changed files with 19 additions and 4 deletions

16
TODO.md
View File

@ -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

View File

@ -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.