Allow mode selection - Githubissues

mitTransportAnalyst / CoAXs

An interactive transit corridor “modifier/builder,” available as a web based tool and intended for use as an interactive, browser-based tool presented in an interactive transit exhibit.

Other

13 stars 3 forks source link

Allow mode selection #14

Closed ansoncfit closed 9 years ago

ansoncfit commented 9 years ago

Transit vs. walking. Appears that bike access to transit is not yet supported by Analyst Server.

kuanb commented 9 years ago

This is applied to the left side, right? We don't hard set that into a submitted scenario from the right map, I would imagine.

ansoncfit commented 9 years ago

Yes, this applies to the left side. Part of the API request, but not affected by anything related to a given scenario.

kuanb commented 9 years ago

Kuan: Spend 5 minutes and see if this is easy / possible with current API.

ansoncfit commented 9 years ago

Expecting API endpoints in place next week. For reference,

all MBTA (no routeTypes removed)
local transit (commuter rail [gtfs route_type = 2] and ferry [gtfs route_type = 4] removed)
bus (commuter rail, ferry, subway [gtfs route_type = 1], and light rail [gtfs route_type = 0] removed)
walking (all routeTypes removed)

ansoncfit commented 9 years ago

And similar to #13 , this should be a one-off request.

All of the options in the Travel Time control panel section are one-off (i.e. not cached). The cached results for the scenarios assume no removed routeTypes and peak service.

kuanb commented 9 years ago

All MBTA: 0, 1, 2, 3, 4, 5, 6, 7

Local Tranist: 0, 1, 3, 5, 6, 7

Bus: 3, 5, 6, 7

Walking: ~none~

kuanb commented 9 years ago

https://github.com/mitTransportAnalyst/CoAXs/commit/7710f64e236001dbc1b320220d963e726ed4ee0c resolves

kuanb commented 9 years ago

error on routeType alter and control against point snap logic

kuanb commented 9 years ago

fixed w: https://github.com/mitTransportAnalyst/CoAXs/commit/f34ba968b15dae33288ff2fdba698bc410f9a398