Coder Social home page Coder Social logo

rtps's Introduction

Regional Transit Screening Platform Toolbox

This tool is in the development phase

A DVRPC web tool to identify different types of transit gaps to assist in making data-driven decisions to evaluate and prioritize transit improvements throughout the region. Built using Javascript ES6 coupled with mapbox-gl for the front-end interface and is powered by a Django REST API and PostgreSQL 9.5 on the back end.

Project Overview

The primary goal of DVRPC's Regional Transit Screening Platform Study was to develop regionally-consistent, data driven tools that the Commission and its planning partners can use to evaluate service, operational, and new capacity transit investments. Before starting the 2050 Long Range Plan (LRP), DVRPC wanted a fresh look at transit throughout the region. The tools aim to separate the worthwhile transit projects on the existing list from those that are less beneficial, and also generate new transit improvement ideas.

This study consists of four primary sections:

  • Network Gaps
  • Transit Accessibility
  • Service Frequency
  • Surface Transit Reliability

Getting Started

cd <project-directory>

git clone https://github.com/dvrpc/RTPS.git

npm install

npm start

rtps's People

Contributors

rbeatty1 avatar mmolta avatar

Watchers

 avatar  avatar

rtps's Issues

reliability legend text edits

Flip words of ridership weighted reliability score to 'Reliability score weighted by ridership'
Use text descriptions on legend for both reliability score layers; lighter is more reliable, darker is less reliable.
On about tab, specify that ridership is a daily average.

Need to change symbology for frequency rail map

The line for the 36 is so light and thin that you can’t see it at all. I know it’s there because I clicked on it accidentally. But I couldn’t click on it again because it’s really hard to select with the hand.

Make data available for download via GIS portal

https://docs.google.com/spreadsheets/d/1cn3EZxMqeQAbt0eRMhi3QJX5MPoRs7DMLkfiWfj1k0E/edit?usp=sharing

I pulled together the data that I want to make available via the GIS portal (once the website is live). I also added some metadata. Let me know if there is additional information I need to provide.

I only want to make data downloadable for one of the 4 maps. The rest are a little too confusing when taken out of context and probably have limited use outside of the webmap. Maybe the landing page for Surface Transit Reliability can have an extra link next to "Learn More" and "Explore" that says "Download." It should probably also be linked inside the Reliability page.

