1_75403
@@ -146,4 +146,4 @@ If a situation affects a stop directly (as opposed to the routes serving that st
### Trip-Specific Situations
-If a situation affects a specific trip or a call (an arrival/departure) at a stop by a specific trip, it will appear in the `` element of the `` element.
+If a situation affects a specific trip or a call (an arrival/departure) at a stop by a specific trip, it will appear in the **``** element of the **``** element.
diff --git a/src/api/where/elements/stop.md b/src/api/where/elements/stop.md
index f27c5c9..a80024c 100644
--- a/src/api/where/elements/stop.md
+++ b/src/api/where/elements/stop.md
@@ -3,7 +3,7 @@ layout: page
title: Stop Element
---
-The `` element models stops in OneBusAway. Stops are directly mapped from entries in the [GTFS stops.txt](http://code.google.com/transit/spec/transit_feed_specification.html#stops_txt___Field_Definitions) file from the GTFS feeds that power an API instance.
+The **``** element models stops in OneBusAway. Stops are directly mapped from entries in the [GTFS stops.txt](http://code.google.com/transit/spec/transit_feed_specification.html#stops_txt___Field_Definitions) file from the GTFS feeds that power an API instance.
## Example
@@ -34,7 +34,7 @@ The following fields are optional:
* code
* wheelchairBoarding
-The following values are supported for the `` element:
+The following values are supported for the **``** element:
* ACCESSIBLE
* NOT_ACCESSIBLE
diff --git a/src/api/where/elements/trip-details.md b/src/api/where/elements/trip-details.md
index 59ded51..2930e56 100644
--- a/src/api/where/elements/trip-details.md
+++ b/src/api/where/elements/trip-details.md
@@ -1,9 +1,9 @@
---
layout: page
-title: tripDetails Element
+title: tripDetails Element**`
---
-The `` element captures extended information about a particular
+The **``** element captures extended information about a particular
trip, potentially including the trip instance information, schedule, status, and
active service alert information. It is returned as a sub-element in a number of API calls. For example:
@@ -39,27 +39,27 @@ active service alert information. It is returned as a sub-element in a number o
## Details
-We start with the `tripId` for the trip, which can be used to look up the
-referenced [`` element](/api/where/elements/trip) in the ``
+We start with the **`tripId`** for the trip, which can be used to look up the
+referenced [**``**](/api/where/elements/trip) elements in the **``**
section.
-Next we have optional trip instance information, including the ``
-and optional [`` element](/api/where/elements/frequency).
+Next we have optional trip instance information, including the **``**
+and optional [**``**](/api/where/elements/frequency) element.
-The optional `` element captures real-time information about the trip,
-where applicable. For more details on the `` element, see the [``](/api/where/elements/trip-status).
+The optional **``** element captures real-time information about the trip,
+where applicable. For more details on the **``** element, see the [**``**](/api/where/elements/trip-status).
-The `` section, which includes the following elements:
+The **``** section, which includes the following elements:
-* timeZone - the id of the default time zone for this trip
-* stopTimes - specific details about which stops are visited during the course of the trip and at what times. See `` below for more info.
-* previousTripId - if this trip is part of a block and has an incoming trip from another route, this element will give the id of the incoming trip
-* nextTrip - if this trip is part of a block and has an outgoing trip to another route, this element will give the id of the outgoing trip
+* **`timeZone`** - the id of the default time zone for this trip
+* **`stopTimes`** - specific details about which stops are visited during the course of the trip and at what times. See **``** below for more info.
+* **`previousTripId`** - if this trip is part of a block and has an incoming trip from another route, this element will give the id of the incoming trip
+* **`nextTrip`** - if this trip is part of a block and has an outgoing trip to another route, this element will give the id of the outgoing trip
-Details about the `` element. Note that arrival and departure times are the scheduled times and do not reflect real-time arrival information, even if it's available:
+Details about the **``** element. Note that arrival and departure times are the scheduled times and do not reflect real-time arrival information, even if it's available:
-* arrivalTime - time, in seconds since the start of the service date, when the trip arrives at the specified stop
-* departureTime - time, in seconds since the start of the service date, when the trip arrives at the specified stop
-* stopId - the stop id of the stop visited during the trip
+* **`arrivalTime`** - time, in seconds since the start of the service date, when the trip arrives at the specified stop
+* **`departureTime`** - time, in seconds since the start of the service date, when the trip arrives at the specified stop
+* **`stopId`** - the stop id of the stop visited during the trip
-Finally, the `` element contains ids for any active [`` elements](/api/where/elements/situation) that currently apply to the trip.
+Finally, the **``** element contains ids for any active [**``**](/api/where/elements/situation) elements that currently apply to the trip.
diff --git a/src/api/where/elements/trip-status.md b/src/api/where/elements/trip-status.md
index 56b2867..1db2794 100644
--- a/src/api/where/elements/trip-status.md
+++ b/src/api/where/elements/trip-status.md
@@ -3,10 +3,10 @@ layout: page
title: tripStatus Element
---
-The `` element captures information about the current status of a transit vehicle serving a trip. It is returned as a sub-element in a number of API calls. For example:
+The **``** element captures information about the current status of a transit vehicle serving a trip. It is returned as a sub-element in a number of API calls. For example:
* [arrivals-and-departures-for-stop](/api/where/methods/arrivals-and-departures-for-stop)
-* Any method that returns a [`` element](/api/where/elements/trip-details).
+* Any method that returns a [**``**](/api/where/elements/trip-details) element.
## Example
@@ -49,27 +49,27 @@ The `` element captures information about the current status of a t
## Details
-* `activeTripId` - the trip id of the trip the vehicle is actively serving. All trip-specific values will be in reference to this active trip
-* `blockTripSequence` - the index of the active trip into the sequence of trips for the active block. Compare to `blockTripSequence` in the [`` element](/api/where/elements/arrival-and-departure) to determine where the active block location is relative to an arrival-and-departure.
-* `serviceDate` - time, in ms since the unix epoch, of midnight for start of the service date for the trip.
-* `frequency` - information about [frequency based scheduling](/api/where/elements/frequency), if applicable to the trip - *OPTIONAL*
-* `scheduledDistanceAlongTrip` - the distance, in meters, the transit vehicle is scheduled to have progress along the active trip. This is an optional value, and will only be present if the trip is in progress. *OPTIONAL*
-* `totalDistanceAlongTrip` - the total length of the trip, in meters
-* `position` - current position of the transit vehicle. This element is optional, and will only be present if the trip is actively running. If real-time arrival data is available, the position will take that into account, otherwise the position reflects the scheduled position of the vehicle. *OPTIONAL*
-* `orientation` - the orientation of the transit vehicle, as an angle in degrees. Here, 0º is east, 90º is north, 180º is west, and 270º is south. This is an optional value that may be extrapolated from other data. *OPTIONAL*
-* `closestStop` - the id of the closest stop to the current location of the transit vehicle, whether from schedule or real-time predicted location data
-* `closestStopTimeOffset` - the time offset, in seconds, from the closest stop to the current position of the transit vehicle among the stop times of the current trip. If the number is positive, the stop is coming up. If negative, the stop has already been passed.
-* `nextStop` and `nextStopTimeOffset` - these are similar to the existing `closestStop` and `closestStopTimeOffset`, except that it always captures the next stop, not the closest stop. Optional, as a vehicle may have progressed past the last stop in a trip. *OPTIONAL*
-* `occupancyStatus` - name() values of GTFS-RT `OccupancyStatus` enum if available
-* `phase` - the current journey phase of the trip (more docs to come)
-* `status` - status modifiers for the trip (more docs to come)
-* `predicted` - true if we have real-time arrival info available for this trip
-* `lastUpdateTime` - the last known real-time update from the transit vehicle. Will be zero if we haven't heard anything from the vehicle.
-* `lastLocationUpdateTime` - the last known real-time *location* update from the transit vehicle. This is different from `lastUpdateTime` in that it reflects the last know location update. An update from a vehicle might not contain location info, which means this field will not be updated. Will be zero if we haven't had a location update from the vehicle.
-* `lastKnownLocation` - last known location of the transit vehicle. This differs from the existing `position` field, in that the position field is potential extrapolated forward from the last known position and other data. *OPTIONAL*
-* `lastKnownDistanceAlongTrip` - the last known distance along trip value received in real-time from the transit vehicle. *OPTIONAL*
-* `lastKnownOrientation` - the last known orientation value received in real-time from the transit vehicle. *OPTIONAL*
-* `distanceAlongTrip` - the distance, in meters, the transit vehicle has progressed along the active trip. This is an optional value that will only be present if the underlying AVL system supplies it and is potential extrapolated from the last known reading to the current time.
-* `scheduleDeviation` - if real-time arrival info is available, this lists the deviation from the schedule in seconds, where positive number indicates the trip is running late and negative indicates the trips is running early. If not real-time arrival info is available, this will be zero.
-* `vehicleId` - if real-time arrival info is available, this lists the id of the transit vehicle currently running the trip. *OPTIONAL*
-* `situationIds` - references to [`` elements](/api/where/elements/situation), for active service alerts applicable to this trip. *OPTIONAL*
+* **`activeTripId`** - the trip id of the trip the vehicle is actively serving. All trip-specific values will be in reference to this active trip
+* **`blockTripSequence`** - the index of the active trip into the sequence of trips for the active block. Compare to **`blockTripSequence`** in the [**``**](/api/where/elements/arrival-and-departure) element to determine where the active block location is relative to an arrival-and-departure.
+* **`serviceDate`** - time, in ms since the unix epoch, of midnight for start of the service date for the trip.
+* **`frequency`** - information about [frequency based scheduling](/api/where/elements/frequency), if applicable to the trip - *OPTIONAL*
+* **`scheduledDistanceAlongTrip`** - the distance, in meters, the transit vehicle is scheduled to have progress along the active trip. This is an optional value, and will only be present if the trip is in progress. *OPTIONAL*
+* **`totalDistanceAlongTrip`** - the total length of the trip, in meters
+* **`position`** - current position of the transit vehicle. This element is optional, and will only be present if the trip is actively running. If real-time arrival data is available, the position will take that into account, otherwise the position reflects the scheduled position of the vehicle. *OPTIONAL*
+* **`orientation`** - the orientation of the transit vehicle, as an angle in degrees. Here, 0º is east, 90º is north, 180º is west, and 270º is south. This is an optional value that may be extrapolated from other data. *OPTIONAL*
+* **`closestStop`** - the id of the closest stop to the current location of the transit vehicle, whether from schedule or real-time predicted location data
+* **`closestStopTimeOffset`** - the time offset, in seconds, from the closest stop to the current position of the transit vehicle among the stop times of the current trip. If the number is positive, the stop is coming up. If negative, the stop has already been passed.
+* **`nextStop`** and **`nextStopTimeOffset`** - these are similar to the existing **`closestStop`** and * **`closestStopTimeOffset`**, except that it always captures the next stop, not the closest stop. Optional, as a vehicle may have progressed past the last stop in a trip. *OPTIONAL*
+* **`occupancyStatus`** - name() values of GTFS-RT **`OccupancyStatus`** enum if available
+* **`phase`** - the current journey phase of the trip (more docs to come)
+* **`status`** - status modifiers for the trip (more docs to come)
+* **`predicted`** - true if we have real-time arrival info available for this trip
+* **`lastUpdateTime`** - the last known real-time update from the transit vehicle. Will be zero if we haven't heard anything from the vehicle.
+* **`lastLocationUpdateTime`** - the last known real-time *location* update from the transit vehicle. This is different from **`lastUpdateTime`** in that it reflects the last know location update. An update from a vehicle might not contain location info, which means this field will not be updated. Will be zero if we haven't had a location update from the vehicle.
+* **`lastKnownLocation`** - last known location of the transit vehicle. This differs from the existing **`position`** field, in that the position field is potential extrapolated forward from the last known position and other data. *OPTIONAL*
+* **`lastKnownDistanceAlongTrip`** - the last known distance along trip value received in real-time from the transit vehicle. *OPTIONAL*
+* **`lastKnownOrientation`** - the last known orientation value received in real-time from the transit vehicle. *OPTIONAL*
+* **`distanceAlongTrip`** - the distance, in meters, the transit vehicle has progressed along the active trip. This is an optional value that will only be present if the underlying AVL system supplies it and is potential extrapolated from the last known reading to the current time.
+* **`scheduleDeviation`** - if real-time arrival info is available, this lists the deviation from the schedule in seconds, where positive number indicates the trip is running late and negative indicates the trips is running early. If not real-time arrival info is available, this will be zero.
+* **`vehicleId`** - if real-time arrival info is available, this lists the id of the transit vehicle currently running the trip. *OPTIONAL*
+* **`situationIds`** - references to [**``**](/api/where/elements/situation) elements, for active service alerts applicable to this trip. *OPTIONAL*
diff --git a/src/api/where/elements/trip.md b/src/api/where/elements/trip.md
index 7739725..3205f4c 100644
--- a/src/api/where/elements/trip.md
+++ b/src/api/where/elements/trip.md
@@ -3,7 +3,7 @@ layout: page
title: Trip Element
---
-The `` element models trips in OneBusAway. Trips are directly mapped from entries in the [GTFS trips.txt](http://code.google.com/transit/spec/transit_feed_specification.html#trips_txt___Field_Definitions) file from the GTFS feeds that power an API instance.
+The **``** element models trips in OneBusAway. Trips are directly mapped from entries in the [GTFS trips.txt](http://code.google.com/transit/spec/transit_feed_specification.html#trips_txt___Field_Definitions) file from the GTFS feeds that power an API instance.
## Example
@@ -23,4 +23,4 @@ The fields of the stop element closely match the fields defined for trips in the
A few important details:
-* The only fields that are absolutely required are `id`, `routeId`, and `serviceId`.
\ No newline at end of file
+* The only fields that are absolutely required are **`id`**, **`routeId`**, and **`serviceId`**.
\ No newline at end of file
diff --git a/src/api/where/elements/vehicle-status.md b/src/api/where/elements/vehicle-status.md
index 481bb47..abd3cd9 100644
--- a/src/api/where/elements/vehicle-status.md
+++ b/src/api/where/elements/vehicle-status.md
@@ -3,7 +3,7 @@ layout: page
title: vehicleStatus Element
---
-The `` element captures extended information about an active
+The **``** element captures extended information about an active
vehicle.
## Example
@@ -24,11 +24,11 @@ vehicle.
## Details
-* vehicledId - the id of the vehicle
-* lastUpdateTime - the last known real-time update from the transit vehicle
-* lastLocationUpdateTime - the last known real-time update from the transit vehicle containing a location update
-* location - the last known location of the vehicle
-* tripId - the id of the vehicle's current trip, which can be used to look up the referenced [`` element](/api/where/elements/trip) in the `` section.
-* tripStatus - [`` element](/api/where/elements/trip-status), providing additional status information for the vehicle's trip.
+* **`vehicledId`** - the id of the vehicle
+* **`lastUpdateTime`** - the last known real-time update from the transit vehicle
+* **`lastLocationUpdateTime`** - the last known real-time update from the transit vehicle containing a location update
+* **`location`** - the last known location of the vehicle
+* **`tripId`** - the id of the vehicle's current trip, which can be used to look up the referenced [**``**](/api/where/elements/trip) element in the **``** section.
+* **`tripStatus`** - [**``**](/api/where/elements/trip-status) element, providing additional status information for the vehicle's trip.
A vehicle may not have an actively assigned trip.
\ No newline at end of file
diff --git a/src/api/where/index.erb b/src/api/where/index.erb
index 4ab7aa0..24aa21a 100644
--- a/src/api/where/index.erb
+++ b/src/api/where/index.erb
@@ -15,7 +15,7 @@ title: OneBusAway RESTful API
The following parameter must be included in all API requests:
- key - your assigned application keykey - your assigned application key
Example:
@@ -33,21 +33,21 @@ of ways.
Supported output formats include JSON and XML. The output format is determined by the request extension. For example:
-/some/api/call.xml
+/some/api/call.xml
will return XML results, while
-/some/api/call.json
+/some/api/call.json
-will return JSON. The JSON method all supports a callback parameter, which is useful for cross-site
+
will return JSON. The JSON method all supports a callback parameter, which is useful for cross-site
scripting access:
-/some/api/call.json?callback=some_function_name
+/some/api/call.json?callback=some_function_name
will return:
-some_function_name({"key":value,...})
+some_function_name({"key":value,...})
Response Element
@@ -69,22 +69,22 @@ of ways.
The response element carries the following fields:
- version - response version informationversion - response version information- code - a machine-readable response code with the following semantics:
- 200 - Success400 - The request could not be understood due to an invalid request parameter or some other error
+ 200 - Success400 - The request could not be understood due to an invalid request parameter or some other error
401 - The application key is either missing or invalid404 - The specified resource was not found500 - A service exception or error occurred while processing the request401 - The application key is either missing or invalid404 - The specified resource was not found500 - A service exception or error occurred while processing the request
- text - a human-readable version of the response codecurrentTime - current system time on the api server as milliseconds since the unix epochdata - the response payload
+ text - a human-readable version of the response codecurrentTime - current system time on the api server as milliseconds since the unix epochdata - the response payload
- references see the discussion of references belowreferences see the discussion of references below
@@ -92,10 +92,10 @@ of ways.
References
- The <references/> element contains a dictionary of objects referenced by the main result payload.
+ The <references/> element contains a dictionary of objects referenced by the main result payload.
For elements that are often repeated in the result payload, the elements are instead included in the
- <references/> section and the payload will refer to elements by and object id that can be used to
- lookup the object in the <references/> dictionary.
+ <references/> section and the payload will refer to elements by and object id that can be used to
+ lookup the object in the <references/> dictionary.
@@ -130,10 +130,10 @@ of ways.
- Every API method supports an optional includeReferences=true|false parameter that determines if the
- <references/> section is included in a response. If you don't need the contents of the
- <references/> section, perhaps because you've pre-cached all the elements, then setting
- includeReferences=false can be a good way to reduce the response size.
+ Every API method supports an optional includeReferences=true|false parameter that determines if the
+ <references/> section is included in a response. If you don't need the contents of the
+ <references/> section, perhaps because you've pre-cached all the elements, then setting
+ includeReferences=false can be a good way to reduce the response size.
Methods
@@ -181,8 +181,8 @@ of ways.
- - Millisecond since the epoch:
time=1365259214945
- - "Human-friendly":
time=yyyy-MM-dd_HH-mm-ss
+ - Millisecond since the epoch:
time=1365259214945
+ - "Human-friendly":
time=yyyy-MM-dd_HH-mm-ss
In human-friendly mode, the time will be parsed relative to the timezone where the OBA server is operating.
\ No newline at end of file
diff --git a/src/api/where/methods/agencies-with-coverage.md b/src/api/where/methods/agencies-with-coverage.md
index a647e01..08d4fbf 100644
--- a/src/api/where/methods/agencies-with-coverage.md
+++ b/src/api/where/methods/agencies-with-coverage.md
@@ -36,6 +36,6 @@ http://api.pugetsound.onebusaway.org/api/where/agencies-with-coverage.xml?key=TE
The response has the following fields:
-* `agencyId` - an agency id for the agency whose coverage is included. Should match an [`` element](/api/where/elements/agency) referenced in the `` section.
-* `lat` and `lon` - indicates the center of the agency's coverage area
-* `latSpan` and `lonSpan` - indicate the height (lat) and width (lon) of the coverage bounding box for the agency.
\ No newline at end of file
+* **`agencyId`** - an agency id for the agency whose coverage is included. Should match an [**``**](/api/where/elements/agency) element referenced in the **``** section.
+* **`lat`** and **`lon`** - indicates the center of the agency's coverage area
+* **`latSpan`** and **`lonSpan`** - indicate the height (lat) and width (lon) of the coverage bounding box for the agency.
\ No newline at end of file
diff --git a/src/api/where/methods/agency.md b/src/api/where/methods/agency.md
index 05b64d6..d02b92d 100644
--- a/src/api/where/methods/agency.md
+++ b/src/api/where/methods/agency.md
@@ -32,9 +32,9 @@ http://api.pugetsound.onebusaway.org/api/where/agency/1.xml?key=TEST
## Request Parameters
-* `id` - the id of the agency, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/agency/[ID GOES HERE].xml`
+* **`id`** - the id of the agency, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/agency/[ID GOES HERE].xml`**
### Response
-For more details on the fields returned for an agency, see the documentation for the [`` element](/api/where/elements/agency).
+For more details on the fields returned for an agency, see the documentation for the [**``**](/api/where/elements/agency) element.
diff --git a/src/api/where/methods/arrival-and-departure-for-stop.md b/src/api/where/methods/arrival-and-departure-for-stop.md
index 79d2f07..b1d05b3 100644
--- a/src/api/where/methods/arrival-and-departure-for-stop.md
+++ b/src/api/where/methods/arrival-and-departure-for-stop.md
@@ -28,16 +28,16 @@ http://api.pugetsound.onebusaway.org/api/where/arrival-and-departure-for-stop/1_
## Request Parameters
-* `id` - the stop id, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/arrival-and-departure-for-stop/[ID GOES HERE].xml`
-* `tripId` - the trip id of the arriving transit vehicle
-* `serviceDate` - the service date of the arriving transit vehicle
-* `vehicleId` - the vehicle id of the arriving transit vehicle (optional)
-* `stopSequence` - the stop sequence index of the stop in the transit vehicle's trip
-* `time` - by default, the method returns the status of the system right now. However, the system can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps) for details on the format of the `time` parameter.
+* **`id`** - the stop id, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/arrival-and-departure-for-stop/[ID GOES HERE].xml`**
+* **`tripId`** - the trip id of the arriving transit vehicle
+* **`serviceDate`** - the service date of the arriving transit vehicle
+* **`vehicleId`** - the vehicle id of the arriving transit vehicle (optional)
+* **`stopSequence`** - the stop sequence index of the stop in the transit vehicle's trip
+* **`time`** - by default, the method returns the status of the system right now. However, the system can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps) for details on the format of the **`time`** parameter.
-The key here is uniquely identifying which arrival you are interested in. Typically, you would first make a call to [arrivals-and-departures-for-stop](/api/where/methods/arrivals-and-departures-for-stop) to get a list of upcoming arrivals and departures at a particular stop. You can then use information from those results to specify a particular arrival. At minimum, you must specify the trip id and service date. Additionally, you are also encouraged to specify the vehicle id if available to help disambiguate between multiple vehicles serving the same trip instance. Finally, you are encouraged to specify the stop sequence. This helps in the situation when a vehicle visits a stop multiple times during a trip (it happens) plus there is performance benefit on the back-end as well.
+The key here is uniquely identifying which arrival you are interested in. Typically, you would first make a call to [**`arrivals-and-departures-for-stop`**](/api/where/methods/arrivals-and-departures-for-stop) to get a list of upcoming arrivals and departures at a particular stop. You can then use information from those results to specify a particular arrival. At minimum, you must specify the trip id and service date. Additionally, you are also encouraged to specify the vehicle id if available to help disambiguate between multiple vehicles serving the same trip instance. Finally, you are encouraged to specify the stop sequence. This helps in the situation when a vehicle visits a stop multiple times during a trip (it happens) plus there is performance benefit on the back-end as well.
## Response
-The method returns an [`` element](/api/where/elements/arrival-and-departure) as its content.
+The method returns an [**``**](/api/where/elements/arrival-and-departure) element as its content.
diff --git a/src/api/where/methods/arrivals-and-departures-for-stop.md b/src/api/where/methods/arrivals-and-departures-for-stop.md
index e72d4d4..f080f02 100644
--- a/src/api/where/methods/arrivals-and-departures-for-stop.md
+++ b/src/api/where/methods/arrivals-and-departures-for-stop.md
@@ -35,18 +35,18 @@ http://api.pugetsound.onebusaway.org/api/where/arrivals-and-departures-for-stop/
## Request Parameters
-* `id` - the stop id, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/arrivals-and-departures-for-stop/[ID GOES HERE].xml`
-* `minutesBefore=n` - include vehicles having arrived or departed in the previous n minutes (default=5)
-* `minutesAfter=n` - include vehicles arriving or departing in the next n minutes (default=35)
-* `time` - by default, the method returns the status of the system right now. However, the system
+* **`id`** - the stop id, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/arrivals-and-departures-for-stop/[ID GOES HERE].xml`**
+* **`minutesBefore=n`** - include vehicles having arrived or departed in the previous n minutes (default=5)
+* **`minutesAfter=n`** - include vehicles arriving or departing in the next n minutes (default=35)
+* **`time`** - by default, the method returns the status of the system right now. However, the system
can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps)
- for details on the format of the `time` parameter.
+ for details on the format of the **`time`** parameter.
## Response
-The response is primarily composed of [`` elements](/api/where/elements/arrival-and-departure), so see the element documentation for specific details.
+The response is primarily composed of [**``**](/api/where/elements/arrival-and-departure) elements, so see the element documentation for specific details.
The nearby stop list is designed to capture stops that are very close by (like across the street) for quick navigation.
diff --git a/src/api/where/methods/block.md b/src/api/where/methods/block.md
index c52d303..44c6b7b 100644
--- a/src/api/where/methods/block.md
+++ b/src/api/where/methods/block.md
@@ -31,9 +31,9 @@ http://api.pugetsound.onebusaway.org/api/where/block/1_5678585.xml?key=TEST
## Request Parameters
-* id - the id of the block, encoded directly in the url:
- * `http://api.pugetsound.onebusaway.org/api/where/block/[ID GOES HERE].xml`
+* **`id`** - the id of the block, encoded directly in the url:
+ * **`http://api.pugetsound.onebusaway.org/api/where/block/[ID GOES HERE].xml`**
## Response
-See details about the various properties of the [`` element](/api/where/elements/block-configuration).
+See details about the various properties of the [**``**](/api/where/elements/block-configuration) element.
diff --git a/src/api/where/methods/current-time.md b/src/api/where/methods/current-time.md
index 6351aa3..34f9e28 100644
--- a/src/api/where/methods/current-time.md
+++ b/src/api/where/methods/current-time.md
@@ -27,5 +27,5 @@ http://api.pugetsound.onebusaway.org/api/where/current-time.xml?key=TEST
## Response
-* `time` - current system time as milliseconds since the Unix epoch
-* `readableTime` - current system time in [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format
\ No newline at end of file
+* **`time`** - current system time as milliseconds since the Unix epoch
+* **`readableTime`** - current system time in [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format
\ No newline at end of file
diff --git a/src/api/where/methods/report-problem-with-stop.md b/src/api/where/methods/report-problem-with-stop.md
index 6eac721..a8de198 100644
--- a/src/api/where/methods/report-problem-with-stop.md
+++ b/src/api/where/methods/report-problem-with-stop.md
@@ -26,18 +26,18 @@ http://api.pugetsound.onebusaway.org/api/where/report-problem-with-stop/1_75403.
## Request Parameters
-* stopId - the trip id, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/report-problem-with-stop/[ID GOES HERE].xml`
-* code - a string code identifying the nature of the problem
- * `stop_name_wrong` - the stop name in OneBusAway differs from the actual stop's name
- * `stop_number_wrong` - the stop number in OneBusAway differs from the actual stop's number
- * `stop_location_wrong` - the stop location in OneBusAway differs from the actual stop's location
- * `route_or_trip_missing` - an expected route or trip is missing from the stop
- * `other` - catch-all for everythign else
-* userComment - additional comment text supplied by the user describing the problem
-* userLat - the reporting user's current latitude
-* userLon - the reporting user's current longitude
-* userLocationAccuracy - the reporting user's location accuracy, in meters
+* **`stopId`** - the trip id, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/report-problem-with-stop/[ID GOES HERE].xml`**
+* **`code`** - a string code identifying the nature of the problem
+ * **`stop_name_wrong`** - the stop name in OneBusAway differs from the actual stop's name
+ * **`stop_number_wrong`** - the stop number in OneBusAway differs from the actual stop's number
+ * **`stop_location_wrong`** - the stop location in OneBusAway differs from the actual stop's location
+ * **`route_or_trip_missing`** - an expected route or trip is missing from the stop
+ * **`other`** - catch-all for everythign else
+* **`userComment`** - additional comment text supplied by the user describing the problem
+* **`userLat`**- the reporting user's current latitude
+* **`userLon`** - the reporting user's current longitude
+* **`userLocationAccuracy`** - the reporting user's location accuracy, in meters
In general, everything but the stop id itself is optional, but generally speaking, providing more fields in the report
will make it easier to diagnose the actual underlying problem. Note that while we record specific location information
diff --git a/src/api/where/methods/report-problem-with-trip.md b/src/api/where/methods/report-problem-with-trip.md
index 2d378df..fc2eb18 100644
--- a/src/api/where/methods/report-problem-with-trip.md
+++ b/src/api/where/methods/report-problem-with-trip.md
@@ -26,24 +26,24 @@ http://api.pugetsound.onebusaway.org/api/where/report-problem-with-trip/1_794302
## Request Parameters
-* tripId - the trip id, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/report-problem-with-trip/[ID GOES HERE].xml`
-* serviceDate - the service date of the trip
-* vehicleId - the vehicle actively serving the trip
-* stopId - a stop id indicating the stop where the user is experiencing the problem
-* code - a string code identifying the nature of the problem
- * `vehicle_never_came`
- * `vehicle_came_early` - the vehicle arrived earlier than predicted
- * `vehicle_came_late` - the vehicle arrived later than predicted
- * `wrong_headsign` - the headsign reported by OneBusAway differed from the vehicle's actual headsign
- * `vehicle_does_not_stop_here` - the trip in question does not actually service the indicated stop
- * `other` - catch-all for everythign else
-* userComment - additional comment text supplied by the user describing the problem
-* userOnVehicle - true/false to indicate if the user is on the transit vehicle experiencing the problem
-* userVehicleNumber - the vehicle number, as reported by the user
-* userLat - the reporting user's current latitude
-* userLon - the reporting user's current longitude
-* userLocationAccuracy - the reporting user's location accuracy, in meters
+* **`tripId`** - the trip id, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/report-problem-with-trip/[ID GOES HERE].xml`**
+* **`serviceDate`** - the service date of the trip
+* **`vehicleId`** - the vehicle actively serving the trip
+* **`stopId`** - a stop id indicating the stop where the user is experiencing the problem
+* **`code`** - a string code identifying the nature of the problem
+ * **`vehicle_never_came`**
+ * **`vehicle_came_early`** - the vehicle arrived earlier than predicted
+ * **`vehicle_came_late`** - the vehicle arrived later than predicted
+ * **`wrong_headsign`** - the headsign reported by OneBusAway differed from the vehicle's actual headsign
+ * **`vehicle_does_not_stop_here`** - the trip in question does not actually service the indicated stop
+ * **`other`** - catch-all for everythign else
+* **`userComment`** - additional comment text supplied by the user describing the problem
+* **`userOnVehicle`** - true/false to indicate if the user is on the transit vehicle experiencing the problem
+* **`userVehicleNumber`** - the vehicle number, as reported by the user
+* **`userLat`** - the reporting user's current latitude
+* **`userLon`** - the reporting user's current longitude
+* **`userLocationAccuracy`** - the reporting user's location accuracy, in meters
In general, everything but the trip id itself is optional, but generally speaking, providing more fields in the report
will make it easier to diagnose the actual underlying problem. Note that while we record specific location information
diff --git a/src/api/where/methods/route-ids-for-agency.md b/src/api/where/methods/route-ids-for-agency.md
index 9135f14..b439f88 100644
--- a/src/api/where/methods/route-ids-for-agency.md
+++ b/src/api/where/methods/route-ids-for-agency.md
@@ -30,9 +30,9 @@ http://api.pugetsound.onebusaway.org/api/where/route-ids-for-agency/40.xml?key=T
## Request Parameters
-* id - the id of the agency, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/route-ids-for-agency/[ID GOES HERE].xml?key=TEST`
+* **`id`** - the id of the agency, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/route-ids-for-agency/[ID GOES HERE].xml?key=TEST`**
## Response
-Returns a list of all route ids for routes served by the specified agency. Note that `` elements for the referenced routes will NOT be included in the `` section, since there are potentially a large number of routes for an agency.
\ No newline at end of file
+Returns a list of all route ids for routes served by the specified agency. Note that **``** elements for the referenced routes will NOT be included in the **``** section, since there are potentially a large number of routes for an agency.
\ No newline at end of file
diff --git a/src/api/where/methods/route.md b/src/api/where/methods/route.md
index 09a1d99..f0f5e1f 100644
--- a/src/api/where/methods/route.md
+++ b/src/api/where/methods/route.md
@@ -43,9 +43,9 @@ http://api.pugetsound.onebusaway.org/api/where/route/1_100224.xml?key=TEST
## Request Parameters
-* `id` - the id of the route, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/route/[ID GOES HERE].xml`
+* **`id`** - the id of the route, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/route/[ID GOES HERE].xml`**
## Response
-See details about the various properties of the [`` element](/api/where/elements/route).
+See details about the various properties of the [**``**](/api/where/elements/route) element.
diff --git a/src/api/where/methods/routes-for-agency.md b/src/api/where/methods/routes-for-agency.md
index 351ce9a..d1d8f9e 100644
--- a/src/api/where/methods/routes-for-agency.md
+++ b/src/api/where/methods/routes-for-agency.md
@@ -35,9 +35,9 @@ http://api.pugetsound.onebusaway.org/api/where/routes-for-agency/1.xml?key=TEST
## Request Parameters
-* id - the id of the agency, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/routes-for-agency/[ID GOES HERE].xml`
+* **`id`** - the id of the agency, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/routes-for-agency/[ID GOES HERE].xml`**
## Response
-Returns a list of all route ids for routes served by the specified agency. See the full description for the [`` element](/api/where/elements/route).
+Returns a list of all route ids for routes served by the specified agency. See the full description for the [**``**](/api/where/elements/route) element.
diff --git a/src/api/where/methods/routes-for-location.md b/src/api/where/methods/routes-for-location.md
index f0798b9..23c1e27 100644
--- a/src/api/where/methods/routes-for-location.md
+++ b/src/api/where/methods/routes-for-location.md
@@ -28,14 +28,14 @@ http://api.pugetsound.onebusaway.org/api/where/routes-for-location.xml?key=TEST&
## Request Parameters
-* lat - The latitude coordinate of the search center
-* lon - The longitude coordinate of the search center
-* radius - The search radius in meters (optional)
-* latSpan/lonSpan - An alternative to `radius` to set the search bounding box (optional)
-* query - A specific route short name to search for (optional)
+* **`lat`** - The latitude coordinate of the search center
+* **`lon`** - The longitude coordinate of the search center
+* **`radius`** - The search radius in meters (optional)
+* **`latSpan/lonSpan`** - An alternative to **`radius`** to set the search bounding box (optional)
+* **`query`** - A specific route short name to search for (optional)
-If you just specify a lat,lon search location, the `routes-for-location` method will just return nearby routes. If you specify an optional `query` parameter, we'll search for nearby routes with the specified route short name. This is the primary method from going from a user-facing route name like "44" to the actual underlying route id unique to a route for a particular transit agency.
+If you just specify a lat,lon search location, the **`routes-for-location`** method will just return nearby routes. If you specify an optional **`query`** parameter, we'll search for nearby routes with the specified route short name. This is the primary method from going from a user-facing route name like "44" to the actual underlying route id unique to a route for a particular transit agency.
## Response
-The `routes-for-location` method returns a [list result](/api/where/elements/list-result), so see additional documentation on controlling the number of elements returned and interpreting the results. The list contents are [`` elements](/api/where/elements/route).
+The **`routes-for-location`** method returns a [**`list result`**](/api/where/elements/list-result), so see additional documentation on controlling the number of elements returned and interpreting the results. The list contents are [**``**](/api/where/elements/route) elements.
diff --git a/src/api/where/methods/schedule-for-route.md b/src/api/where/methods/schedule-for-route.md
index 752052e..fd0a39a 100644
--- a/src/api/where/methods/schedule-for-route.md
+++ b/src/api/where/methods/schedule-for-route.md
@@ -61,10 +61,10 @@ http://api.pugetsound.onebusaway.org/api/where/schedule-for-route/97_9.xml?key=T
## Request Parameters
-* id - the route id to request the schedule for, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/schedule-for-route/[ID_GOES_HERE].xml`
-* date - The date for which you want to request a schedule of the format YYYY-MM-DD (optional, defaults to current date)
- * `http://api.pugetsound.onebusaway.org/api/where/schedule-for-route/[ID_GOES_HERE].json?key=[KEY]&date=[DATE-GOES-HERE]`
+* **`id`** - the route id to request the schedule for, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/schedule-for-route/[ID_GOES_HERE].xml`**
+* **`date`** - The date for which you want to request a schedule of the format YYYY-MM-DD (optional, defaults to current date)
+ * **`http://api.pugetsound.onebusaway.org/api/where/schedule-for-route/[ID_GOES_HERE].json?key=[KEY]&date=[DATE-GOES-HERE]`**
## Response
@@ -73,15 +73,15 @@ http://api.pugetsound.onebusaway.org/api/where/schedule-for-route/97_9.xml?key=T
The intent of this response is to mimic a traditional schedule-table format for viewing a route. As such the entry includes traditional header information, as well as a section of concentrated schedule information (in the form of stopTripGroupings).
The header information is:
-* `` - the route being looked into - this information is presented in the format `[agency]_[routeIdentifier]`
-* `` - the date being looked at - the date of service in milliseconds since the Unix epoch
-* `` - the Service Ids which contain that route and are live on the specified date - for more information see the [GTFS spec](http://code.google.com/transit/spec/transit_feed_specification.html)
+* **``** - the route being looked into - this information is presented in the format **`[agency]_[routeIdentifier]`**
+* **``** - the date being looked at - the date of service in milliseconds since the Unix epoch
+* **``** - the Service Ids which contain that route and are live on the specified date - for more information see the [GTFS spec](http://code.google.com/transit/spec/transit_feed_specification.html)
The entry also has concentrated schedule information in the form of stopTripGroupings. Each grouping includes:
-* `` - the direction the trips are heading - for more information see the [GTFS spec](http://code.google.com/transit/spec/transit_feed_specification.html)
-* `` - the trip headsign - a string indicting the destination of the trip
-* `` - an ordered list of stop Ids - Each id is of the format `[agency]_[stopIdentifier]`
-* `` - a list of trip Ids that matched by shared direction- Each trip Id is of the format `[agency]_[tripIdentifier]`
+* **``** - the direction the trips are heading - for more information see the [GTFS spec](http://code.google.com/transit/spec/transit_feed_specification.html)
+* **``** - the trip headsign - a string indicting the destination of the trip
+* **``** - an ordered list of stop Ids - Each id is of the format **`[agency]_[stopIdentifier]`**
+* **``** - a list of trip Ids that matched by shared direction- Each trip Id is of the format **`[agency]_[tripIdentifier]`**
Alternate codes:
diff --git a/src/api/where/methods/schedule-for-stop.md b/src/api/where/methods/schedule-for-stop.md
index d95aa0b..adff24b 100644
--- a/src/api/where/methods/schedule-for-stop.md
+++ b/src/api/where/methods/schedule-for-stop.md
@@ -58,35 +58,35 @@ http://api.pugetsound.onebusaway.org/api/where/schedule-for-stop/1_75403.xml?key
## Request Parameters
-* id - the stop id to request the schedule for, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/schedule-for-stop/[ID GOES HERE].xml`
-* date - The date for which you want to request a schedule of the format YYYY-MM-DD (optional, defaults to current date)
+* **`id`** - the stop id to request the schedule for, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/schedule-for-stop/[ID GOES HERE].xml`**
+* **`date`** - The date for which you want to request a schedule of the format YYYY-MM-DD (optional, defaults to current date)
## Response
The response is pretty complex, so we'll describe the details at a high-level along with references to the various elements in the response.
-The response can be considered in two parts. The first part lists specific arrivals and departures at a stop on a given date (`` section) while the second part lists which days the stop currently has service defined (the `` section). By convention, we refer to the arrival and departure time details for a particular trip at a stop as a stop time.
+The response can be considered in two parts. The first part lists specific arrivals and departures at a stop on a given date (**``** section) while the second part lists which days the stop currently has service defined (the **``** section). By convention, we refer to the arrival and departure time details for a particular trip at a stop as a stop time.
-We break up the stop time listings in a couple of ways. First, we split the stop times by route (corresponds to each `` element). We next split the stop times for each route by direction of travel along the route (corresponds to each `` element). Most stops will serve just one direction of a particular route, but some stops will serve both directions, and it may be useful to present those listings separately. Each `` element has a `tripHeadsign` property that indicates the direction of travel.
+We break up the stop time listings in a couple of ways. First, we split the stop times by route (corresponds to each **``** element). We next split the stop times for each route by direction of travel along the route (corresponds to each **``** element). Most stops will serve just one direction of a particular route, but some stops will serve both directions, and it may be useful to present those listings separately. Each **``** element has a **`tripHeadsign`** property that indicates the direction of travel.
-Finally we get down to the unit of a stop time, as represented by the `` element. Each element has the following set of properties:
+Finally we get down to the unit of a stop time, as represented by the **``** element. Each element has the following set of properties:
-* arrivalTime - time in milliseconds since the Unix epoch that the transit vehicle will arrive
-* departureTime - time in milliseconds since the Unix epoch that the transit vehicle will depart
-* tripId - the id for the trip of the scheduled transit vehicle
-* serviceId - the serviceId for the schedule trip (see the [GTFS spec](http://code.google.com/transit/spec/transit_feed_specification.html) for more details
+* **`arrivalTime`** - time in milliseconds since the Unix epoch that the transit vehicle will arrive
+* **`departureTime`** - time in milliseconds since the Unix epoch that the transit vehicle will depart
+* **`tripId`** - the id for the trip of the scheduled transit vehicle
+* **`serviceId`** - the serviceId for the schedule trip (see the [GTFS spec](http://code.google.com/transit/spec/transit_feed_specification.html) for more details)**`
-In addition to all the `` elements, the response also contains `` elements which list out all the days that a particular stop has service. This element has the following properties:
+In addition to all the **``** elements, the response also contains **``** elements which list out all the days that a particular stop has service. This element has the following properties:
-* date - the date of service in milliseconds since the Unix epoch
-* group - we provide a group id that groups `` into collections of days with similar service. For example, Monday-Friday might all have the same schedule and the same group id as result, while Saturday and Sunday have a different weekend schedule, so they'd get their own group id.
+* **`date`** - the date of service in milliseconds since the Unix epoch
+* **`group`** - we provide a group id that groups **``** into collections of days with similar service. For example, Monday-Friday might all have the same schedule and the same group id as result, while Saturday and Sunday have a different weekend schedule, so they'd get their own group id.
-In addition to all the `` elements, the main entry also has the following properties:
+In addition to all the **``** elements, the main entry also has the following properties:
-* date - the active date for the returned calendar
-* stopId - the stop id for the requested stop, which can be used to access the [`` element](/api/where/elements/stop) in the `` section
-* timeZone - the time-zone the stop is located in
+* **`date`**- the active date for the returned calendar
+* **`stopId`** - the stop id for the requested stop, which can be used to access the [**``** ](/api/where/elements/stop) element in the **``** section
+* **`timeZone`** - the time-zone the stop is located in
### Proposed Additions
@@ -109,4 +109,4 @@ In order to better support frequency-based scheduling, we propose the addition o
-Much like the `` currently has a list of `` element that captures scheduled arrivals, we propose the addition of a list of `` elements that capture frequency-based arrivals. The frequency defines the service interval, the frequency of service, and some details about the trip.
+Much like the **``** currently has a list of **``** element that captures scheduled arrivals, we propose the addition of a list of **``** elements that capture frequency-based arrivals. The frequency defines the service interval, the frequency of service, and some details about the trip.
diff --git a/src/api/where/methods/shape.md b/src/api/where/methods/shape.md
index 075a949..1db69c0 100644
--- a/src/api/where/methods/shape.md
+++ b/src/api/where/methods/shape.md
@@ -37,9 +37,9 @@ http://api.pugetsound.onebusaway.org/api/where/shape/1_10002005.xml?key=TEST
## Request Parameters
-* `id` - the shape id, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/shape/[ID GOES HERE].xml`
+* **`id`** - the shape id, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/shape/[ID GOES HERE].xml`**
## Response
-The path is returned as a `` element with a points in the [encoded polyline format](http://code.google.com/apis/maps/documentation/polylinealgorithm.html) defined for Google Maps.
\ No newline at end of file
+The path is returned as a **``** element with a points in the [**`encoded polyline format`**](http://code.google.com/apis/maps/documentation/polylinealgorithm.html) defined for Google Maps.
\ No newline at end of file
diff --git a/src/api/where/methods/stop-ids-for-agency.md b/src/api/where/methods/stop-ids-for-agency.md
index 1a496b4..f7397b8 100644
--- a/src/api/where/methods/stop-ids-for-agency.md
+++ b/src/api/where/methods/stop-ids-for-agency.md
@@ -30,9 +30,9 @@ http://api.pugetsound.onebusaway.org/api/where/stop-ids-for-agency/40.xml?key=TE
## Request Parameters
-* id - the id of the agency, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/stop-ids-for-agency/[ID GOES HERE].xml`
+* **`id`** - the id of the agency, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/stop-ids-for-agency/[ID GOES HERE].xml`**
## Response
-Returns a list of all stop ids for stops served by the specified agency. Note that `` elements for the referenced stops will NOT be included in the `` section, since there are potentially a large number of stops for an agency.
\ No newline at end of file
+Returns a list of all stop ids for stops served by the specified agency. Note that **``** elements for the referenced stops will NOT be included in the **``** section, since there are potentially a large number of stops for an agency.
\ No newline at end of file
diff --git a/src/api/where/methods/stop.md b/src/api/where/methods/stop.md
index c077e4a..08521ae 100644
--- a/src/api/where/methods/stop.md
+++ b/src/api/where/methods/stop.md
@@ -36,9 +36,9 @@ http://api.pugetsound.onebusaway.org/api/where/stop/1_75403.xml?key=TEST
## Request Parameters
-* `id` - the id of the requested stop, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/stop/[ID GOES HERE].xml`
+* **`id`** - the id of the requested stop, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/stop/[ID GOES HERE].xml`**
## Response
-See details about the various properties of the [`` element](/api/where/elements/stop).
\ No newline at end of file
+See details about the various properties of the [**``** ](/api/where/elements/stop) element.
\ No newline at end of file
diff --git a/src/api/where/methods/stops-for-location.md b/src/api/where/methods/stops-for-location.md
index 06c1efc..fd81dee 100644
--- a/src/api/where/methods/stops-for-location.md
+++ b/src/api/where/methods/stops-for-location.md
@@ -29,14 +29,14 @@ http://api.pugetsound.onebusaway.org/api/where/stops-for-location.xml?key=TEST&a
## Request Parameters
-* lat - The latitude coordinate of the search center
-* lon - The longitude coordinate of the search center
-* radius - The search radius in meters (optional)
-* latSpan/lonSpan - An alternative to `radius` to set the search bounding box (optional)
-* query - A specific stop code to search for (optional)
+* **`lat`** - The latitude coordinate of the search center
+* **`lon`** - The longitude coordinate of the search center
+* **`radius`** - The search radius in meters (optional)
+* **`latSpan/lonSpan`** - An alternative to **`radius`** to set the search bounding box (optional)
+* **`query`** - A specific stop code to search for (optional)
-If you just specify a lat,lon search location, the `stops-for-location` method will just return nearby stops. If you specify an optional `query` parameter, we'll search for nearby stops with the specified code. This is the primary method from going from a user-facing stop code like "75403" to the actual underlying stop id unique to a stop for a particular transit agency.
+If you just specify a lat,lon search location, the **`stops-for-location`** method will just return nearby stops. If you specify an optional **`query`** parameter, we'll search for nearby stops with the specified code. This is the primary method from going from a user-facing stop code like "75403" to the actual underlying stop id unique to a stop for a particular transit agency.
## Response
-The `stops-for-location` method returns a [list result](../elements/list-result), so see additional documentation on controlling the number of elements returned and interpreting the results. The list contents are `` elements, so see details about the various properties of the [`` element](../elements/stop).
+The **`stops-for-location`** method returns a [**`list result`**](../elements/list-result), so see additional documentation on controlling the number of elements returned and interpreting the results. The list contents are **``** elements, so see details about the various properties of the [**``** ](../elements/stop) element.
diff --git a/src/api/where/methods/stops-for-route.md b/src/api/where/methods/stops-for-route.md
index 3973477..77b3493 100644
--- a/src/api/where/methods/stops-for-route.md
+++ b/src/api/where/methods/stops-for-route.md
@@ -3,7 +3,7 @@ layout: page
title: stops-for-route Method
---
-Retrieve the set of stops serving a particular route, including groups by direction of travel. The `stops-for-route` method first and foremost provides a method for retrieving the set of stops that serve a particular route. In addition to the full set of stops, we provide various "stop groupings" that are used to group the stops into useful collections. Currently, the main grouping provided organizes the set of stops by direction of travel for the route. Finally, this method also returns a set of polylines that can be used to draw the path traveled by the route.
+Retrieve the set of stops serving a particular route, including groups by direction of travel. The **`stops-for-route`** method first and foremost provides a method for retrieving the set of stops that serve a particular route. In addition to the full set of stops, we provide various "stop groupings" that are used to group the stops into useful collections. Currently, the main grouping provided organizes the set of stops by direction of travel for the route. Finally, this method also returns a set of polylines that can be used to draw the path traveled by the route.
## Sample Request
@@ -53,9 +53,10 @@ http://api.pugetsound.onebusaway.org/api/where/stops-for-route/1_100224.xml?key=
## Request Parameters
-* `id` - The route id, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/stops-for-route/[ID GOES HERE].xml`
-* `includePolylines=true|false` = Optional parameter that controls whether polyline elements are included in the response. Defaults to true.
-* `time=YYYY-MM-DD|epoch` = specify the service date explicitly. Defaults to today.
+* **`id`** - The route id, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/stops-for-route/[ID GOES HERE].xml`**
+* **`includePolylines=true|false`** = Optional parameter that controls whether polyline elements are included in the response. Defaults to true.
+* **`time=YYYY-MM-DD|epoch`** = specify the service date explicitly. Defaults to today.
## Response
+**
\ No newline at end of file
diff --git a/src/api/where/methods/trip-details.md b/src/api/where/methods/trip-details.md
index 91cd370..e31dbb0 100644
--- a/src/api/where/methods/trip-details.md
+++ b/src/api/where/methods/trip-details.md
@@ -32,20 +32,20 @@ http://api.pugetsound.onebusaway.org/api/where/trip-details/1_47805860.xml?key=T
## Request Parameters
-* id - the id of the trip, encoded directly in the URL:
+* **`id`** - the id of the trip, encoded directly in the URL:
* `http://api.pugetsound.onebusaway.org/api/where/trip-details/[ID GOES HERE].xml`
-* serviceDate - the service date for the trip as unix-time in ms (optional). Used to disambiguate different versions of the same trip. See [Glossary#ServiceDate the glossary entry for service date].
-* includeTrip - Can be true/false to determine whether full [``](/api/where/elements/trip) element is included in the `` section. Defaults to true.
-* includeSchedule - Can be true/false to determine whether full `` element is included in the `` section. Defaults to true.
-* includeStatus - Can be true/false to determine whether the full `` element is include in the `` section. Defaults to true.
-* time - by default, the method returns the status of the system right now. However, the system
- can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps)
- for details on the format of the `time` parameter.
+* **`serviceDate`** - the service date for the trip as unix-time in ms (optional). Used to disambiguate different versions of the same trip. See [Glossary#ServiceDate the glossary entry for service date].
+* **`includeTrip`** - Can be true/false to determine whether full [**``**](/api/where/elements/trip) element is included in the **``** section. Defaults to true.
+* **`includeSchedule`** - Can be true/false to determine whether full **``** element is included in the **``** section. Defaults to true.
+* **`includeStatus`** - Can be true/false to determine whether the full **``** element is include in the **``** section. Defaults to true.
+* **`time`** - by default, the method returns the status of the system right now. However, the system
+ can also be queried at a specific time. This can be useful for testing. See [**`timestamps`**](/api/where/#timestamps)
+ for details on the format of the **`time`** parameter.
## Response
-The response `` element is a
-[`` element](/api/where/elements/trip-details) that captures extended
+The response **``** element is a
+[**``** ](/api/where/elements/trip-details) element that captures extended
details about a trip.
The status element will indicate whether the trip is scheduled or canceled.
diff --git a/src/api/where/methods/trip-for-vehicle.md b/src/api/where/methods/trip-for-vehicle.md
index 39e4ba3..b3531ba 100644
--- a/src/api/where/methods/trip-for-vehicle.md
+++ b/src/api/where/methods/trip-for-vehicle.md
@@ -34,17 +34,17 @@ http://api.pugetsound.onebusaway.org/api/where/trip-for-vehicle/1_4210.xml?key=T
## Request Parameters
-* id - the id of the vehicle, encoded directly in the URL:
+* **`id`** - the id of the vehicle, encoded directly in the URL:
* `http://api.pugetsound.onebusaway.org/api/where/trip-for-vehicle/[ID GOES HERE].xml`
-* includeTrip - Can be true/false to determine whether full [`` element](/api/where/elements/trip) is included in the `` section. Defaults to false.
-* includeSchedule - Can be true/false to determine whether full `` element is included in the `` section. Defaults to fale.
-* includeStatus - Can be true/false to determine whether the full `` element is include in the `` section. Defaults to true.
-* time - by default, the method returns the status of the system right now. However, the system
- can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps)
- for details on the format of the `time` parameter.
+* **`includeTrip`** - Can be true/false to determine whether full [**``** ](/api/where/elements/trip) element is included in the **``** section. Defaults to false.
+* **`includeSchedule`** - Can be true/false to determine whether full **``** element is included in the **``** section. Defaults to fale.
+* **`includeStatus`** - Can be true/false to determine whether the full **``** element is include in the **``** section. Defaults to true.
+* **`time`** - by default, the method returns the status of the system right now. However, the system
+ can also be queried at a specific time. This can be useful for testing. See [**`timestamps`**](/api/where/#timestamps)
+ for details on the format of the **`time`** parameter.
## Response
-The respone `` element is a
-[`` element](/api/where/elements/trip-details) that captures extended
+The respone **``** element is a
+[**``** ](/api/where/elements/trip-details) element that captures extended
details about a trip.
diff --git a/src/api/where/methods/trip.md b/src/api/where/methods/trip.md
index 9513992..48d39e6 100644
--- a/src/api/where/methods/trip.md
+++ b/src/api/where/methods/trip.md
@@ -33,9 +33,9 @@ http://api.pugetsound.onebusaway.org/api/where/trip/1_12540399.xml?key=TEST
## Request Parameters
-* id - the id of the trip, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/trip/[ID GOES HERE].xml`
+* **`id`** - the id of the trip, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/trip/[ID GOES HERE].xml`**
## Response
-See details about the various properties of the [`` element](/api/where/elements/trip).
+See details about the various properties of the [**``** ](/api/where/elements/trip) element.
diff --git a/src/api/where/methods/trips-for-location.md b/src/api/where/methods/trips-for-location.md
index 12c3b36..e9ac058 100644
--- a/src/api/where/methods/trips-for-location.md
+++ b/src/api/where/methods/trips-for-location.md
@@ -1,6 +1,6 @@
---
layout: page
-title: trips-for-location Method
+title:
---
@@ -32,19 +32,19 @@ http://api.pugetsound.onebusaway.org/api/where/trips-for-location.xml?key=TEST&a
## Request Parameters
-* lat - The latitude coordinate of the search center
-* lon - The longitude coordinate of the search center
-* latSpan/lonSpan - Set the limits of the search bounding box
-* includeTrip - Can be true/false to determine whether full [`` elements](/api/where/elements/trip) are included in the `` section. Defaults to false.
-* includeSchedule - Can be true/false to determine whether full `` elements are included in the `` section. Defaults to false.
-* time - by default, the method returns the status of the system right now. However, the system
- can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps)
- for details on the format of the `time` parameter.
+* **`lat`** - The latitude coordinate of the search center
+* **`lon`** - The longitude coordinate of the search center
+* **`latSpan/lonSpan`** - Set the limits of the search bounding box
+* **`includeTrip`** - Can be true/false to determine whether full [**``**](/api/where/elements/trip) elements are included in the **``** section. Defaults to false.
+* **`includeSchedule`** - Can be true/false to determine whether full **``** elements are included in the **``** section. Defaults to false.
+* **`time`** - by default, the method returns the status of the system right now. However, the system
+ can also be queried at a specific time. This can be useful for testing. See [**`timestamps`**](/api/where/#timestamps)
+ for details on the format of the **`time`** parameter.
## Response
The response is a list of
-[`` element](/api/where/elements/trip-details) that captures extended
+[**``**](/api/where/elements/trip-details) element that captures extended
details about each active trip. Active trips are ones where the transit vehicle
is currently located within the search radius. We use real-time arrival data to
determine the position of transit vehicles when available, otherwise we
diff --git a/src/api/where/methods/trips-for-route.md b/src/api/where/methods/trips-for-route.md
index 35aea4b..f27647b 100644
--- a/src/api/where/methods/trips-for-route.md
+++ b/src/api/where/methods/trips-for-route.md
@@ -31,22 +31,22 @@ http://api.pugetsound.onebusaway.org/api/where/trips-for-route/1_100224.xml?key=
## Request Parameters
-* id - the id of the route, encoded directly in the URL:
- * `http://api.pugetsound.onebusaway.org/api/where/trips-for-route/[ID GOES HERE].xml`
-* includeStatus - Can be true/false to determine whether full
- [`` elements](/api/where/elements/trip-status) with full real-time
- information are included in the `` section for each ``
+* **`id`** - the id of the route, encoded directly in the URL:
+ * **`http://api.pugetsound.onebusaway.org/api/where/trips-for-route/[ID GOES HERE].xml`**
+* **`includeStatus`** - Can be true/false to determine whether full
+ [**``**](/api/where/elements/trip-status) elements with full real-time
+ information are included in the **``** section for each **``**
element. Defaults to false.
-* includeSchedule - Can be true/false to determine whether full ``
- elements are included in the `` element. Defaults to false.
-* time - by default, the method returns the status of the system right now. However, the system
- can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps)
- for details on the format of the `time` parameter.
+* **`includeSchedule`** - Can be true/false to determine whether full **``**
+ elements are included in the **``** element. Defaults to false.
+* **`time`** - by default, the method returns the status of the system right now. However, the system
+ can also be queried at a specific time. This can be useful for testing. See [**`timestamps`**](/api/where/#timestamps)
+ for details on the format of the **`time`** parameter.
## Response
The response is a list of
-[`` element](/api/where/elements/trip-details) that captures extended
+[**``**](/api/where/elements/trip-details) element that captures extended
details about each active trip. The set of active trips includes any trip that
serves that specified route that is currently active.
The status element will indicate whether the trip is scheduled or canceled.
diff --git a/src/api/where/methods/vehicles-for-agency.md b/src/api/where/methods/vehicles-for-agency.md
index ec04750..108493c 100644
--- a/src/api/where/methods/vehicles-for-agency.md
+++ b/src/api/where/methods/vehicles-for-agency.md
@@ -33,14 +33,14 @@ http://api.onebusaway.org/api/where/vehicles-for-agency/1.xml?key=TEST
## Request Parameters
-* id - the id of the agency, encoded directly in the URL:
- * `http://api.onebusaway.org/api/where/vehicles-for-agency/[ID GOES HERE].xml`
-* time - by default, the method returns the status of the system right now. However, the system
- can also be queried at a specific time. This can be useful for testing. See [timestamps](/api/where/#timestamps)
- for details on the format of the `time` parameter.
+* **`id`** - the id of the agency, encoded directly in the URL:
+ * **`http://api.onebusaway.org/api/where/vehicles-for-agency/[ID GOES HERE].xml`**
+* **`time`** - by default, the method returns the status of the system right now. However, the system
+ can also be queried at a specific time. This can be useful for testing. See [**`timestamps`**](/api/where/#timestamps)
+ for details on the format of the **`time`** parameter.
## Response
The response is a list of
-[`` elements](/api/where/elements/vehicle-status) that captures extended
+[**``**](/api/where/elements/vehicle-status) elements that captures extended
details about each active vehicle associated with the specified agency.
diff --git a/src/downloads.erb b/src/downloads.erb
index 15b0db6..7f4d46f 100644
--- a/src/downloads.erb
+++ b/src/downloads.erb
@@ -7,7 +7,7 @@ title: Downloading the Software
You can download pre-built binaries from Cambridge Systematics's Maven Repository.
Current Version:
- <%= site.metadata.oba_version %>
+ <%= site.metadata.oba_version %>
(Released <%= site.metadata.oba_version_release_date %>)
diff --git a/src/features/sign-mode.md b/src/features/sign-mode.md
index f17412d..05009e7 100644
--- a/src/features/sign-mode.md
+++ b/src/features/sign-mode.md
@@ -14,15 +14,15 @@ should have form like:
http://your.host-name.com/where/standard/stop.action?id=X_Y
-To enable sign mode, simply replace the `standard` part of the URL with `sign`:
+To enable sign mode, simply replace the **`standard`** part of the URL with **`sign`**:
http://your.host-name.com/where/sign/stop.action?id=X_Y
There are a number of parameters you can add to the URL to tweak the behavior of the sign:
-* `title=...` - By default, the sign uses the current stop name as a title. This option allows you to override the title.
-* `showTitle=false` - Alternatively, you can hide the title completely.
-* `route=X_Y` - Specify a route id to indicate that only this route should be show. Can be repeated.
-* `minutesBefore=N` - Excludes vehicles that departed more than N minutes ago.
-* `minutesAfter=N` - Exclude vehicles arriving more than N minutes from now.
-* `refresh=N` - Automatically refresh the page every N seconds.
+* **`title=...`** - By default, the sign uses the current stop name as a title. This option allows you to override the title.
+* **`showTitle=false`** - Alternatively, you can hide the title completely.
+* **`route=X_Y`** - Specify a route id to indicate that only this route should be show. Can be repeated.
+* **`minutesBefore=N`** - Excludes vehicles that departed more than N minutes ago.
+* **`minutesAfter=N`** - Exclude vehicles arriving more than N minutes from now.
+* **`refresh=N`** - Automatically refresh the page every N seconds.
diff --git a/src/guides/api-webapp-configuration-guide.md b/src/guides/api-webapp-configuration-guide.md
index c36a828..033d08b 100644
--- a/src/guides/api-webapp-configuration-guide.md
+++ b/src/guides/api-webapp-configuration-guide.md
@@ -3,13 +3,13 @@ title: API Webapp Configuration Guide
layout: page
---
-This guide will instruct you on how to configure an instance of `onebusaway-api-webapp`. These are specific
+This guide will instruct you on how to configure an instance of **`onebusaway-api-webapp`**. These are specific
configuration instructions, part of your larger OneBusAway installation. The
-`onebusaway-api-webapp` powers the [OneBusAway REST API](/api/where).
+**`onebusaway-api-webapp`** powers the [OneBusAway REST API](/api/where).
## API Keys
-The API service typically expects an API key with each request, as identified by the `key` parameter. The API key
+The API service typically expects an API key with each request, as identified by the **`key`** parameter. The API key
is a loose form of authentication that can be used for simple access control and logging purposes. It also supports
basic connection throttling to prevent a single client from abusing the API service.
@@ -25,7 +25,7 @@ delete API keys, along with determining how much traffic is allowed from the spe
### Creating an API Key in data-sources.xml
-It's possible to create an API key directly in your `data-sources.xml` configuration file. Simply add a section like:
+It's possible to create an API key directly in your **`data-sources.xml`** configuration file. Simply add a section like:
~~~
diff --git a/src/guides/database-configuration-guide.md b/src/guides/database-configuration-guide.md
index 0eddb9e..b26aec5 100644
--- a/src/guides/database-configuration-guide.md
+++ b/src/guides/database-configuration-guide.md
@@ -10,18 +10,18 @@ Here we attempt to describe how to setup and configure data-sources as needed an
To configure your database, you'll need to do the following:
-* Edit your `data-sources.xml` file to specify your JDBC data-source configuration
+* Edit your **`data-sources.xml`** file to specify your JDBC data-source configuration
* Copy the JAR for your JDBC provider into your webapp classpath
Read on for more details.
## Common Config Examples
-The one piece of configuration you'll typically always need to supply is a `dataSource` definition. This provides
+The one piece of configuration you'll typically always need to supply is a **`dataSource`** definition. This provides
information about the JDBC data-source and how to authenticate to it. Since we typically don't want database
configuration information, including usernames and passwords to reside in the public source code, we often define a
-`data-sources.xml` Spring configuration file that is imported by each application but that doesn't get included in SVN.
-In `data-sources.xml`, we define our data-source:
+**`data-sources.xml`** Spring configuration file that is imported by each application but that doesn't get included in SVN.
+In **`data-sources.xml`**, we define our data-source:
~~~
@@ -39,7 +39,7 @@ Notes:
* **DO**: Do make sure you've already created the database where appropriate and that the credentials you've supplied work correctly
* **DON'T**: Don't worry about creating the initial tables in the database. Hibernate should automatically take care of that the first time the application is run.
-Below we include some comon `dataSource` configuration examples.
+Below we include some comon **`dataSource`** configuration examples.
### hsqldb
@@ -84,7 +84,7 @@ An example of using a stand-alone hsqldb instance running as a process:
## Additional Configuration
-Typically, specifying your database `dataSource` is enough configuration for simple uses. However, you may wish to
+Typically, specifying your database **`dataSource`** is enough configuration for simple uses. However, you may wish to
perform more complex configuration, including tweaking the database configuration or adding new classes for persistence.
Read on for more advanced details.
@@ -98,14 +98,14 @@ implementation classes requiring database access.
To understand how Hibernate and Spring work together, let's start with some common Spring bean definitions shared
between all !OneBusAway modules that wish to access a database.
-The `onebusaway-container` module has a resource:
+The **`onebusaway-container`** module has a resource:
src/main/resources/org/onebusaway/container/application-context-hibernate.xml
that does the bulk of the Hibernate configuration, but that also provides extension points so you can configure your
application as appropriate.
-If you take a look at `application-context-hibernate.xml`, you'll see sections like:
+If you take a look at **`application-context-hibernate.xml`**, you'll see sections like:
@@ -129,7 +129,7 @@ SessionFactory bean:
-The only thing that isn't defined with a default is the `dataSource` reference, which you'll always need to provide.
+The only thing that isn't defined with a default is the **`dataSource`** reference, which you'll always need to provide.
Details on the pieces you configure are described below.
## Adding additional Hibernate entity classes
@@ -139,10 +139,10 @@ This typically only needs to be done when you are working inside one of the !One
extend the set of classes that can be serialized to a database or manage the set of stored queries that can operate on
those entity classes.
-The first is to configure them in a `hibernate.cfg.xml` file or by annotated the entity classes with @Entity and other
+The first is to configure them in a **`hibernate.cfg.xml`** file or by annotated the entity classes with @Entity and other
annotations and telling Hibernate to scan the classes directly.
-Both approaches are used by the `onebusaway-transit-data-federation` module, as can be seen in the resource:
+Both approaches are used by the **`onebusaway-transit-data-federation`** module, as can be seen in the resource:
onebusaway-transit-data-federation/src/main/resources/org/onebusaway/transit_data_federation/application-context-common.xml
@@ -167,7 +167,7 @@ Specifically, we specify two overrides:
-The first override add the `RouteCollection` class to the set of annotated classes that will be scanned by the
+The first override add the **`RouteCollection`** class to the set of annotated classes that will be scanned by the
SessionFactory for management by Hibernate. The second add a couple of Hibernate xml mapping files that will included
in the SessionFactory as well.
@@ -177,20 +177,20 @@ The bulk of database operations happen in one of two modules:
### onebusaway-users
-The `onebusaway-users` module uses a database to manage user account information. This module is included by three of
+The **`onebusaway-users`** module uses a database to manage user account information. This module is included by three of
the major UI modules:
* onebusaway-sms-webapp
* onebusaway-phone-webapp
* onebusaway-webapp
-As such, each of the three application modules typically need a `data-sources.xml` resource with the appropriate
-`dataSource` definition pointing to your user database.
+As such, each of the three application modules typically need a **`data-sources.xml`** resource with the appropriate
+**`dataSource`** definition pointing to your user database.
### onebusaway-transit-data-federation
-The `onebusaway-transit-data-federation` archives transit data in a back-end database as well.
+The **`onebusaway-transit-data-federation`** archives transit data in a back-end database as well.
-The main transit data federation application container, `onebusaway-transit-data-federation-webapp` needs a
-`data-sources.xml` resource with the appropriate `dataSource` definition pointing to your transit data database. This is
+The main transit data federation application container, **`onebusaway-transit-data-federation-webapp`** needs a
+**`data-sources.xml`** resource with the appropriate **`dataSource`** definition pointing to your transit data database. This is
typically the same data source you specified when [creating your transit data bundle](/guides/transit-data-bundle-guide).
\ No newline at end of file
diff --git a/src/guides/installation-guide.md b/src/guides/installation-guide.md
index f69dca4..0ef2ece 100644
--- a/src/guides/installation-guide.md
+++ b/src/guides/installation-guide.md
@@ -11,7 +11,7 @@ with your data, check out our [Quickstart guide](/guides/quickstart-guide).
Check out the [Downloads page](/downloads) for information about downloading the OneBusAway application modules.
-At minimum you need to download `onebusaway-transit-data-federation-builder.jar` to build your transit data bundle and
+At minimum you need to download **`onebusaway-transit-data-federation-builder.jar`** to build your transit data bundle and
one of the webapps to host your OneBusAway instance.
## Building a Bundle
@@ -20,7 +20,7 @@ OneBusAway has the concept of a transit data bundle, which is a collection of al
agency (or group of transit agencies) in the internal format needed to power OneBusAway. These transit data bundles
are typically created from external data such as GTFS feeds for transit data.
-You will use the downloaded `onebusaway-transit-data-federation-builder.jar` to build the bundle, but the instructions
+You will use the downloaded **`onebusaway-transit-data-federation-builder.jar`** to build the bundle, but the instructions
are complex enough to deserve their own page:
* [Guide to Building a Transit Data Bundle](/guides/transit-data-bundle-guide)
@@ -32,14 +32,14 @@ choose whichever container you like, but we use Apache Tomcat by default. You c
* [Download Apache Tomcat](http://tomcat.apache.org/)
-Which webapps will you be running? For your first install, we recommend the `onebusaway-combined-webapp.war`, which
+Which webapps will you be running? For your first install, we recommend the **`onebusaway-combined-webapp.war`**, which
combines all the major OneBusAway modules and functionality into one application. It includes the following modules:
-* `onebusaway-transit-data-federation-webapp` - back-end transit data
-* `onebusaway-webapp` - standard web interface
-* `onebusaway-api-webapp` - REST and SIRI api interfaces
-* `onebusaway-sms-webapp` - SMS interface
-* `onebusaway-phone-webapp` - phone (IVR) interface
+* **`onebusaway-transit-data-federation-webapp`** - back-end transit data
+* **`onebusaway-webapp`** - standard web interface
+* **`onebusaway-api-webapp`** - REST and SIRI api interfaces
+* **`onebusaway-sms-webapp`** - SMS interface
+* **`onebusaway-phone-webapp`** - phone (IVR) interface
Optionally, you can also download and run each OneBusAway webapp independently. This is useful when you just need one
piece of OneBusAway functionality or want to do a more complex deployment. See special configuration details towards
@@ -59,15 +59,15 @@ data-sources.xml
This configuration file is just a [Spring bean configuration file](http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/beans.html)
and can be used to define beans and other resources that determine the configuration of your OneBusAway instance.
-The webapps look for `data-sources.xml` in the `WEB-INF/classes` directory of each webapp by default. You can add the
+The webapps look for **`data-sources.xml`** in the **`WEB-INF/classes`** directory of each webapp by default. You can add the
file to the war file directly or copy it into the exploded war directory structure.
### Spring Configuration Example
OneBusAway is powered by a number of Java classes that provide different pieces of functionality. While we try to
provide reasonable default behavior, you may wish to tweak OneBusAway at times. Many options can be set using a
-`PropertyOverrideConfigurer` to override specific class properties. Here is a quick example of the config you'd add
-to your `data-sources.xml` file:
+**`PropertyOverrideConfigurer`** to override specific class properties. Here is a quick example of the config you'd add
+to your **`data-sources.xml`** file:
~~~
@@ -81,8 +81,8 @@ to your `data-sources.xml` file:
~~~
-Here, each `` entry specifies a key and a value. The key takes the form `objectName.propertyName` where
-`objectName` is a OneBusAway object and `propertyName` is a property of that object whose value you'd like to override.
+Here, each **``** entry specifies a key and a value. The key takes the form **`objectName.propertyName`** where
+**`objectName`** is a OneBusAway object and **`propertyName`** is a property of that object whose value you'd like to override.
For the full list of documented configuration options, check out the
[Realtime Config](./realtime-configuration-guide), [API Config](./api-webapp-configuration-guide),
@@ -91,8 +91,8 @@ For the full list of documented configuration options, check out the
### Tomcat and an external data-sources.xml
-As a Tomcat tip, you can override the location of the `data-sources.xml` to point to an external file instead, which is
-handy for injecting `data-sources.xml` without modifying the war. The key is to use a context xml file to define your
+As a Tomcat tip, you can override the location of the **`data-sources.xml`** to point to an external file instead, which is
+handy for injecting **`data-sources.xml`** without modifying the war. The key is to use a context xml file to define your
webapp:
~~~
@@ -106,24 +106,24 @@ webapp:
For more info, see http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
It's important to note that when you override contextConfigLocation in this way, you'll need to additionally import the
-`application-context-webapp.xml` for the webapp you are attempting to configure (it's normally included in the
+**`application-context-webapp.xml`** for the webapp you are attempting to configure (it's normally included in the
'contextConfigLocation' entry in web.xml for the webapp, but we lose it when we override). The location of the webapp
is dependent on the webapps you are using:
-* onebusaway-combined-webapp: classpath:application-context-webapp.xml
+* **onebusaway-combined-webapp** : classpath:application-context-webapp.xml
If you are deploying the webapps individually, the locations are:
-* onebusaway-transit-data-federation-webapp: classpath:org/onebusaway/transit_data_federation/application-context-webapp.xml
-* onebusaway-api-webapp: classpath:org/onebusaway/api/application-context-webapp.xml
-* onebusaway-phone-webapp: classpath:org/onebusaway/phone/application-context-webapp.xml
-* onebusaway-sms-webapp: classpath:org/onebusaway/sms/application-context-webapp.xml
-* onebusaway-webapp: classpath:org/onebusaway/webapp/application-context-webapp.xml
+* **onebusaway-transit-data-federation-webapp** : classpath:org/onebusaway/transit_data_federation/application-context-webapp.xml
+* **onebusaway-api-webapp** : classpath:org/onebusaway/api/application-context-webapp.xml
+* **onebusaway-phone-webapp** : classpath:org/onebusaway/phone/application-context-webapp.xml
+* **onebusaway-sms-webapp** : classpath:org/onebusaway/sms/application-context-webapp.xml
+* **onebusaway-webapp** : classpath:org/onebusaway/webapp/application-context-webapp.xml
## Configuring the Combined Webapp
-There is a minimum amount of configuration you need to perform to prepare the `onebusaway-combined-webapp` to be run.
-At minimum, you need to add the following entries to your `data-sources.xml` file:
+There is a minimum amount of configuration you need to perform to prepare the **`onebusaway-combined-webapp`** to be run.
+At minimum, you need to add the following entries to your **`data-sources.xml`** file:
~~~
@@ -145,7 +145,7 @@ At minimum, you need to add the following entries to your `data-sources.xml` fil
~~~
-The primary configuration element sets your `bundlePath`, pointing to your [Transit Data Bundle](/guides/transit-data-bundle-guide).
+The primary configuration element sets your **`bundlePath`**, pointing to your [Transit Data Bundle](/guides/transit-data-bundle-guide).
In addition, you might optionally consider [changing the default database](/guides/database-configuration-guide) or
[adding a real-time data source](/guides/realtime-configuration-guide).
@@ -159,19 +159,19 @@ For configuration details for each of user-interface components, see the specifi
## Configuring Webapps Independently
-As mentioned previously, there may be situations where you do not wish to use the `onebusaway-combined-webapp.war`, but
+As mentioned previously, there may be situations where you do not wish to use the **`onebusaway-combined-webapp.war`**, but
instead you wish to use the individual OneBusAway webapps. This gives you more power and flexibility for your
installation, but the configuration is more complex as result. As described above, each webapp is configured through
-its own `data-sources.xml` file.
+its own **`data-sources.xml`** file.
-The key issue is that when you run the transit data webapp (`onebusaway-transit-data-federation-webapp`) independently
-of the user interface webapps (`onebusaway-webapp`, `onebusaway-api-webapp`, etc.), you will need to explicitly
+The key issue is that when you run the transit data webapp (**`onebusaway-transit-data-federation-webapp`**) independently
+of the user interface webapps (**`onebusaway-webapp` , `onebusaway-api-webapp`** , etc.), you will need to explicitly
configure an RPC mechanism that allows the webapps to communicate with each other. Details are included below.
#### Configuring onebusaway-transit-data-federation-webapp
-As described above, `onebusaway-transit-data-federation-webapp` does the heavy lifting of exposing the transit data
-bundle to the various user interface modules. As such, the main job of the `data-sources.xml` configuration file for
+As described above, **`onebusaway-transit-data-federation-webapp`** does the heavy lifting of exposing the transit data
+bundle to the various user interface modules. As such, the main job of the **`data-sources.xml`** configuration file for
the webapp is to point to the location of the bundle and the database where you installed the bundle.
See [Database Setup and Configuration](/guides/database-configuration-guide) for more specific details about database
setup and configuration.
@@ -209,11 +209,11 @@ Here is a quick example:
#### Configuring user interface webapps
While each user interface webapp has specific configuration details, they share a lot of configuration in common.
-Specifically, we need to configure where they will find the `onebusaway-transit-data-federation-webapp`. Optionally,
+Specifically, we need to configure where they will find the **`onebusaway-transit-data-federation-webapp`**. Optionally,
you can also override the default database configuration. For more details, see
[Database Setup and Configuration](/guides/database-configuration-guide).
-Each user interface webapp `data-sources.xml` should include these common entries:
+Each user interface webapp **`data-sources.xml`** should include these common entries:
~~~
diff --git a/src/guides/phone-webapp-configuration-guide.md b/src/guides/phone-webapp-configuration-guide.md
index 84303a8..1382027 100644
--- a/src/guides/phone-webapp-configuration-guide.md
+++ b/src/guides/phone-webapp-configuration-guide.md
@@ -3,7 +3,7 @@ title: Phone (IVR) Webapp Configuration Guide
layout: page
---
-This guide will instruct you on how to configure an instance of the `onebusaway-phone-webapp` interactive-voice-response
+This guide will instruct you on how to configure an instance of the **`onebusaway-phone-webapp`** interactive-voice-response
(IVR) phone interface, as described in the [phone service feature guide](/features/phone-and-sms).
## IVR Providers
@@ -26,8 +26,8 @@ exten => 200,2,Agi(agi://localhost:8001/index.agi,60,r)
exten => 200,3,Hangup
~~~
-Here, `localhost` is the hostname where you are running your server and `8001` is the default AGI port used by
-the phone application. You can change the default port by adding the following snippet to your `data-sources.xml`
+Here, **`localhost`** is the hostname where you are running your server and **`8001`** is the default AGI port used by
+the phone application. You can change the default port by adding the following snippet to your **`data-sources.xml`**
config file:
~~~
@@ -46,11 +46,11 @@ The default Asterisk text-to-speech is not great. I had better luck using a tex
generate the speech for the text in my IVR system. Cepstral has products that can probably directly integrate into
Asterisk, but they are a bit pricey when your budget is "as close to free as possible." Instead, I opted for a license
that only allows you to run one text-to-speech session at a time on the command-line and just cache all the results,
-since most of the text in the IVR system ends up being largely static over time. To configure, I installed `swift`,
-the Cepstral text-to-speech application and configured my license. I also installed `sox`, which will be used to
-convert the files produced by `swift` into a form more usable by Asterisk.
+since most of the text in the IVR system ends up being largely static over time. To configure, I installed **`swift`**,
+the Cepstral text-to-speech application and configured my license. I also installed **`sox`**, which will be used to
+convert the files produced by **`swift`** into a form more usable by Asterisk.
-Next, I override the default text-to-speech factory by adding the following to my `data-sources.xml` file:
+Next, I override the default text-to-speech factory by adding the following to my **`data-sources.xml`** file:
~~~
@@ -80,7 +80,7 @@ First, create an xml file with the following syntax that defines translations fo
~~~
-Then add the following configuration to your `data-sources.xml` file:
+Then add the following configuration to your **`data-sources.xml`** file:
~~~
@@ -92,12 +92,12 @@ Then add the following configuration to your `data-sources.xml` file:
~~~
All told, you can tweak pronunciation in four different ways by creating beans that implement the
-`TextModification` interface and tagging
-them with a `` tag. The four supported qualifiers are:
+**`TextModification`** interface and tagging
+them with a **``** tag. The four supported qualifiers are:
-* `destinationPronunciation`: Used to pronounce trip destinations.
-* `routeNumberPronunciation`: Used to pronounce route numbers.
-* `directionPronunciation`: Used to pronounce directions (eg. "north" vs "sount")
-* `locationPronunciation`: Used to pronounce location names.
+* **`destinationPronunciation`**: Used to pronounce trip destinations.
+* **`routeNumberPronunciation`**: Used to pronounce route numbers.
+* **`directionPronunciation`**: Used to pronounce directions (eg. "north" vs "sount")
+* **`locationPronunciation`**: Used to pronounce location names.
You can specify multiple qualifiers for a single bean if it can be used to support multiple pronunciations.
\ No newline at end of file
diff --git a/src/guides/quickstart-guide.md b/src/guides/quickstart-guide.md
index ac890e9..cd5b778 100644
--- a/src/guides/quickstart-guide.md
+++ b/src/guides/quickstart-guide.md
@@ -30,8 +30,8 @@ supports real-time data for delays, service alerts, and vehicle positions in the
You need to download one of the quickstart bundles. Pick a bundle based on what features you are interested in:
-* The full webapp: `onebusaway-quickstart-assembly-webapp.war` - Includes the [REST API](/api/where) and [the web interfaces](/features/web).
-* The API-only webapp: `onebusaway-quickstart-assembly-api-webapp.war` - Includes just the [REST API](/api/where).
+* The full webapp: **`onebusaway-quickstart-assembly-webapp.war`** - Includes the [REST API](/api/where) and [the web interfaces](/features/web).
+* The API-only webapp: **`onebusaway-quickstart-assembly-api-webapp.war`** - Includes just the [REST API](/api/where).
Find links to both of these WAR files on our [Downloads page](/downloads).
@@ -50,7 +50,7 @@ We provide a simple wizard to help you configure and run the OneBusAway quick-st
the downloaded quick-start war file. Follow the steps and you'll be up and running in no time.
**NOTE:** You may need to run the OneBusAway quick-start GUI from the command-line if you want to pass additional
-options to `java`, like specifying more memory or server optimization:
+options to **`java`**, like specifying more memory or server optimization:
~~~
java -Xmx1G -server -jar onebusaway-quickstart-assembly.war
@@ -73,7 +73,7 @@ java -Xmx1G -server -jar onebusaway-quickstart-assembly.war -webapp path/to/crea
Once the webapp has finished startup, browse to [http://localhost:8080/](http://localhost:8080/).
To see more options for configuring the build and the webapp, including adding real-time information, specify the
-`-help` option to get full usage instructions:
+**`-help`** option to get full usage instructions:
~~~
java -jar onebusaway-quickstart-assembly.war -help
diff --git a/src/guides/realtime-configuration-guide.md b/src/guides/realtime-configuration-guide.md
index a68c5bc..8aabafd 100644
--- a/src/guides/realtime-configuration-guide.md
+++ b/src/guides/realtime-configuration-guide.md
@@ -10,7 +10,7 @@ information.
We support [GTFS-realtime](https://developers.google.com/transit/gtfs-realtime) out of the box, including support for trip updates,
vehicle positions, and alerts. To add support, create a
-`GtfsRealtimeSource` bean in your `data-sources.xml` file. Then specify URLs for the three different types of GTFS-realtime data as
+**`GtfsRealtimeSource`** bean in your **`data-sources.xml`** file. Then specify URLs for the three different types of GTFS-realtime data as
properties of the bean. Here is a full example:
~~~
@@ -31,19 +31,19 @@ properties of the bean. Here is a full example:
~~~
-You can additionally specify a `refreshInterval` that controls how often we query the URLs, in seconds. If you
-are deploying a multi-agency instance of OneBusAway, you may also need to specify the `agencyId` or `agencyIds`
+You can additionally specify a **`refreshInterval`** that controls how often we query the URLs, in seconds. If you
+are deploying a multi-agency instance of OneBusAway, you may also need to specify the **`agencyId`** or **`agencyIds`**
of the transit agency to associate the incoming GTFS-realtime data with. This allows you to define multiple incoming
GTFS-realtime data-sources from different agencies in the same system.
-You must provide both a `TripUpdates` feed and a `VehiclePositions` feed in order for OneBusAway to report vehicle positions.
-Without a `TripUpdates` feed OneBusAway will discard the vehicle positions.
+You must provide both a **`TripUpdates`** feed and a **`VehiclePositions`** feed in order for OneBusAway to report vehicle positions.
+Without a **`TripUpdates`** feed OneBusAway will discard the vehicle positions.
## SIRI VM
We support [SIRI](https://www.siri-cen.eu) out of the box, including support for vehicle monitoring (VM) and situation
-exchange (SX). To add support, create a `SiriController`
-bean in your `data-sources.xml` file. Then specify SIRI endpoint requests indicating
+exchange (SX). To add support, create a **`SiriController`**
+bean in your **`data-sources.xml`** file. Then specify SIRI endpoint requests indicating
your SIRI data-source. Here is a full example:
~~~
@@ -70,8 +70,8 @@ your SIRI data-source. Here is a full example:
A number of agencies have Orbital/ACS/Xerox OrbCAD AVL systems. Some agencies have configured the data-export option of
these systems to spit out a CSV file of vehicle locations and schedule deviations for all the vehicles in their fleet,
which is then shared through a webserver. OneBusAway supports data of this form. To add support, create a
-`OrbcadRecordHttpSource`
-bean in your `data-sources.xml` file. Then specify the URL for your real-time data file. Here is a full example:
+**`OrbcadRecordHttpSource`**
+bean in your **`data-sources.xml`** file. Then specify the URL for your real-time data file. Here is a full example:
~~~
@@ -99,8 +99,8 @@ Creating a custom implementation typically involves the following steps:
* Create a Java class that implements your real-time data-source.
* Add your class to the OneBusAway application server class path.
-* Create an instance of your class in your `data-source.xml` file.
-* Have your implementation periodically notify OneBusAway of new real-time data using the `VehicleLocationListener` interface.
+* Create an instance of your class in your **`data-source.xml`** file.
+* Have your implementation periodically notify OneBusAway of new real-time data using the **`VehicleLocationListener`** interface.
Here is a quick example to get you started:
diff --git a/src/guides/transit-data-bundle-guide.md b/src/guides/transit-data-bundle-guide.md
index efc54f3..098a22f 100644
--- a/src/guides/transit-data-bundle-guide.md
+++ b/src/guides/transit-data-bundle-guide.md
@@ -9,7 +9,7 @@ are typically created from external data such as GTFS feeds for transit data. T
## Creating the Bundle
-To create the bundle, you'll need to download the `onebusaway-transit-data-federation` application. Go to the
+To create the bundle, you'll need to download the **`onebusaway-transit-data-federation`** application. Go to the
[Downloads page](/downloads) to download the application.
The jar file is automatically configured to run the main class for building transit data bundles:
@@ -25,15 +25,15 @@ java -jar onebusaway-transit-data-federation-builder.jar ...
~~~
**Note:** Depending on the size of your transit network, you may need to increase the amount of memory available to the
-Java VM with an argument like `java -Xmx1G -jar ...`. If your Java VM supports it, you might also consider adding the
-`-server` argument, as it often makes Java run much faster.
+Java VM with an argument like **`java -Xmx1G -jar ...`**. If your Java VM supports it, you might also consider adding the
+**`-server`** argument, as it often makes Java run much faster.
## Quick Configuration
By default, the builder accepts two command line options:
-* `path/to/your/gtfs.zip` - path to your GTFS feed
-* `bundle_output_path` - the output directory where bundle artifacts will be written
+* **`path/to/your/gtfs.zip`** - path to your GTFS feed
+* **`bundle_output_path`** - the output directory where bundle artifacts will be written
This quick start mode can be used to quickly build a transit data bundle for a single transit agency, but without out
much configuration flexibility. If you need more flexibility, see Advanced Config below.
@@ -42,10 +42,10 @@ much configuration flexibility. If you need more flexibility, see Advanced Conf
The bundle also accepts an xml file command line argument for more advanced configuration options:
-* `bundle.xml` - path to your bundle config xml file
-* `bundle_output_path` - the output directory where bundle artifacts will be written
+* **`bundle.xml`** - path to your bundle config xml file
+* **`bundle_output_path`** - the output directory where bundle artifacts will be written
-The configuration details for the bundle are captured in an xml file. The `bundle.xml` xml config file gives you a lot
+The configuration details for the bundle are captured in an xml file. The **`bundle.xml`** xml config file gives you a lot
of control of how your bundle is built:
* combine multiple GTFS feeds
@@ -121,7 +121,7 @@ is often necessary to pick ids of your own. Consider the example:
~~~
-In this example, we define a GTFS bundle which points to a GTFS file through the `path` property. This GTFS is from
+In this example, we define a GTFS bundle which points to a GTFS file through the **`path`** property. This GTFS is from
King County Metro and includes data for King County Metro, Sound Transit, and City of Seattle. For http://onebusaway.org
we use the convention of mapping agencies to their APTA assigned id. In this case, that's "1" for King County Metro,
"23" for City of Seattle, and "40" for Sound Transit. We map the agency ids in a two ways. First, we specify a default
@@ -150,7 +150,7 @@ two GTFS entities are actually the same. This is most often used for stops in p
~~~
-Here we configure an `EntityReplacementStrategyFactory` with a specific mapping for GTFS stops. The mapping refers
+Here we configure an **`EntityReplacementStrategyFactory`** with a specific mapping for GTFS stops. The mapping refers
to a mapping file path. The mapping file has the following format:
~~~
@@ -166,15 +166,15 @@ ids indicate stops to merge into the first stop.
The bundle builder accepts a number of command-line options that can control the build process, allowing you to control
which phases of the build are run.
-* `-skip phase_name` - skips the specified build phase. Can be repeated.
-* `-only phase_name` - only runs the specified build phase. Can be repeated.
-* `-skipTo phase_name` - jump ahead to the specified build phase. Only specify once.
-* `-include phase_name` - include the specified build phase, useful when the phase is not enabled by default. Can be repeated.
+* **`-skip phase_name`** - skips the specified build phase. Can be repeated.
+* **`-only phase_name`** - only runs the specified build phase. Can be repeated.
+* **`-skipTo phase_name`** - jump ahead to the specified build phase. Only specify once.
+* **`-include phase_name`**- include the specified build phase, useful when the phase is not enabled by default. Can be repeated.
### Adding a Custom Build Phase
You can add your own custom build phases into the build process. To do so, you specify a task definition in your
-`bundle.xml` config:
+**`bundle.xml`** config:
~~~
@@ -194,7 +194,7 @@ You can add your own custom build phases into the build process. To do so, you
~~~
As you can see, the TaskDefinition bean allows you to define custom tasks and optionally control where they appear
-in the build order. The only requirement is that your task instance implement `Runnable`.
+in the build order. The only requirement is that your task instance implement **`Runnable`**.
-In addition to adding your task definition to your `bundle.xml`, you'll also need to add the jar or class files with
+In addition to adding your task definition to your **`bundle.xml`**, you'll also need to add the jar or class files with
your task implementation to the classpath when you run the build process.
diff --git a/src/guides/troubleshooting-guide.md b/src/guides/troubleshooting-guide.md
index b0f9905..e964f10 100644
--- a/src/guides/troubleshooting-guide.md
+++ b/src/guides/troubleshooting-guide.md
@@ -42,7 +42,7 @@ Next, check the main map view:
[http://localhost:8080/where/standard/](http://localhost:8080/where/standard/)
This should bring up a browseable map. If you get an error about your Google Maps API key, you need to specify your
-own API key. Check out the `defaultWebappConfigurationSource.googleMapsApiKey` parameter in the
+own API key. Check out the **`defaultWebappConfigurationSource.googleMapsApiKey`** parameter in the
parameter config documentation.
You should be able to search for routes by name and zoom in to find transit stops on the map. If you can't find any
@@ -96,7 +96,7 @@ If you don't see any entries, it probably means your transit data bundle wasn't
Next, for a specific agency, you can query the set of routes ([method documentation](/api/where/methods/routes-for-agency))
and stops ([method documentation](../api/where/methods/stop-ids-for-agency)) for the agency.
-For routes, use the following URL, replace `AGENCYID` with the agency id from the [ element](/api/where/elements/agency)
+For routes, use the following URL, replace **`AGENCYID`** with the agency id from the [ element](/api/where/elements/agency)
in the agencies response.
[http://localhost:8080/api/where/routes-for-agency/AGENCYID.xml?key=TEST](http://localhost:8080/api/where/routes-for-agency/AGENCYID.xml?key=TEST)
@@ -124,7 +124,7 @@ You should see a number of [ elements](/api/where/elements/route) for th
If you don't see any elements, it could indicate a problem with your transit data bundle.
-For stops, use the following URL, again updating `AGENCYID` appropriately:
+For stops, use the following URL, again updating **`AGENCYID`** appropriately:
[http://localhost:8080/api/where/stop-ids-for-agency/AGENCYID.xml?key=TEST](http://localhost:8080/api/where/stop-ids-for-agency/AGENCYID.xml?key=TEST)
diff --git a/src/guides/webapp-configuration-guide.md b/src/guides/webapp-configuration-guide.md
index 914fb3d..19db42f 100644
--- a/src/guides/webapp-configuration-guide.md
+++ b/src/guides/webapp-configuration-guide.md
@@ -3,8 +3,8 @@ title: Webapp Configuration Guide
layout: page
---
-This guide will instruct you on how to configure an instance of `onebusaway-webapp`. These are specific configuration
-instructions, part of your larger OneBusAway installation. The `onebusaway-webapp` powers
+This guide will instruct you on how to configure an instance of **`onebusaway-webapp`**. These are specific configuration
+instructions, part of your larger OneBusAway installation. The **`onebusaway-webapp`** powers
the various OneBusAway web interfaces:
* standard web interface
@@ -14,14 +14,14 @@ the various OneBusAway web interfaces:
## Wiki Integration
-To make it easier to customize the content and look-and-feel of your `onebusaway-webapp` installation, we provide a
-content configuration option that we call *wiki integration*. The idea is that you can point your `onebusaway-webapp`
+To make it easier to customize the content and look-and-feel of your **`onebusaway-webapp`** installation, we provide a
+content configuration option that we call *wiki integration*. The idea is that you can point your **`onebusaway-webapp`**
installation at a wiki or some other content management system, allowing you to control the various content pages that
are included in the webapp.
As a quick example, if you have an [XWiki installation](http://www.xwiki.org) available at the url
-http://wiki.mydomain.org, you can configure your `onebusaway-webapp` to use the wiki by adding the following elements
-to your `data-sources.xml` config file:
+http://wiki.mydomain.org, you can configure your **`onebusaway-webapp`** to use the wiki by adding the following elements
+to your **`data-sources.xml`** config file:
~~~
diff --git a/src/release-notes.md b/src/release-notes.md
index 676ba5f..0749c1a 100644
--- a/src/release-notes.md
+++ b/src/release-notes.md
@@ -128,7 +128,7 @@ title: Release Notes
* Add @ConfigurationParameter annotation for marking
important OneBusAway bean configuration parameters. Also add support for automatically generating
documentation for these parameters.
- * Make the Google Maps API key a configurable parameter: `defaultWebappConfigurationSource.googleMapsApiKey`
+ * Make the Google Maps API key a configurable parameter: **`defaultWebappConfigurationSource.googleMapsApiKey`**
* Allow such bean properties to be overriden from the command-line for the webapp quickstart with the same
-PbeanName.propertyName=value syntax used in the bundle builder command-line app.
* Add more content to the trip problem report page to make it easier to diagnose problems.
@@ -139,7 +139,7 @@ title: Release Notes
trip that is no longer loaded in the transit bundle.
* Upgrade to struts 2.2.3.1, which hides those annoying GWT class exceptions on webapp startup.
* ConfigurationService config cache was not properly reset on application startup.
- * In the VehicleLocationRecords API Action, the `vehicleId`, `fromTime`, and `toTime` parameters were not being
+ * In the VehicleLocationRecords API Action, the **`vehicleId`**, **`fromTime`**, and **`toTime`** parameters were not being
properly set for the action.
[commit](https://github.com/OneBusAway/onebusaway-application-modules/commit/826b4bba2a67ec28f682b6431bd5965cd34fbe10)
* Make sure vehicleId is properly set when creating a TripProblemReportBean from a DB record.
@@ -170,8 +170,8 @@ title: Release Notes
## 1.0.2
-* Make `onebusaway-quickstart` part of the main `onebusaway-application-modules` module set.
-* Add a ui-only webapp artifact to `onebusaway-combined-webapp`.
+* Make **`onebusaway-quickstart`** part of the main **`onebusaway-application-modules`** module set.
+* Add a ui-only webapp artifact to **`onebusaway-combined-webapp`**.
* Tweak support for GTFS-realtime, including support for new OBA-specific delay field.
* Initial support for fixed-schedule trips with a headway-in-name-only frequency label, as indicated by frequencies.txt
label_only feature proposal.