On mobile, if you scroll down past the search box to the map, the viewport gets stuck and you can't scroll back up to the search box.

This may become obsolete due to #21 but I figured it was worth tracking anyway.

https://wiki.openstreetmap.org/wiki/Tag:highway=residential?uselang=en

After #3 is done, it would be nice to allow the user to control the relative weight of each of the three types of routes. One idea would be to have three tiers of importance (high, medium, and low), pass those through to the API, and adjust the scale factor in the query to update the weight.

Right now you have to enter some text (anything, not a substring) to get our custom options to appear below the autocomplete search inputs for start/destination locations. It would be better if the location option showed up as soon as the input was focused, like the behavior on citymapper's web app

User testing suggestion: since pgr_djikstra() returns the total cost of a given route, we should be able to return an approximate time for a given route by assuming a certain speed (this blog post suggests 11-18 mph) and multiplying it by the cost.

The one snag is that in order to prioritize mellow streets we cheat by reducing the cost in the query:

So in order to get the true cost we'll need to either figure out how to adjust the pgr_djisktra() query to return the unaltered cost, or run an additional query after we get the route to confirm its true cost.

Right now the app requires the user to input OSM IDs in order to retrieve a route. Switch this up so that the API can receive address strings and geocode them.

The frontend is pretty complex now, so we should set up some basic JS tests.

Map the North Side of Chicago following the Reader map: https://www.google.com/maps/d/u/0/viewer?mid=17mPyCktdurhbwt9HcBZFSJrXmLBKioYs&ll=41.859429425065585%2C-87.63630865000006&z=13

For our purposes, the "North Side" includes all neighborhoods north of I-55 and east of 90/94. This includes:

• South Loop
• Loop
• Near North Side
• Lincoln Park
• Lakeview/Roscoe Village
• Uptown/Edgewater
• Albany Park/North Park

Map the West Side of Chicago following the Reader map: https://www.google.com/maps/d/u/0/viewer?mid=17mPyCktdurhbwt9HcBZFSJrXmLBKioYs&ll=41.859429425065585%2C-87.63630865000006&z=13

For our purposes, the "West Side" includes all neighborhoods west of 90/94 and north/west of the South Branch of the river. This includes:

• Pilsen/UIC ✅
• Lawndale ✅
• West Town
• Garfield Park/Humboldt Park ✅
• Logan Square/Hermosa ✅

Prompt users to tell us about routes we may have missed. This could either be a CAPTCHA-protected form or, probably easier, just a link to tweet at us.

Clicking the "Directions to " or "Directions from " button in a saved location popup (pictured below) should immediately search for routes if the other input has already been set. Otherwise, it should focus the empty input.

Related to #8, update the query and the API response to show which streets in the generated route are mellow or not. Also return which type of mellow route they are (#3).

Right now the admin interface for adding routes is completely undocumented. Add some docs, including steps for exporting fixtures.

Following the citywide map, expand 1) the underlying OSM data and 2) the selection of neighborhoods to fit the full city.

I cloned this repo, ran docker-compose build, and then hit this error on the next step in the README:

Beas-MBP:mellow-bike-map beamalsky$ docker-compose -f docker-compose.yml -f db/docker-compose.yml run --rm make
Creating network "mellow-bike-map_default" with the default driver
Creating volume "mellow-bike-map_mellow-bike-map-db-data" with default driver
Creating volume "mellow-bike-map_mellow-bike-map-node-modules" with default driver
Creating mellow-bike-map-postgres ... done
Building make
Step 1/4 : FROM mdillon/postgis:11
 ---> b2a8fefe8a63
Step 2/4 : RUN apt-get update && apt-get install -y --no-install-recommends     build-essential gcc make cmake gdal-bin postgresql-server-dev-11     expat libexpat1-dev libboost-dev libboost-graph-dev libboost-program-options-dev libpqxx-dev     wget ca-certificates
 ---> Using cache
 ---> ce2f9c425429
Step 3/4 : RUN wget -O pgrouting-3.1.0.tar.gz https://github.com/pgRouting/pgrouting/archive/v3.1.0.tar.gz &&     tar xvfz pgrouting-3.1.0.tar.gz &&     cd pgrouting-3.1.0 &&     mkdir build &&     cd build &&     cmake .. &&     make &&     make install &&     cd / && rm -Rf pgrouting-3.1.0*
 ---> Using cache
 ---> 8700ee10c6bc
Step 4/4 : RUN wget -O osm2pgrouting-2.3.6.tar.gz https://github.com/pgRouting/osm2pgrouting/archive/v2.3.6.tar.gz &&     tar xvfz osm2pgrouting-2.3.6.tar.gz &&     cd osm2pgrouting-2.3.6 &&     cmake -H. -Bbuild &&     cd build &&     make &&     make install &&     cd / && rm -Rf osm2pgrouting-2.3.6*
 ---> Using cache
 ---> e708efbda884

