This dataset contains information on the Pittsburgh Parking Authority's parking meters and other payments points, including a description of the location of the meter, which parking zone it is in, and its geocoordinates. The "Payment Points + Rates" table is augmented with information about rates and the limits on when parking is metered.

This dataset contains transaction-level records of purchases of parking from the Pittsburgh Parking Authority. Individual transactions are published with information including the zone or meter where the purchase was made, start time of the interval paid for, end time of the interval paid for, purchase time (for meter transactions), date recorded in the database (a good proxy for purchase time for mobile transactions), amount paid in that transaction, whether the transaction was made through a smart phone (a "mobile" transaction) or at a meter (in which case the means of payment will be identified as cash, credit card, or a combination of the two), and whether a given purchase started a new parking session or extended an existing session. The payment-interval start times are the same for all transactions in a given session: If someone pays to park at 9am and then 15 minutes later adds more money to extend their parking session, there will be two rows in the table (one for the 9am purchase and one for the 9:15am purchase), but both rows will have the same payment-interval start time (9am) since the payment interval is at the parking-session level. This dataset is considered "beta" at this point. The formatting of values and the set of fields may change as this dataset approaches its final state.

This dataset includes all parking expiations issued by the Adelaide City Council, and includes data such as payments, current status and exemptions for all parking expiations issued during the last three years. The dataset is refreshed on the 6th day of every month and includes data up to the end of the previous month. The data is re-written each month as statuses etc. do change for expiations issued during the period. The data is valid as of the date the extract is run. FAQs Why is the amount paid greater than the Expiation Amount? The expiation amount is the amount of the original Expiation Fee on the date the Expiation Fee is issued. After this time additional fees such as Reminder Fees, Search Fees and some others can be incurred which are added to the Expiation. All Expiation Fees, Reminder Fees, Search Fees etc. are set by the State Government. What is FERU? FERU is the Fines Enforcement and Recovery Unit, who are responsible for the recovery and enforcement of unpaid Expiations. If an Expiation Remains unpaid Council will refer the matter to FERU to recover the debt. Expiations can also be referred to FERU when a payment plan is entered into. When an Expiation has been referred to FERU the Offence Balance in the data is $0. Why is the Offence Balance a negative figure? On some occasions Adelaide City Council receives payments (either one or multiple payments) in excess of the amount payable for an Expiation. Council has a procedure in place to identify these payments and try to return the money.

전라남도 순천시 도시재생 구역 내에 있는 주차장 장소값 기준으로 주차 운영 정보 데이터를 개방 합니다 (주차장명, 주차정보, 결재정보,휴무일 등)

These datasets contain the total number of Mobility Parking Scheme transactions and statuses. The data includes: The count (number) of Mobility Parking Scheme transactions per month for a given year. The count of active Mobility Parking Permits at the end of each month for a given year. Data will be updated to include the backdated transactions in the previous 2 months. Interactive analytics from 1 July 2022 is available on Registration and Licensing Statistics Portal https://www.transport.nsw.gov.au/registration-and-licensing-statistics-p... Information prior to 1 July 2022 is available on Webstats https://roads-waterways.transport.nsw.gov.au/cgi-bin/index.cgi?action=st... Disclaimer: Transport for NSW (TfNSW) publishes statistical licensing and registration data to disseminate information and provide transparency for the benefit of the public. TfNSW has taken care to ensure that data published is correct and accurate as possible. The data has been consistently produced and is updated regularly. However, TfNSW does not warrant, represent or guarantee the accuracy, reliability, quality or suitability for any purpose of the information or data published at this website nor accept any responsibility arising in connection with any errors in, or omissions from, the information or data provided. TfNSW does not accept any legal liability for any loss or damage arising directly or indirectly from the use of information or data published at this website. TfNSW recommends that users exercise their own skill, care and judgement with respect to their use of information or data published including by evaluating the relevance of the material on this website for their purpose.

This dataset includes a table with space counts, number of meters, rates, and parking types for each zone, as sampled on particular dates. A second table includes lease counts by lot, also with the dates that the counts were made.

Parking Meters