City Data Model Project Collaboratory - User contributions [en-ca]

UseCase:Regional Parking Usage Report

2023-07-19T14:39:35Z

KenVaughn:

{{Use Case
|Domain=Smart Transportation
|Summary=Create a report on curbside use allocations and statistics on actual use.
|Description=To better manage its curbside space, an agency needs to be able to generate a report showing how much curbside space is used for various purposes and how often the space is actually in use.
|Actors=Transportation planner, Traffic Management System, curbside monitoring components
|Basic Flow of Events=1. The traffic management system allocates curbside space for different purposes (this may be dynamic)

2. Users reserve curbside space

3. The traffic management system records when spaces are in use

4. Transportation planner requests historic reports
|Information Requirements=location of curbs and spaces
usage of each curb space (and the percent of time assigned for that use)
percent of the time in use for the designated purpose
|References=ARC-IT PM04 Regional Parking Management
|Scenario License=Cc-by-4.0
|Use Case Status=Pending Approval
}}
{{Supplementary Figures}}

UseCase:Regional Parking Usage Report

2023-07-19T14:38:08Z

KenVaughn: Refine flow of events

{{Use Case
|Domain=Smart Transportation
|Summary=Create a report on curbside use allocations and statistics on actual use.
|Description=To better manage its curbside space, an agency needs to be able to generate a report showing how much curbside space is used for various purposes and how often the space is actually in use.
|Actors=Transportation planner, Traffic Management System, curbside monitoring components
|Basic Flow of Events=1. The traffic management system allocates curbside space for different purposes (this may be dynamic)

2. Users reserve curbside space

3. The traffic management system records when spaces are in use

4. Transportation planner requests historic reports
|Information Requirements=location of curbs
usage of each curb (and the percent of time assigned for that use)
percent of the time in use for the designated purpose
|References=ARC-IT PM04 Regional Parking Management
|Scenario License=Cc-by-4.0
|Use Case Status=Pending Approval
}}
{{Supplementary Figures}}

Specification:Curb Data Specification

2023-07-19T14:34:35Z

KenVaughn: Added CDS specification

{{Specification
|Specification Number=CDS 1.0.0
|Reference=https://github.com/openmobilityfoundation/curb-data-specification/blob/main/README.md
|Description=The Curb Data Specification (CDS), a project of the Open Mobility Foundation (OMF), is a data standard and set of Application Programming Interfaces (APIs) that helps cities manage and companies use dynamic curb zones that optimize loading activities of people and goods and measure the impact of these programs.

NOTE: The CDS defines rates in US cents and does not have an unambiguous way to internationalize.
|Specification License=Cc-by-4.0
|Licensing Comments=Licensing defined by standard
}}

File:GeoJSON Polygon.png

2023-07-19T14:27:56Z

KenVaughn:

File:Curb Policy.png

2023-07-19T14:27:35Z

KenVaughn:

File:Curb Zone.png

2023-07-19T14:26:47Z

KenVaughn:

UseCase:Regional Parking Usage Report

2023-07-19T02:28:45Z

KenVaughn:

{{Use Case
|Domain=Smart Transportation
|Summary=Create a report on curbside use allocations and statistics on actual use.
|Description=To better manage its curbside space, an agency needs to be able to generate a report showing how much curbside space is used for various purposes and how often the space is actually in use.
|Actors=Transportation planner, Traffic Management System, curbside monitoring components
|Basic Flow of Events=The traffic management system allocates curbside space for different purposes (this may be dynamic)
Users reserve curbside space
The traffic management system records when spaces are in use
Transportation planner requests historic reports
|Information Requirements=location of curbs
usage of each curb (and the percent of time assigned for that use)
percent of the time in use for the designated purpose
|References=ARC-IT PM04 Regional Parking Management
|Scenario License=Cc-by-4.0
|Use Case Status=Pending Approval
}}
{{Supplementary Figures}}

UseCase:Regional Parking Usage Report

2023-07-18T23:46:13Z

KenVaughn: Created page with "{{Use Case |Domain=Smart Transportation |Summary=Create a report on curbside use allocations and statistics on actual use. |Description=To better manage its curbside space, an..."

