Here is where got the datasets for parking meter transactions: https://data.sandiego.gov/datasets/parking-meters-transactions/

pole_id meter_type date_trans_start date_meter_expire trans_amt pay_method
J-710 SS 2025-01-01 04:23:35 2025-01-01 04:23:35 25 CASH
8-1408 SS 2025-01-01 05:13:15 2025-01-01 05:13:15 5 CASH
8-904 SS 2025-01-01 06:21:56 2025-01-01 06:21:56 30 CASH
WB-500S SS 2025-01-01 07:58:02 2025-01-01 10:00:03 200 CREDIT CARD
B-1115 SS 2025-01-01 08:00:00 2025-01-01 08:00:00 25 CASH
15-832 SS 2025-01-01 08:01:57 2025-01-01 08:01:57 25 CASH

🔍 Dataset Columns Explained:

  • pole_id – unique identifier for a parking meter.
  • meter_type – type of parking meter (e.g. single space, smart sensor, etc).
  • date_trans_start – timestamp when the transaction started (user paid).
  • date_meter_expire – timestamp when the paid parking time expired.
  • trans_amt – how much money was paid (in cents).
  • pay_method – how they paid (e.g., CASH, CARD, APP).

Here is where got the datasets for parking meter locations: https://data.sandiego.gov/datasets/parking-meters-locations/

zone area sub_area pole config_id config_name date_inventory lat lng sapid
Downtown Core 1000 FIRST AVE 1-1004 49382 Sunday Mode 2021-01-04 00:00:00 32.715904 -117.163929 SS-000031
Downtown Core - Columbia 1000 FIRST AVE 1-1004 9000 2 Hour Max $1.25 HR 8am-6pm Mon-Sat (NFC) 2018-11-11 00:00:00 32.715904 -117.163929 SS-000031
Downtown Core 1000 FIRST AVE 1-1006 49382 Sunday Mode 2021-01-04 00:00:00 32.716037 -117.163930 SS-000031
Downtown Core - Columbia 1000 FIRST AVE 1-1006 9000 2 Hour Max $1.25 HR 8am-6pm Mon-Sat (NFC) 2018-11-11 00:00:00 32.716037 -117.163930 SS-000031
Downtown Core 1000 FIRST AVE 1-1008 49382 Sunday Mode 2021-01-04 00:00:00 32.716169 -117.163931 SS-000031
Downtown Core - Columbia 1000 FIRST AVE 1-1008 9000 2 Hour Max $1.25 HR 8am-6pm Mon-Sat (NFC) 2018-11-11 00:00:00 32.716169 -117.163931 SS-000031

🔍 Dataset Columns Explained:

  • zone – broad region of the city where the parking meter is located (e.g., “Downtown”).
  • area – more specific district or neighborhood within the zone (e.g., “Core” or “Core - Columbia”).
  • sub_area – street or block-level location (e.g., “1000 FIRST AVE”).
  • pole – unique identifier for the individual parking meter or pole; used to link to transaction data.
  • config_id – numeric code representing a specific parking rule or configuration.
  • config_name – descriptive text explaining the parking rules (e.g., time limits, pricing, days/hours active).
  • date_inventory – date the configuration was recorded or applied; useful for historical analysis.
  • lat – latitude coordinate of the meter’s physical location; used for mapping and spatial analysis.
  • lng – longitude coordinate of the meter’s physical location.
  • sapid – system-generated identifier (likely internal) for the meter, used for asset tracking and inventory management.