Accessibility Changes

  • new text in google doc
  • change legend to say 'Reachable Destinations' instead of "Number of..." - makes people look for an actual # which we are not providing
  • add case study panel - also outline in google doc, below descriptions
  • reformat to have numbers like the frequency map (as we've talked about); current introduction can take place of 'overview' from frequency map and it can show all the stations and lines with no zones behind as is currently the default when you open accessibility

transit overlay in zonal frequency maps

If it is possible to do this without making the map appear too cluttered, it would be helpful to have a subtle passenger rail overlay in tabs 3 and 4 of the frequency map. if it can only be transit or highway, transit might be more useful in this context.

Move overview text in frequency webmap

The placement of the text in the Overview box (#1) in the frequency map is confusing because it does not describe the specific map being showed. Can the overview and corresponding text have it's own box at the top?

consider shifting demand filter in gap results

Another one for us to think about together. When running tests for Upper Merion we realized that it looks like there is no demand from NJ. In reality, we know that's not true. The demand filter was used to reduce noise, but if someone interprets the map to mean that there is no one going from NJ to the KoP area, it will make people question the results. There could be a way to present this (as a screening tool focusing on the places with the most potential), or there could be a happy medium of demand filters to reduce noise but show more places at the same time. Of those that get filtered out (demand < 1), about 7% have demand between 0.5 and 1. That probably wouldn't add much. Lets test some queries when we meet and decide together.

Update existing frequency map

A new table was added to the RTPS_Gap db (model_avg_freq) to be used to show existing frequency. The avg_freq field shows a 24 hour average weekday frequency in number of trips/hour. The symbology can remain the same using the following breaks: 0-1 = 61+, 1-2 = 31-60, 2-4 = 16-30, 4+ = 0-15.

Move Gap Analysis summary text back to main analysis panel

On Summary panel, have regional summary map access instead? With summary map, include text "This map summarizes the network gap analysis which identifies in demand connections between transit supportive places where transit is either not available or not competitive."

update gap legend and text

I know you know about this one already, but I wanted to make sure I tracked the feedback I got. Add teals to legend. Specify that oranges are for 'Existing transit' and teals are for 'No (or very little) existing transit'

more accessibility text changes

From Shoshana:

  1. on the landing page for this section "Where can station accessibility improvements have the greatest impact for wheelchair users and persons with mobility assistance needs? View data showing destinations reachable via rail by wheelchair users and persons with mobility impairments as compared to all users."
  2. on the Explore page of this section, part 1 "This analysis identifies essential services (jobs, grocery stores, medical offices, etc) that can be reached via transit where wheelchair users and persons with mobility impairments are most impacted by wheelchair inaccessible rail stations. These maps can be used to help prioritize rail station improvements."
  3. on the Explore page of this section, part 2 "This map serves as the baseline. It shows the number of destinations reachable via rail from each zone for passengers that do not need mobility assistance . The darker the color, the more essential service destinations are reachable from that TAZ via rail."
  4. on the Explore page of this section, part 3 "This map shows the destinations reachable by wheelchair users and persons who can only use wheelchair accessible stations. The darker the color, the more essential service destinations are reachable from that TAZ via rail."
  5. on the Explore page of this section, part 4 "This map highlights the differences between the baseline map (1) and wheelchair accessible map (2). The darker the color, the greater the disparity for wheelchair users and persons with mobility impairments in comparison with all users."
  6. on the Explore page of this section, part 5 " This map considers which stations are programmed for wheelchair accessibility and mobility assistance improvements or have improvements in progress. It includes stations that are currently accessible and those that are programmed for improvement. Again, the darker the color, the more essential service destinations are reachable via rail from that zone."
  7. on the Explore page of this section, part 6 "This map compares the previous map (4) to the baseline map (1). It shows where the disparity remains after the programmed wheelchair accessibility and mobility assistance improvements. These are the places that should be the focus of the next batch of wheelchair accessibility and mobility assistance improvements at rail stations."

Reliability text and panel layout udpates

Lets think/talk about this one more together. The idea would be to have the filter at the top of this new panel. You select your route(s) and then turn on the layers you want. The septa passenger loads would only be available on this panel since looking at the regional layer only shows what is on top. The regional layer panel would need a name...

Update legend in Tab 5 of Frequency map

From Bhairevi: 'Tab 5: The legend only shows the color transition, not that of thickness, whereas the change in thickness is more visible than the change in colors. I understood the range of values upon reading the description (some viewers may want the legend to be sufficiently explanatory?) If we keep the legend as is, do you think we can increase the contrast in colors? Or is that with the values we have, more contrasting shades may not accurately represent the numeric range? I know these were the colors we had used, but it feels like the range is clearer in the case of buses than that of the rail, since light blue is closer to the grey background...?'

Update accessibility station table

I updated the accessibility field in the station table in the RTPS_Gap DB. This update needs to be incorporated into the data being used to symbolize the stations in all the maps.

Landing page feedback

Looks fantastic! I know it's a work in progress, but just a few things I wanted to make note of:

  • Can there be more space at the top/bottom of the circles? On my laptop screen, it looks pretty squished.
  • Can we make it so if you click on the RTPP logo at the top, it goes back to the original look of the landing page with the question and gray background?
  • Not sure if it's just on my laptop screen, but when I click on a circle, learn more and explore are partially hidden behind the circles
  • We need to add the link to policies, the contact, etc, that we talked about at DIT yesterday
  • On the individual maps, the top circles look a bit squished (horizontally) on my screen. Is there a way to get a little bit of the horizontal blue line between them, like on the landing page.

Add case study with example of how to interpret results for relevant maps

For example, have 5 panels zoomed in to the same station with text describing how to interpret what you are looking at. Amy's idea for the example station for accessibility was Lombard South. For accessibility, this would be an additional thing to click on in the left panel. I will provide text. This might also apply to some of the other webmaps, but I'm not sure which yet. Just something to keep in mind.

Order of gap analyses

This is for the top bar, but also for the landing page if it will be linear (L to R). Just wanted to be explicit about this in case it impacts color choices throughout.
0. Home

  1. Gap
  2. Reliability
  3. Accessibility
  4. Frequency

update frequency popups

in panel 2, have it read 'transit trips per day'
in panel 3, have it read 'car trips per day'

Network Gap Updates

  • Reorder and rename tabs
  • update text to match that in webmap outline
  • Change green button to read just 'Run'
  • Add title/heading over legend to read 'Transit Gap Priority' and consider switching location of high/low and served/not served if it makes more sense (as in top/bottom of color bar)
  • whatever distribution visualizations you were thinking of? (although not as urgently needed as the rest of these updates and there is a little less room now with more descriptions)
  • is there a relatively easy way to add a toggle-able transit overlay (maybe separated by rail/trolley and bus)
  • Municipality name appears when hovering on map

Add/update text in Accessibility map

Add key assumptions at top with intro paragraph (more detail to be added shortly)

Change wording to avoid 2 different uses of "accessible" (more detail to be added shortly)

Consider left aligning map title text (Greg K)

Make Gap and Reliability stand out more

They should look slightly different and be first. Gap is really a tool while the others are viewers and reliability will get a fair amount of use. Needs a cooler name like Network Gap Analyzer. Greg had the idea to call them out with their own icons on the landing page. We can talk brainstorm more about this in person.

accessibility text changes

  • center legend title
  • change map number references in text to match with clickable map numbers (accounting for 1 being Overview panel)

Add collective filter in reliability map

When building out the reliability map, can you please incorporate the ability to apply a single filter by route to all layers (input and result) when they are turned on.

Frequency maps fixes/changes

  • Right now, when I open the frequency map, nothing shows up until I click on #1 or start scrolling down. The overview box should be visible when this page first loads, even if nothing is on the map yet.
  • Shrink the large gap under 'overview' before the text begins
  • Text updates in [google doc] starting after table (https://docs.google.com/document/d/1WQ8agNV_wEKlhYlbyO3Pylf3AgbnepuivUm-QW3-JQg/edit?usp=sharing)
  • Remove '# minute AM Peak Frequency' from pop-up on panel 2 (keep # trips per hour)
  • No map layers show up for panels 5, 6, and 7
  • Combine panels 6 and 7 (see new text in google doc)
  • Reductions in car trips per day (#4) pop-up should say trips per day instead of passengers per day. I want to double check the rest of the pop-ups for #5 and #6 when they are visible again.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.