conveyal / taui

Serverless dynamic personalized transit accessibility

Taui

Running

Clone the repository and with yarn and node v10 installed run yarn run dev. Taui is built and run with next.js and now.

Configuration

Copy the empty-store.json file to store.json. This file populates the data used for running a Taui.

Key fields:

• allowChangeConfig -- Set to false when deploying a site for a user.
• map.accessToken -- A Mapbox access token is required for Mapbox GL maps and Mapbox Geocoding to work.
• grids -- Point sets or opportunities can be set here.
• networks -- A url to an S3 bucket containing the results of regional analysis generated from R5.
• poiUrl -- URL to a GeoJSON file that contains a FeatureCollection of Points to be shown on the map. Add a label to the properties field of each point.

Deployment

taui's Issues

Compare two scenarios

We need to be able to compare multiple scenarios, e.g. current and future. These would just be separate static site outputs.

Use react-dock for panel

Show path taken

We want to show the path that was taken to reach the destination, as in @kchanba's mock, and the average time to reach the destination:

End marker offset by small amount

Arbitrary transitive config

I fixed #27 by monkeying about with the code that initializes transitive. However, we should just have the option to specify arbitrary transitive options in the config. I looked into this and couldn't figure out how the config system works---somehow new config items are put into the redux store I guess?

Accessibility display is broken

It always says "0 jobs" even though I can see the mutator occurring that is supposed to change the number:

Route names on map don't match those on cards

Error in transitive renderer

Once zoomed in the transitive display becomes wildly out of place. No errors, not sure what's going on exactly. See here: http://mamp-static.s3-website-eu-west-1.amazonaws.com/#start=21%20Place%20Notre-Dame%20du%20Mont%2C%20Marseille%2C%20Bouches-du-Rh%C3%B4ne%2013006%2C%20France&end=18%20Lotissement%20le%20Domaine%20des%20Solleillades%2C%20Marseille%2C%20Bouches-du-Rh%C3%B4ne%2013011%2C%20France for an example.

Geocoder box text stays present after clearing field

When you click in the origin or destination field after already having entered information in the geocoder, the text is not cleared visually, although it is evidently cleared from the component, as pressing enter does nothing until a new address has been entered.

Configuration Changes

We're going to have a lot of separate future configurations. We need to figure out a way to create and manage these.

Config folder

To start, I'm thinking a /config folder with each .js file inside defining a separate configuration. They would get loaded in via an environment variable. For example, running:

$ CONFIG=indyconnect npm build

Would load the /config/indyconnect.js build file.

Environment variables

Passing the configuration data throughout the application is annoying. I'd rather populate the app with process.env.X that get replaced with things like API keys and default data. Loading the entire config file that way would be very convenient. Envify might be able to help with that...

Many identical paths

e.g. this:

This is a browsochrones issue I believe.

Rename project

We should probably call this analysis-static-ui.

Retain address entry after searching for address

After searching for and selecting an address, the entered address disappears from the address entry box. We should retain the search or, better yet, the normalized address name coming from the geocoder.

Lat/lng representation

GeoJSON uses coordinates in the form of: [${longitude}, ${latitude}].
Leaflet uses latlng in the form of: { lat: ${latitude}, lng: ${longitude} } ... along with a few others.
turf-point is a GeoJSON Feature object using coordinates.

Pfft. Create a helper that normalizes this?

Offline use

We need to make TAUI function offline, without uploading graphs to S3, etc.

TAUI tab pegs 4 processors

When I'm using TAUI with some data generated for NL, it uses 400% CPU constantly.

Here's the config:

{
  "grids": [],
  "networks": [
    {
      "name": "Redesign",
      "url": "https://d2z7d5345ccuw9.cloudfront.net/5ba0dc6737ed817c0d6bd4e5",
      "showOnMap": true
    },
    {
      "name": "Baseline",
      "url": "https://d2z7d5345ccuw9.cloudfront.net/5ba0dc6737ed817c0d6bd4e5",
      "showOnMap": true
    }
  ]
}

