APC Gateway Context Properties
The APC Gateway context properties control the export and import of passenger boarding and alighting data.
| Property | Description |
|---|---|
|
|
If selected, when exporting APC Gateway data to PLAN, the system automatically flags the imported trips that are eligible for Section 15. Section 15 refers to Section 15 of the Urban Mass Transportation Act of 1964 (US), which defines the accounting and reporting requirements for public transit systems. |
|
You may choose not to automate all the functions, for example, automate the validating process but manually cleanse the data. If selected, the system automatically validates the data after it is imported into the system. |
|
|
If selected, the system automatically cleans the data after validating it. |
|
| If selected, the system automatically exports the data after cleaning it. | |
| RidImportCleansePost-Cleanse validationPerform Post-Cleanse validation | If selected, stops data with initial/departing load over X, multiple bus trips, and trips with 0 passenger miles is held after the cleanse. |
| RidImportCleansePost-Cleanse validationMax Initial Load default | Set the maximum initial load default. |
| Set the maximum departing load default. | |
| Minimum passenger distance allowed.(in units specified in the Core/Locale/Formats/Distance/Precision context properties). | |
|
Select the method that the system applies when load balancing: Average, Min, or Max. The property is set to Average by default. |
|
|
Set the maximum percentage of the imbalance allowed. By default, the value is set at 0.1. If you use a value lower than the default (0.1), the quality of the data may be affected. |
|
|
Set the pathname to the xml file, which contains a maximum imbalance percentage allowed by total count threshold. The MaxPercentage parameter for the highest threshold, which is less than the blocks total on/off count is used. If the total count is less than all the thresholds from this file, the value from the Maximum Imbalance Percentage property is used. |
|
| "Recleansing" is a method of reviewing cleansed block data and arbitrarily inserting zero load points as a method to discourage or reduce carry-through or initial load values. If selected and a block (or sub-block) consists of X minimum number of trips, then the cleansed block splits itself in half (at the end of a trip) and assumes that the split point is a zero load point. The two "split blocks" are cleansed again to ensure that they can still be properly cleansed, that is, does not result in zero loads. If the blocks can be cleansed, they become the basis for the new cleansed count information. If not, then the count reverts to the last iteration of successfully cleansed data. This process is repeated until system can not longer split the block, add more zero load points, and successfully cleanse the block. | |
| If selected, the system cleans the data when the Cleanse command is applied. | |
| If selected, through loads are considered when data is cleansed. | |
| If selected, Min or Max methods are applied on whole blocks only; Average on block pieces. | |
| If selected, the system automatically updates the trip ID by block, time, and
pattern. The property is selected by default. Note: This property is used if the
APC system does not contain FX trip IDs. |
|
| RidImportCSVSet TripId From Lat Lon | If selected, the system sets the trip IDs based on latitude and longitude. |
| RidImportCSVSet TripId From Block Line Direction | If selected, the system sets the trip IDs based on the line direction. |
| RidImportCSVSet TripId From Route Block Stop Depart Time | If selected, the system sets the trip IDs based on the route, block stop, and departure time. |
| RidImportCSVObserved vs. Scheduled Stop Time Threshold | Set the variance between a stop's scheduled time and the time (in minutes) from the Farebox data. |
| RidImportCSVEarly Morning Cutover Time | Set the earliest time for a service day. |
| Set the last date that the data was imported. It only pertains to WatchType = 4 (or the AVL import of data). The date is updated as new data is processed. | |
| If the data is automatically validated and this property is set to 0, the system processes all data. After the process is run at least once, the last validation date is saved in the database. If set to 1, the validation date range starts on the date following that date. | |
| RidImportValidateHold BlocksToo small number of boardings for Block | Set the number of boardings that is considered too small. The system holds the block if it contains this or a lower number of boardings. |
| RidImportValidateHold BlocksToo small number of alightings for Block | Set the number of alightings that is considered too small. The system holds the block if it contains this or a lower number of alightings. |
| RidImportValidateHold BlocksToo big number of boardings for Block | Set the number of boardings that is considered too big. The system holds the block if it contains this or a higher number of boardings. |
| RidImportValidateHold BlocksToo big number of alightings for Block | Set the number of boardings that is considered too big. The system holds the block if it contains this or a higher number of boardings. |
|
If selected, the system automatically holds the data of all stops with invalid Stop IDS for the trip. The property is selected by default. |
|
|
If selected, the system automatically holds the data of all stops with invalid Trip IDs. The property is selected by default. |
|
|
|
If selected, the system automatically holds the data of all stops whose Depart Time is less than their Arrive Time; that is, depart time is before the arrive time. |
|
If selected, the system automatically holds the data of all stops whose Actual time is different from their Scheduled Time by more than the maximum number of minutes set in the Max Schedule Time Difference context property. |
|
|
Set the maximum amount of time (in minutes) that the Actual time is different or varies from the Scheduled time. The default is 20 minutes. |
|
|
|
If selected, the system automatically holds the data of all stops whose Depart time does not follow the FX stop sequence. |
|
If selected, the system automatically holds the data of all trips whose first and last stops are not in the count. |
|
| ImportValidateHold Trips Missing More Than N Stops |
If selected, the system automatically holds the data of all trips that are missing more than the maximum number of stops set in the Max Missing Stops context property. |
|
Set the maximum number of missing stops in a trip. The default is 999 stops. The maximum number is 32767. |
|
|
If selected, the system automatically holds the data of all trips that are missing more than the maximum percentage of missing stops set in the Max Percentage Missing Stops context property. |
|
| Set the maximum percentage of missing stops in a trip. The default is
0.99. This value is applied when the Missing More Than N Percent property is selected. |
|
| If selected, the system holds all trips that do not match the holiday service profile. | |
| If selected, the system holds all trips that has a stop with too many boardings. | |
| If selected, the system holds all trips that has a stop with too many alightings. | |
|
Select an action that you want the system to perform should an invalid stop
occur, for example, the APC count is on a stop that does not exist on the route
based on the parameter:
|
|
|
If selected, the system merges the counts from stops where the driver picked up additional passengers within close proximity of a stop that the bus had just left. The property is selected by default. The system uses the distance value set in the Max Repeating Stop Merge Distance property in determining which counts to merge. |
|
|
Set the maximum distance from a bus stop within which a driver picks up more passengers after leaving a stop. If the Merge Repeating Stops property is selected, the system only merges counts that occur within this distance. Repeated stops refer to instances when the bus driver opens the door to pick up more passengers within close proximity of a stop that the bus had just left. |
|
|
If selected, the system fills in the vehicle name with the MDT ID of the MDT associated with the vehicle. |
|
|
If selected, the system deletes held trips data that are older than the number of days set in the Auto Delete Held Trips Older Than N Days context property before validating data. |
|
|
Set the number of days that you want to keep held trips data before they are deleted, for example, 7 days. This value is applied when the Auto Delete Old Held Checks Before Validation context property is selected. |
|
| If selected, Flex events are considered with regular stop events. | |
| Set the xml file, which contains the APC Gateway watch configuration. | |
| ImportCalculate NTD Counts | If selected, the NTD cleanse is run on successfully cleansed block data. |