AdminInterface

The admin interface looks like this and is accessible at /api/admin/index

There are a couple of sections here. The first four items under 'Items requiring review' are things that are used to handle new agencies and GTFS feeds, and should generally be used in order.

'Feeds with no agencies' will show a list of GTFS feeds that have not been matched to agencies. When you go to the page, it will show information from a single GTFS feed at the top. If you start typing the name of an agency in the box, it will show possible matches. If you click on one of these names, the feed will be assigned to that agency (selecting with the keyboard does not currently work).

At this point, you can click on 'Agencies with no metros' which will attempt to automatch all the agencies with no metros to metro areas based on GTFS feed geometries. There is currently no automated way to fix those that fail to match. During this automatching process, these are the things that can happen:

• If an agency overlaps exactly one metro area, it is added to that metro area.
• If an agency overlaps several metro areas but only one has transit, all of the metro areas are merged together.
• If an agency overlaps several metro areas and more than one have transit, it is flagged and goes to the agencies with multiple metros section. This is to prevent a feed for an intercity carrier from merging, say, Chicago, San Francisco, New York, Cleveland, Dallas and Los Angeles together.
• If an agency does not match a metro at all, a new metro is created.

If there are still unmapped agencies at the end of all that, it means something in the process failed; most likely the agency has no geometry because it either a) has no feeds, or b) has no feeds that OneBusAway was able to parse successfully.

If you click on 'Agencies matching multiple metro areas', you will see a screen showing all the agencies with multiple metros on the left, and a list of the metros they match on the right. You can do one of three things: merge all the matched areas together (be aware that this can create very large graphs), put the agency in each metro (meaning that, in every metro, the agency will be available for trips, but that you won't be able to transfer between two metros using this. For instance, if you were to add the train from Emeryville, CA to Chicago, IL to the metros in San Francisco and Chicago you could plan trips on the long-distance train in each of those cities, but you couldn't plan a trip involving BART, Amtrak and CTA, for instance. To clarify, a trip involving Amtrak and CTA would work, or a trip involving BART and Amtrak, but not all three at once. The third option is to just disable the agency.

The next option, 'Metro areas needing rebuild', allows you to rebuild all the metros which have been marked as needing it. These are agencies that have been modified through the admin interface; when new GTFS comes in, rebuild are automatic. Unfortunately, this is not linked with the CRUD interface; you'll need to trigger a manual rebuild if you edit that way (either by setting the needsUpdate field of the requisite metro area to true, or by manaully generating a rebuild using the ID of the metro area in the admin interface (see below).

The next two options have to do with Google Mapping and are documented there.

Under 'Other tasks', the item 'Configure real-time updates' allows one to configure what GTFS-realtime feeds are added to the deployed instances. When you click on that, you will be asked to choose an agency, again using the autocomplete box that requires the user to click on completions. When you have clicked on an agency, you will see a list of that agency's GTFS feeds; you can add real time feeds to each GTFS feed. Clicking the save link saves only the GTFS feed you are working on, i.e. other feeds for the same agency are not saved (multiple GTFS-realtime feeds are OK though).

'Remove unreferenced stored feeds' looks through the feed storer you have defined and finds feeds that are not referenced by the database and prompts you to remove them. Be aware that if you are storing your feeds in S3 and there are other things in your bucket, those will be removed as well, so look through the list carefully before agreeing to delete anything. This is generally no longer needed; it's useful when the import process crashes (which doesn't happen much anymore unless you run out of memory or disk space, or there is a hardware or software failure outside of Dashboard).

'Map feeds to agencies' is a bulk mapper for mapping between feeds and agencies, and has the same functionality as 'Feeds with no agencies'. Simply search and select agencies on the left and feeds on the right, then click 'connect'; all the selected items will be connected.

'Fetch new GTFS' will run all the updaters in your Spring configuration. These updaters are also run every morning at 2:37 am America/New_York (assuming the server time is set to UTC; they are run at 7:37 am server local time).

'Generate deployment plans for all enabled metros with transit' will generate rebuilds for every enabled metro with transit and send them to deployer (if specified in the configuration.

'Split metro metro area ID into number parts' will take you to the metro area splitter.

'Create deployment plan for metro area id using a window starting yyyy-MM-dd and lasting n days, and send it to URL' will create a deployment plan for the given metro and send it to the given URL. This will also clear scheduled rebuilds for the given metro, &c. It is useful when there is a non-GTFS change (e.g. OSM or OTP) that is known to affect a metro. All the fields can be left blank (or default) except for the metro area ID; if the URL is left blank, no deployment plan will be sent (it will just be displayed in or downloaded by your browser).