transitland / mobility-explorer

Understand transportation networks around the world using Transitland open data and Valhalla routing engine APIs

Mobility Explorer

---

October 2020: Try the new global transit map on the Transitland v2 website. The Transitland v1 Datastore API, which powers Mobility Explorer, is now deprecated. It will be supported for the time being, but we encourage all users and developers to learn more about the Transitland v2 website and APIs.

---

Mobility Explorer helps you understand transportation networks around the world. Search for a place or browse the map, and use the buttons to view transit routes, stops, and operators.

Use Mobility Explorer to query and visualize transit data from Transitland, a community-edited, open transit data aggregation project, and to analyze access using an instance of the Valhalla routing engine.

User Documentation

• Overview
• Tutorial
• Explore Transit
• Isochrones
• Map Matching

Prerequisites

You will need the following things properly installed on your computer.

• Git
• Node.js (with NPM)
• Bower
• Ember CLI

Installation

• git clone <repository-url> this repository
• change into the new directory
• npm install
• bower install

Running / Development

• ember server
• Visit your app at http://localhost:4200.

Code Generators

Make use of the many generators for code, try ember help generate for more details

Building

• ember build (development)
• ember build --environment production (production)

Further Reading / Useful Links

• ember.js
• ember-cli
• Development Browser Extensions
  • ember inspector for chrome
  • ember inspector for firefox

mobility-explorer's Issues

query param for operator id

Option to view all routes by single mode.

render stops

render stops within bbox on map

render route lines

render route polylines using map bbox query param

create stop and route model

UX: explanatory copy

route polyline style improvements

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

Style routes by wheelchair accessibility

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

Deploy to servers

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

Route coverage map: frequency

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

each time an action is triggered in search bar, the map adds data

Stop coverage map: frequency

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

query param for stop id

UI: link to query

Create route structure

UI: dynamic legends

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

feature suggestion: link to openstreetmap.org for more info on ways

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

Operator detail link/render routes served by operator

Route detail link/render stops along route

Route details don't render immediately

Operator coverage map

Show service area polygons for operators in the map view.

leaflet bbox sometimes gets set to incorrect value

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

Create mixin for bbox query param

UI: collapsing menu

UI: full window map

Sometimes onestop_id query param is too sticky

Stop detail link to route operator

query isn't using bounding box

or the model is not rereshing

search bar

Add search bar to routes

Map zoom problems (yo-yo map)

Stop detail link/render routes serving stop

Stop hover detail view not rendering correctly

Operator detail view

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.

render map bounds using bbox param

Switch to Mapzen tiles

render operator polygons

render operator service area polygons using map bbox

pagination is limiting results returned from API

map doesn't reload properly upon route change

Stop detail view: travelshed (integrate isochrone service)

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

query param for route id

Style routes by bike accessibility

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

Route detail link to operator

UI: location search

Choose way to format location in URL

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

UI: nav buttons

Disable map mouse zoom on touch devices

hightlight selected stop/route/operator

and dim others

Style routes by mode/operator

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

Stop detail view: walkshed

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

Operator detail link to stops served by operator