From 808e0f26fab47d4983a912eec51c9607fdc109d2 Mon Sep 17 00:00:00 2001
From: Dustin Carlino <dcarlino@google.com>
Date: Wed, 16 May 2018 19:40:53 -0700
Subject: [PATCH] planning for lanes

---
 TODO.md       | 16 ++++++++++++----
 docs/lanes.md |  7 +++++++
 2 files changed, 19 insertions(+), 4 deletions(-)

diff --git a/TODO.md b/TODO.md
index bc425fd2f4..b20c7077b7 100644
--- a/TODO.md
+++ b/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
 
diff --git a/docs/lanes.md b/docs/lanes.md
index b919168f98..3ff2cbe825 100644
--- a/docs/lanes.md
+++ b/docs/lanes.md
@@ -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.