{{Use Case
|Domain=Smart Transportation
|Summary=Create a report on curbside use allocations and statistics on actual use.
|Description=To better manage its curbside space, an agency needs to be able to generate a report showing how much curbside space is used for various purposes and how often the space is actually in use.
|Actors=Transportation planner, Traffic Management System, curbside monitoring components
|Basic Flow of Events=The traffic management system allocates curbside space for different purposes (this may be dynamic)
Users reserve curbside space
The traffic management system records when spaces are in use
Transportation planner requests historic reports
|Scenario License=Cc-by-4.0
|Use Case Status=Pending Approval
}}
{{Supplementary Figures}}

Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model

2022-08-24T13:44:26Z

KenVaughn:

{{Specification
|Specification Number=ISO 5206-1
|Reference=https://www.iso.org/standard/80997.html
https://github.com/parkingdata/spec
|Description=ISO 5206-1 defines a physical data model for parking and parking-related activities (both on-street and off-street) covering common data supporting business-to-business exchanges and end-user services.
|Specification License=License TBD
|Licensing Comments=ISO copyright
}}

Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model

2022-08-24T13:43:52Z

KenVaughn:

{{Specification
|Specification Number=ISO 5206-1
|Reference=https://www.iso.org/standard/80997.html
|Description=ISO 5206-1 defines a physical data model for parking and parking-related activities (both on-street and off-street) covering common data supporting business-to-business exchanges and end-user services.
|Specification License=License TBD
|Licensing Comments=ISO copyright
}}

Finding, Reserving, and Paying for Parking

2022-08-22T21:52:30Z

KenVaughn:

{{Use Case
|Domain=Smart Transportation
|Summary=A traveller needs to find, reserve and pay for parking with fees applied to the traveller's account.
|Description=A traveller is using a rental vehicle to reach a meeting at a remote site. Prior to starting the trip, the traveller wishes to find, reserve and pay for parking to maximize the efficiency of the journey. The traveller wishes to pay for parking as a part of the car hire charge. The meeting that the traveller attends goes longer than expected and the vehicle is parked for longer than the original reservation was made for.
|Actors=Traveller, Parking Facility
|Basic Flow of Events=1. Traveller enters their destination into the interface device with details about the parking needs.

2. System provides a list of parking places near the destination.

3. The traveller requests details for a selected parking place.

4. The system provides details for the selected parking place.

5. The traveller requests a reservation.

6. The system requests payment details.

7. The traveller provides payment information.

8. The system confirms payment and provides proof of reservation.
|Flow Exceptions=1. A traveller may request details for multiple parking places but will typically select only one.

2. A traveller may escape from the flow of events at any time.

3. The system may reject the payment and not reserve the space.
|Information Requirements=Destination location, parking place location, estimated arrival time at parking place, estimated departure time from parking place, parking place operating hours, existing relationships between the traveller and any parking service providers, rates for each parking place, space availability, services offered by the parking place, payment methods offered.
|Required Classes=Agent
|References=Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020)
|Specifications=Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model
|Scenario License=License TBD
|Licensing Comments=Use case presented here is generalized but consistent with the APDS use case
|Use Case Status=Pending Approval
}}
{{Supplementary Figures
|Figure Row={{Figure Row
|Figure=Class Diagram for Find Parking Places Within a Radius.png
|Caption=Class Diagram for Find Parking Places Within a Radius
}}
}}

Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model

2022-08-22T21:37:33Z

KenVaughn: Add ISO 5206-1 to list of standards

{{Specification
|Specification Number=ISO 5206-1
|Reference=ISO 5206-1
|Description=ISO 5206-1 defines a physical data model for parking and parking-related activities (both on-street and off-street) covering common data supporting business-to-business exchanges and end-user services.
|Specification License=License TBD
|Licensing Comments=ISO copyright
}}

Finding, Reserving, and Paying for Parking

2022-08-22T21:22:31Z

KenVaughn:

