Interface: Reno TMC - Reno Parking Infrastructure
Architecture Flow Definitions
archive requests (Planned) Applicable ITS Standards
A request to a data source for information on available data (i.e., "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one–time response from the recipient.
archive status (Planned) Applicable ITS Standards
Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
parking archive data (Planned) Applicable ITS Standards
Data used to analyze and monitor trends in parking demand, pricing, and operational actions. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
parking information (Planned) Applicable ITS Standards
General parking information and status, including current parking availability.
parking traffic information (Planned) Applicable ITS Standards
Instructions for operation of local parking facilities to support regional traffic management objectives (e.g., which parking lot exits to use). Also, includes inputs from traffic sensors to monitor parking queues and support more effective management of parking entrances and exits.
payment instructions (Existing) Applicable ITS Standards
Information provided to configure and support fixed point payment operations including pricing information.
payment transactions (Existing) Applicable ITS Standards
Detailed list of transactions including violations. Each transaction includes the date/time, vehicle/customer, and transaction amount. Additional information is included to support delayed payment and violation processing.