In route coverage view, provide way to style/render routes that allow bikes.

In the detail view for a stop, provide option to view walkshed around that stop.

render operator service area polygons using map bbox

or the model is not rereshing

In route coverage view, provide toggle to style routes based on mode or operator

In the stop coverage view, style stops based on service frequency.

Add search bar to routes

and dim others

render stops within bbox on map

• mode color key that only shows modes currently visualized
• operator color key that only shows operators currently visualized
• show count information

In route coverage view, provide option to view routes that are wheelchair accessible.

Show service area polygons for operators in the map view.

@meghanhade an idea to consider: for more information about an OSM way, link to https://openstreetmap.org/way/xxxxx

• display overlapping lines side-by-side
• change line weight based on zoom level

render route polylines using map bbox query param

In route coverage view, style routes based on service frequency.

/explorer/(location)/(model)/(params) or /explorer/(model)/(params)/(location)

Options to view routes or stops for that operator. If route is selected, show route detail view. If stop is selected, show stop detail view.

In the detail view for a stop, provide option to view transitshed from that stop.

TODO:

• remove .travis.yml -- we'll be using CircleCI instead
• create a circle.yml file that looks like https://github.com/transitland/feed-registry/blob/master/circle.yml
• in circle.yml: replace s3://staging.transit.land/feed-registry/ with s3://static-dev.mapzen.com/mobility/explorer/ and replace s3://transit.land/feed-registry/ with s3://static-prod.mapzen.com/mobility/explorer
• in circle.yml remove the two places that read AWS_ACCESS_KEY_ID=${STAGING_AWS_ACCESS_KEY_ID} AWS_SECRET_ACCESS_KEY=${STAGING_AWS_SECRET_ACCESS_KEY}. Keep the rest of the line. We're using the same keys for both dev and prod S3 buckets.
• in config/environments.js add a "staging" environment. It can have the same configuration as "development". This is so you can have two different sets of configuration.
• in config/environment.js set baseURL to equal /mobility/explorer/ in the "staging" and "production" environments. This is so your assets will live under that subdirectory, rather than at the root of the server (as they do when accessing the dev server at, say, http://localhost:4200/)
• try a test deploy from your own system (more about this below). If it works, you should be able to open up https://dev.mapzen.com/mobility/playground/
• add AWS keys to CircleCI environment variables: https://circleci.com/gh/mapzen/mobility-playground/edit#env-vars Keys are on Slack. You'll need to set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
• do a merge or push to master on GitHub and see if CircleCI successfully deploys it to dev.mapzen.com

to test a deploy locally, you'll just run a few of the commands listed in circle.yml:

• set keys locally export AWS_ACCESS_KEY_ID =xxxxx && export AWS_SECRET_ACCESS_KEY=xxxx
• install the awscli library to upload the files to S3: sudo pip install -U awscli
• build the files locally: ember build --environment=staging
• upload to S3: aws s3 sync ./dist s3://static-dev.mapzen.com/mobility/explorer/

Related: https://github.com/mapzen/operations-engineering/issues/329

It sometimes sets to a location in antarctica. Not able to consistently reproduce error.