{{Use Case
|Domain=Smart Transportation
|Summary=A traveller needs to find, reserve and pay for parking with fees applied to the traveller's account.
|Description=A traveller is using a rental vehicle to reach a meeting at a remote site. Prior to starting the trip, the traveller wishes to find, reserve and pay for parking to maximize the efficiency of the journey. The traveller wishes to pay for parking as a part of the car hire charge. The meeting that the traveller attends goes longer than expected and the vehicle is parked for longer than the original reservation was made for.
|Actors=Traveller, Parking Facility
|Basic Flow of Events=1. Traveller enters their destination into the interface device with details about the parking needs.

2. System provides a list of parking places near the destination.

3. The traveller requests details for a selected parking place.

4. The system provides details for the selected parking place.

5. The traveller requests a reservation.

6. The system requests payment details.

7. The traveller provides payment information.

8. The system confirms payment and provides proof of reservation.
|Flow Exceptions=1. A traveller may request details for multiple parking places but will typically select only one.

2. A traveller may escape from the flow of events at any time.

3. The system may reject the payment and not reserve the space.
|Information Requirements=Destination location, parking place location, estimated arrival time at parking place, estimated departure time from parking place, parking place operating hours, existing relationships between the traveller and any parking service providers, rates for each parking place, space availability, services offered by the parking place, payment methods offered.
|Required Classes=Agent
|References=Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020)
|Specifications=NewTestSpecifification1
|Scenario License=License TBD
|Licensing Comments=Use case presented here is generalized but consistent with the APDS use case
|Use Case Status=Pending Approval
}}
{{Supplementary Figures
|Figure Row={{Figure Row
|Figure=Class Diagram for Find Parking Places Within a Radius.png
|Caption=Class Diagram for Find Parking Places Within a Radius
}}
}}

Parking::PlaceHierarchy::Place

2021-07-05T17:11:15Z

KenVaughn:

{{Class Definition
|Subclass Of=Parking::PlaceHierarchy::HierarchyElementGeneral
|Description=place or location that may be used for parking or other purposes
|Sources=APDS: Parking Data Standard: Data Dictionary: Release 2.1 (April 2020)
|Definition Status=Pending Approval
}}
{{Annotation Specification
|Annotation Row={{Annotation Row
|Annotation=rdfs:comment
|Value=place or location that may be used for parking or other purposes
}}{{Annotation Row
|Annotation=rdfs:isDefinedBy
|Value=APDS Parking Data Standard
}}
}}
{{Manchester Specification
|Manchester Row={{Manchester Row
|Property=refs:subClassOf
|Value=Parking::PlaceHierarchy::HierarchyElementGeneral
}}{{Manchester Row
|Property=hasTimeZone
|Restriction=exactly 1
|Value=string
}}
}}
{{Supplementary Figures}}

Parking::PlaceHierarchy::HierarchyElementGeneral

2021-07-05T17:09:54Z

KenVaughn:

{{Class Definition
|Description=generalised component of a place hierarchy, that forms one element in the tree-like hierarchy
|Sources=APDS: Parking Data Standard: Data Dictionary: Release 2.1 (April 2020)
ISO 5206-1
|Definition Status=Pending Approval
}}
{{Annotation Specification
|Annotation Row={{Annotation Row
|Annotation=rdfs:comment
|Value=generalised component of a place hierarchy, that forms one element in the tree-like hierarchy
}}
}}
{{Manchester Specification
|Manchester Row={{Manchester Row
|Property=hasAlias
|Restriction=only
|Value=MultilingualString
}}{{Manchester Row
|Property=hasDescription
|Restriction=max 1
|Value=MultilingualString
}}{{Manchester Row
|Property=HasName
|Restriction=exactly 1
|Value=MultilingualString
}}{{Manchester Row
|Property=hasType
|Restriction=exactly 1
|Value=HierarchyElementTypeEnum
}}
}}
{{Supplementary Figures}}

Parking::PlaceHierarchy::Place

2021-07-05T17:00:35Z

KenVaughn: Created page with "{{Class Definition |Subclass Of=Parking::PlaceHierarchy::HierarchyElementGeneral |Description=place or location that may be used for parking or other purposes |Required by Use..."

