Mapping and Loading Ridership Data into PLAN

After the boardings (ons) and alightings (offs) contained within the Ridership data have been balanced, the data is stored in the pre-transformation database of Gateway and is ready for final transformation to ensure all data elements are mapped explicitly to the table structures of Trapeze PLAN.

The data must be imported into PLAN Ridership Analysis
Make sure that the following fields are filled in within the PLAN tables:
  • RidCheckId
  • StopNum
  • LineDirId

  • LineAbbr

  • ServiceAbbr
  • PatternId
  • SignId
After the transformation engine successfully transforms the data format to be congruent with the Trapeze PLAN tables, APC Gateway exports the transformed data to Trapeze by loading its staging buffer and pushing the data into the Trapeze database.