Note this does not have any opportunity data. Is that the source of the problem? If so we should make it work normally without opportunity data, it's good for checking out results quickly, or just showing isochrones.

I18N: "show" is not translated in the static site UI

Use Mapzen Geocoder

Geocoder results in Indianapolis

The geocoder results in Indianapolis are not up to snuff. For example, our default address of 111 Monument Circle, Indianapolis, IN becomes 111 Monument Circle, Center, IN (using township name rather than city name). This is an upstream issue in Pelias: pelias/pelias#184. However, we do need to fix it ASAP for our deployment, maybe just switch back to Mapbox geocoding?

Use redux-effects-fetch for retrieving data

GeoJSON isochrones don't lineup with Gridualizer steps

The interpolation algorithms in jsolines (https://github.com/conveyal/jsolines/blob/master/index.js#L278) may be different than the ones in Gridualizer (https://github.com/conveyal/gridualizer/blob/dev/lib/interpolators/bicubic.js).

Select pre-defined origin and destination points

Add to store.yml, can be done with just "links" using query parameters.

Use react-select-geocoder

GeoJSON "properties" missing on download

"properties" is null which is invalid GeoJSON and fails to load in certain applications.

Show two isochrones at once

Rather than toggling between different isochrones, it would be nice to see them overlaid. This implies some interaction changes though. If you've got only two layers this is just a configuration option to always show all isochrones at once. If you've got more than two, you'd need to be able to toggle them on/off, or maybe show the last two that were clicked or something.

Also ideally to be included in a static site delivered by September 8, but lower priority.

Auto load origin and destination at startup

Isoline issue

Probably a bug in conveyal/jsolines

Vary time cutoff

We need to be able to vary the time cutoff for both accessibility and isochrones. We can now quickly calculate isochrones are arbitrary cutoffs, we just need to connect it to the UI.

Put accessibility breakdown into cards

Let's put separate accessibility breakdowns for new and old routes into cards, so that clicking on them can change which isochrone is displayed on the map.

Make transitive snap to streets at a higher zoom level

Folks in Indianapolis want to snap to streets sooner.

Show old paths and old isochrones on map

Right now the map always shows the paths from the new route, as well as the isochrones from the new route. Clicking on the route cards should change the map display.

Negative signs on increases in travel time

If we're saying "slower" we don't need to put the sign of the change in the app:

Set grid icons manually, not just guessing based on the name

Metric Icon guesses the correct Font Awesome icon to use based off of the name of the grid. Let's add a setting to the grid so that we can set it manually.

From src/components/route-card:

function MetricIcon ({
  name
}) {
  const lc = name.toLowerCase()
  if (lc.indexOf('job') !== -1) return <Icon type='building' />
  if (lc.indexOf('worker') !== -1) return <Icon type='child' />
}

Debug lag caused by transitive rendering repeatedly

Showing Transitive paths makes isochrone updates slow

When you haven't selected a destination, the isochrones update smoothly when the travel time slider is changed.

After you select a destination and the Transitive route visualization is enabled, the updating is much slower. I assume the routes are being recalculated and redrawn every time the slider moves, even though the slider cannot affect the routes.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Take everything Browsochrones-ish out of Redux flow

Putting too much in actions? Not sure it just seems unnecessarily complex and heavy this way.

Jump to location based on URL

Feature request for upcoming delivery of static site to client: include map center point and zoom level in URL so the map goes to a particular location on page load. For embedding different parts of one big result set into a site within different iframes.

This will ideally be included in a site delivered by September 8.

Switch off Webpack

Todos:

• browserify-css
• Remove out webpack-hot
• budo

Wording changes

Isoline time cutoff should become "highlight area accessible within"

Old route should become "current route"

Deduplicate pattern names in route cards

When there are multiple patterns on the same route, the cards are showing something like Red / Red. We should deduplicate the route names.