{{Class Definition
|Subclass Of=Parking::PlaceHierarchy::HierarchyElementGeneral
|Description=place or location that may be used for parking or other purposes
|Required by Use Cases=Finding, Reserving, and Paying for Parking
|Sources=APDS: Parking Data Standard: Data Dictionary: Release 2.1 (April 2020)
|Definition Status=Pending Approval
}}
{{Annotation Specification
|Annotation Row={{Annotation Row
|Annotation=rdfs:comment
|Value=place or location that may be used for parking or other purposes
}}{{Annotation Row
|Annotation=rdfs:isDefinedBy
|Value=APDS Parking Data Standard
}}
}}
{{Manchester Specification
|Manchester Row={{Manchester Row
|Property=refs:subClassOf
|Value=Parking::PlaceHierarchy::HierarchyElementGeneral
}}{{Manchester Row
|Property=hasTimeZone
|Restriction=exactly 1
|Value=string
}}
}}
{{Supplementary Figures}}

Parking::PlaceHierarchy::HierarchyElementGeneral

2021-07-05T16:47:18Z

KenVaughn: Created page with "{{Class Definition |Description=generalised component of a place hierarchy, that forms one element in the tree-like hierarchy |Required by Use Cases=Finding, Reserving, and Pa..."

{{Class Definition
|Description=generalised component of a place hierarchy, that forms one element in the tree-like hierarchy
|Required by Use Cases=Finding, Reserving, and Paying for Parking
|Sources=APDS: Parking Data Standard: Data Dictionary: Release 2.1 (April 2020)
ISO 5206-1
|Definition Status=Pending Approval
}}
{{Annotation Specification
|Annotation Row={{Annotation Row
|Annotation=rdfs:comment
|Value=generalised component of a place hierarchy, that forms one element in the tree-like hierarchy
}}
}}
{{Manchester Specification}}
{{Supplementary Figures}}

Finding, Reserving, and Paying for Parking

2021-07-05T16:00:02Z

KenVaughn: Created page with "{{Use Case |Domain=Smart Transportation |Summary=A traveller needs to find, reserve and pay for parking with fees applied to the traveller's account. |Description=A traveller..."

{{Use Case
|Domain=Smart Transportation
|Summary=A traveller needs to find, reserve and pay for parking with fees applied to the traveller's account.
|Description=A traveller is using a rental vehicle to reach a meeting at a remote site. Prior to starting the trip, the traveller wishes to find, reserve and pay for parking to maximize the efficiency of the journey. The traveller wishes to pay for parking as a part of the car hire charge. The meeting that the traveller attends goes longer than expected and the vehicle is parked for longer than the original reservation was made for.
|Actors=Traveller, Parking Facility
|Basic Flow of Events=Traveller enters destination into interface device with details about the parking needs
System provides list of parking places near destination
Traveller requests details for a parking place
System provides details for a parking place
Traveller requests a reservation
System requests payment details
Traveller provides payment information
System confirms payment and provides proof of reservation
|Flow Exceptions=A traveller may request details for multiple parking places but will typically select only one.
A traveller may escape from the flow of events at any time.
The system may reject the payment and not reserve the space.
|Information Requirements=Destination location, parking place location, estimated arrival time at parking place, estimated departure time from parking place, parking place operating hours, existing relationships between the traveller and any parking service providers, rates for each parking place, space availability, services offered by the parking place, payment methods offered.
|Required Classes=ProduceState
|References=Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020)
|Specifications=NewTestSpecifification1
|Scenario License=License TBD
|Licensing Comments=Use case presented here is generalized but consistent with the APDS use case
|Use Case Status=Pending Approval
}}
{{Supplementary Figures
|Figure Row={{Figure Row
|Figure=Class Diagram for Find Parking Places Within a Radius.png,
|Caption=Class Diagram for Find Parking Places Within a Radius
}}
}}

File:Class Diagram for Find Parking Places Within a Radius.png

2021-07-05T15:59:07Z

KenVaughn: Class Diagram from APDS Parking Data Specification: Use Case Document

== Summary ==
Class Diagram from APDS Parking Data Specification: Use Case Document
== Licensing ==
{{subst:Non-commercial from license selector}}