a-b-street/abstreet
1
1
Fork 0
mirror of https://github.com/a-b-street/abstreet.git synced 2024-11-24 09:24:26 +03:00
Code Issues Projects Releases Wiki Activity

Another attempt to write down a sort of roadmap for modularizing abst

Browse Source
This commit is contained in:
Dustin Carlino 2020-10-14 13:14:53 -05:00
parent c0513a3d64
commit 20b4f15e86
1 changed files with 38 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
book/src/map/platform.md
View File

@ -81,3 +81,41 @@ optional pieces, and probably loaded in as separate files.
Depending what other open source projects are on board, the general idea is to Depending what other open source projects are on board, the general idea is to
start assembling an ecosystem of libraries/tooling to make it easier to build start assembling an ecosystem of libraries/tooling to make it easier to build
new things off of open GIS data. new things off of open GIS data.
The end state might look like this. A few separate applications would exist, all
running both natively and in the browser:
- A/B Street the game, more or less in its current form
- A new OpenStreetMap viewer, likely focused on visualizing roads and
points-of-interest in detail
- The street parking OSM editor, and other OSM editors specialized for mapping
certain things
- A new app focusing on 15-minute neighborhoods, using isochrones to show
amenities available nearby
- Ideally, allow editing current land use / zoning, to let people explore how
new policies might get closer to a 15-minute neighborhood.
- Possibly [GOAT](https://www.open-accessibility.org) does all of this
already, and this new thing shouldn't be built
- A new app for creating story maps, showing events that occur over time, with
lots of detail about the surrounding environment
All of these would make use of some common libraries, which should be extracted
out cleanly from A/B Street today:
- the map model and OSM importer
- the widgetry UI library
- some common code for specifically interacting with maps in widgetry
- a tool to generate a traffic demand model from OSM data, optional census data,
etc
- This has been initially
[prototyped](https://dabreegster.github.io/abstreet/trafficsim/travel_demand.html#proletariat-robot)
- the discrete-event traffic simulation that A/B Street uses today
- core geometry/utility libraries
But note only the first application would use things like the simulation
library. The point of more cleanly modularizing these pieces is to make it
easier for new people to build different pieces, without having to understand
and be coupled to everything else. Also, as appropriate, these pieces should use
common data formats (like
[shared-row](https://github.com/d-wasserman/shared-row/)) to be interoperable
with Streetmix, Complete Streets, etc.