2019-01-18 08:40:47 +03:00
# TODO - Map quality
## Geometry
2019-02-01 00:53:41 +03:00
- bad polyline shifting remains
- from the remaining cases, looks like we need to totally remove some tight points and retry
- make polygons use the corrections too?
- bad polyline shifting causes jagged lane endings in generalized_trim_back
2019-01-18 10:43:56 +03:00
- handle small roads again somehow?
2019-02-03 03:46:50 +03:00
- bad polygons
- ../initial_maps/024, o101. sorting final endpoints by angle to center isn't foolproof.
- adjacent roads based on angle isnt foolproof either. o177
2019-01-28 01:30:30 +03:00
- VERY overeager... ate half of the map
- deal with loop roads
2019-01-26 23:08:08 +03:00
2019-01-22 03:48:19 +03:00
- manually draw a picture of the weird intersection to see what would look reasonable. i think we need original road bands from deleted stuff to make decent polygons.
2019-01-18 10:43:56 +03:00
- model U-turns
2019-01-19 09:15:24 +03:00
- degenerate-2's should only have one crosswalk
- then make them thinner
2019-01-18 08:40:47 +03:00
- ped paths through sidewalk corners are totally broken
2019-01-21 01:27:25 +03:00
- calculate the better paths first, then make the corner geometry from that?
- car turns often clip sidewalk corners now
2019-01-18 08:40:47 +03:00
- figure out what to do about yellow center lines
2019-01-18 10:43:56 +03:00
- intersections on one-ways look weird
2019-01-18 08:40:47 +03:00
- yellow and white lines intersect cars and turn icons and such
- who should own drawing them?
## More data
- lanes: https://data-seattlecitygis.opendata.arcgis.com/datasets/49d417979fec452981a068ca078e7070_3
- not filled out for most streets
- traffic circles: https://data-seattlecitygis.opendata.arcgis.com/datasets/717b10434d4945658355eba78b66971a_6
- https://data-seattlecitygis.opendata.arcgis.com/datasets/sidewalks
- disagrees with OSM road centers sometimes
- https://data-seattlecitygis.opendata.arcgis.com/datasets/curb-ramps
- high quality thick roads: https://seattlecitygis.maps.arcgis.com/apps/webappviewer/index.html?id=86cb6824307c4d63b8e180ebcff58ce2
- OSM has footways
- but theyre not marked everywhere
- and theyre hard to associate with roads (sometimes need to infer a planter strip)
- draw ALL water and greenery areas
- draw benches, bike racks
- render trees
- look for current stop sign priorities
- https://gis-kingcounty.opendata.arcgis.com/datasets/traffic-signs--sign-point/
2019-01-18 10:43:56 +03:00
## Low-priority geometry issues
- if building front path intersects another building, then scrap that building.
- or wait, just require bldgs to be even closer to sidewalk first.
- need to do polygon vs polygon check!
- will need to speed it up with quadtree containing entire buildings. make sure these are easy to use.
- can we make OSM buildings with holes?
- experiment with https://docs.rs/clipping/0.1.1/clipping/gh/struct.CPolygon.html and https://github.com/21re/rust-geo-booleanop
2019-01-21 23:02:59 +03:00
2019-01-22 21:02:18 +03:00
## More problems to fix
- Disconnected map
- Some lane-changing model needed to determine this
- Impossible turns (from a far bus lane to a crazy left)
2019-01-21 23:02:59 +03:00
## Release
- publish the map data
- stabilize the code except for sim