27 |
28 | ## Creating fare zones
29 |
30 | To create a fare zone for use in fare rules, you must first select a stop that you would like to include in the zone. Click in the `zone_id` dropdown and begin typing the new `zone_id`. Click `Create new zone: [zone_id]` and then save the stop. Repeat for as many zones as needed.
31 |
34 |
35 | Once created and assigned to one or more stop, fare zones can be used when defining fare rules for **From/to zone** or **Contains zone**.
36 |
--------------------------------------------------------------------------------
/docs/user/editor/stops.md:
--------------------------------------------------------------------------------
1 | # Stops
2 |
3 | ## Editing stops
4 |
5 | To begin editing stops, click the map marker icon button on the lefthand navigation bar.
6 |
7 | 
8 |
9 | ## Selecting a stop
10 |
11 | Choose a stop from the list or search by stop name in the dropdown.
12 |
13 | You can also **zoom into the map** while the stop list is visible and once you're close enough you'll begin to see stops displayed. Click one to begin editing its details.
14 |
15 | ## Creating a stop: right-click on map
16 |
17 | To create a new stop, **right-click on the map** in the location you would like to place the stop. **Note:** as with all newly created items (except patterns), the new stop will not be saved until the save icon (💾) is clicked.
18 |
19 | ## Moving a stop
20 |
21 | To move a selected stop simply **click and drag the stop to the new location**. Or, if already you know the latitude and longitude coordinates, you can copy these into the text fields. After moving the stop, click save to keep the changes.
22 |
23 |
27 |
28 | ## View all stops for feed
29 |
30 | To view all stops for a feed, hover over the map layers icon (in the top, lefthand corner of the map) and turn on the `Stop locations` layer. When you do, you'll see all of the stops (which appear as grey circles) for the feed even at wide zoom levels. This layer can be viewed whether or not the stop list is visible, so it can be helpful for users who would like to view stop locations alongside routes or trip patterns.
31 |
32 | 
33 |
34 | Clicking on a stop shown in this layer will select the stop for editing, but be careful—it can be tricky to select the right stop from very far away!
35 |
36 |
37 |
40 |
--------------------------------------------------------------------------------
/docs/user/introduction.md:
--------------------------------------------------------------------------------
1 | # Introduction
2 |
3 | ## Conceptual Overview
4 |
5 | The GTFS Data Manager enables exchange and coordination of data creation, updates, validation and deployment of GTFS data feeds for transit schedules.
6 |
7 | The platform allows GTFS producers (transit operators, local governments, etc.) to share existing feeds or utilize the build function in GTFS Editor to create and maintain feeds. GTFS creators can use the built in validator to check for potential issues.
8 |
9 | ## Data Manager Concepts
10 |
11 | ### Projects
12 |
13 | Projects are collections of feed sources and deployments.
14 |
15 | ### Feed Sources
16 |
17 | Feed sources define the locations or upstream sources of GTFS feeds. These can be any combination of:
18 |
19 | 1. **Manually Uploaded** - Manually collected/managed feeds provided directly by an external source.
20 | 2. **Fetched Automatically** - Public available feeds that can be fetch from a URL
21 | 3. **Produced In House** - Internally managed/created feeds produced by GTFS Editor
22 |
23 | ### Feed Versions
24 |
25 | Feed Versions store specific instances of a GTFS feed for a given feed source as published over time. Each Feed Version has an associated GTFS file that is stored within the Data Manager, can be downloaded by users, and for which detailed information such as validation results is available.
26 |
27 | ### Snapshots
28 |
29 | Internally managed GTFS data sets are pulled from the GTFS Editor using “snapshots” created in the editor interface. These snapshots are static versions of the data set, or save points, that can be exported, or used as starting point for future edits. The Data manager only imports snapshotted versions of feeds. This allows users to ensure the correct version of data is being imported and to retrieve and review data in the future.
30 |
31 | *Note: See section 2.6 in GTFS Editor User Manual for more information on snapshots.*
32 |
--------------------------------------------------------------------------------
/flow-typed/npm/@conveyal/lonlat_v1.x.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: 801d87d0bccd96d1e1a9c0fd6a351c79
2 | // flow-typed version: <>/@conveyal/lonlat_v^1.3.0/flow_v0.37.0
3 |
4 | declare module '@conveyal/lonlat' {
5 | declare type coordinatesInput = [number, number]
6 | declare type objectInput = {
7 | lat?: number,
8 | latitude?: number,
9 | lon?: number,
10 | lng?: number,
11 | longitude?: number
12 | }
13 | declare type pointInput = {x: number, y: number}
14 | declare type standardizedLonLat = {
15 | lat: number,
16 | lon: number
17 | }
18 |
19 | declare export default function normalize(mixed): standardizedLonLat
20 |
21 | declare export function isEqual(mixed, mixed, ?number): boolean
22 | declare export function print(mixed): string
23 | declare export function toCoordinates(mixed): [number, number]
24 | declare export function toLeaflet(mixed): {lat: number, lng: number}
25 | }
26 |
--------------------------------------------------------------------------------
/flow-typed/npm/babel-polyfill_v6.x.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: 28eccd914ac7bd65de204cb1d8d37cfe
2 | // flow-typed version: 7b122e75af/babel-polyfill_v6.x.x/flow_>=v0.30.x
3 |
4 | declare module 'babel-polyfill' {}
5 |
--------------------------------------------------------------------------------
/flow-typed/npm/flow-bin_v0.x.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: 6a5610678d4b01e13bbfbbc62bdaf583
2 | // flow-typed version: 3817bc6980/flow-bin_v0.x.x/flow_>=v0.25.x
3 |
4 | declare module "flow-bin" {
5 | declare module.exports: string;
6 | }
7 |
--------------------------------------------------------------------------------
/flow-typed/npm/isomorphic-fetch_v2.x.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: 47370d221401bec823c43c3598266e26
2 | // flow-typed version: ec28077c25/isomorphic-fetch_v2.x.x/flow_>=v0.25.x
3 |
4 |
5 | declare module 'isomorphic-fetch' {
6 | declare module.exports: (input: string | Request | URL, init?: RequestOptions) => Promise;
7 | }
8 |
--------------------------------------------------------------------------------
/flow-typed/npm/lodash.throttle_v4.x.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: b1bcad4f459d3e23e1460c8b17a4feea
2 | // flow-typed version: <>/lodash.throttle_v^4.1.1/flow_v0.37.0
3 |
4 | declare module 'lodash.throttle' {
5 | declare export default function throttle((...T) => void, number): (...T) => void
6 | }
7 |
--------------------------------------------------------------------------------
/flow-typed/npm/lodash.tolower_v4.x.x.js:
--------------------------------------------------------------------------------
1 | declare module 'lodash.tolower' {
2 | declare export default (string) => string
3 | }
4 |
--------------------------------------------------------------------------------
/flow-typed/npm/lodash.upperfirst_v4.x.x.js:
--------------------------------------------------------------------------------
1 | declare module 'lodash.upperfirst' {
2 | declare export default (string) => string
3 | }
4 |
--------------------------------------------------------------------------------
/flow-typed/npm/object-path_v0.11.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: 8e08c7b448e19eef73737b79fa31c8ae
2 | // flow-typed version: <>/object-path_v0.11.4/flow_v0.53.1
3 |
4 | declare module 'object-path' {
5 | declare module.exports: {
6 | ensureExists(obj: ?Object | Array, string | Array, ?any): ?any,
7 | get(obj: ?Object | Array, string | Array): ?any,
8 | set(obj: ?Object | Array, string, any): ?any
9 | }
10 | }
11 |
--------------------------------------------------------------------------------
/flow-typed/npm/polyline_v0.2.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: e8af478fdd21bcfff8ff15754086c5b2
2 | // flow-typed version: <>/polyline_v^0.2.0/flow_v0.53.1
3 |
4 | type Coordinate = [number, number]
5 |
6 | declare module 'polyline' {
7 | declare module.exports: {
8 | decode(string): Coordinate[],
9 | encode(Coordinate[]): string
10 | }
11 | }
12 |
--------------------------------------------------------------------------------
/flow-typed/npm/prop-types_v15.x.x.js:
--------------------------------------------------------------------------------
1 | // flow-typed signature: d9a983bb1ac458a256c31c139047bdbb
2 | // flow-typed version: 927687984d/prop-types_v15.x.x/flow_>=v0.41.x
3 |
4 | type $npm$propTypes$ReactPropsCheckType = (
5 | props: any,
6 | propName: string,
7 | componentName: string,
8 | href?: string) => ?Error;
9 |
10 | declare module 'prop-types' {
11 | declare var array: React$PropType$Primitive>;
12 | declare var bool: React$PropType$Primitive;
13 | declare var func: React$PropType$Primitive;
14 | declare var number: React$PropType$Primitive;
15 | declare var object: React$PropType$Primitive