Successfully built e708efbda884
Successfully tagged mellow-bike-map-make:latest
WARNING: Image for service make was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
python manage.py loaddata app/mbm/fixtures/mellowroute.json && touch db/import/mellowroute.table
python: can't open file 'manage.py': [Errno 2] No such file or directory
Makefile:5: recipe for target 'db/import/mellowroute.table' failed
make: *** [db/import/mellowroute.table] Error 2
Beas-MBP:mellow-bike-map beamalsky$ docker-compose -f docker-compose.yml -f db/docker-compose.yml run --rm make
Starting mellow-bike-map-postgres ... done
python manage.py loaddata app/mbm/fixtures/mellowroute.json && touch db/import/mellowroute.table
python: can't open file 'manage.py': [Errno 2] No such file or directory
Makefile:5: recipe for target 'db/import/mellowroute.table' failed
make: *** [db/import/mellowroute.table] Error 2

Do you know what's up here @jeancochrane? Looks like it's having trouble with the Django management command.

Map the South Side of Chicago following the Reader map: https://www.google.com/maps/d/u/0/viewer?mid=17mPyCktdurhbwt9HcBZFSJrXmLBKioYs&ll=41.859429425065585%2C-87.63630865000006&z=13

For our purposes, the "South Side" includes all neighborhoods south of I-55 and south/east of the south branch of the river. This includes:

• Bronzeville
• Bridgeport/McKinley Park/Brighton Park
• Hyde Park/Washington Park/Woodlawn
• Englewood
• Gage Park/Midway
• South Shore/South Chicago
• Chatham/Greater Grand Crossing
• Auburn Gresham
• Far Southwest Side

The core app.js file, which is the entrypoint for the whole frontend application, is almost 400 lines. There's a lot of logic in there that could be named and encapsulated in a function for readability. It also includes some anonymous functions that should be named.

We should break as much code as we can out of that module and name any discrete pieces of logic, purely for readability. We shouldn't do this until we've written tests for the existing functionality in #42

Use the geolocation API to request the user's location.

From an interface perspective, I think it would make the most sense to request the user's location when the page first loads, and if the user grants permission then show their location on the map. Then, in the Source input dropdown, offer Use my location as an option.

Prefer a self-hosted solution.

Right now the frontend only shows you the calculated route, but it doesn't show which streets are marked as mellow. Update the map to always show these streets, with colors in a way such that it's easy for a user to tell which streets on their route are mellow.

Poll for location and update it on the map every so often.

When you open the app, it should try to get your current location and set that as the default source location. It should also zoom to your gps marker once the location is found.

Switch to new domain with new site name.

Similar to the original Mellow Bike Map, we should show a legend element on the map explaining what the different colors mean. Ideally this legend should be easy to toggle on and off so that it doesn't get in the way on mobile.

Try to figure out if there's a way we can allow the user to open the route in a mapping app, e.g. Google Maps or Apple Maps.

The map could use some love. Some things that stick out:

• More friendly input/search elements
• Loading spinner during API requests or responses
• More subdued basemap
• Better colors for routes

Feel free to do these all in one big PR or split them out as you see fit.

Right now the autocomplete dropdown is biased based on your gps location, but that's unreliable and unnecessary. We should replace that code with hardcoded bounds for the city of chicago and consider setting strictBounds.

@jeancochrane suggests taking the coordinates for the Loop and adding a radius of ~20 miles, which is roughly the distance from the Loop to the furthest community that includes routes on our map (Hegewisch).

A small DO droplet or EC2 instance will probably do. I think we'll need 16GB for the database, to be safe.

Right now all mellow routes are stored equally, but we would like to be able to distinguish between paths (protected from cars, e.g. the lakefront trail), routes (city-recommended bike paths, e.g. Milwaukee Ave) and streets (mellow streets). This will require changing the data model, updating the admin interface, and altering the routing algorithm to account for the three different types.

The Reader map uses the following color code to distinguish between the three types:

• Green: streets
• Pink: paths
• Orange: routes

See if there's a way that we can use pgrouting to generate a list of directions in addition to the route geometry.

Based on the citywide map and the new neighborhoods in #28, add routes from the new citywide map.

Looking to add new info to the map about the counterflow bike lane on Sunnyside near Welles park. It's already a mellow street, but it will only give directions in one direction, since it's a one-way street. I'm assuming that there's some issue with the underlying OSM data that makes this tricky. Any thoughts on counterflow lanes?

The ultralight basemap is really nice but is missing two key features:

• Street names
• Markers for one-way streets

Hopefully we can add these elements through the map API.