Use two-table strategy in CartoDB
maxZoom
Data processing, rough draft
Keep boroughs in plans, not lots
Lots
Style plan sidebar
Break query url up a bit
Lot count
Break sql query up a bit
Move to OSM-style hash
Move hash to its own file
Use map instead of args
Remember plan name in hash
Remove underscores
Add plan content with borough