parks data model review meeting yorkinfo partnership

31
1 Parks Data Model Review Meeting YorkInfo Partnership

Upload: dewei

Post on 23-Feb-2016

34 views

Category:

Documents


0 download

DESCRIPTION

Parks Data Model Review Meeting YorkInfo Partnership. Parks Data Model Review Meeting YorkInfo Partnership. Steve Grisé Solution Architect, Vertex3 October 11, 2013. Agenda. Introductions and background – Deb Data Model Presentation – Steve Discussion - All - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Parks Data Model  Review Meeting YorkInfo  Partnership

1

Parks Data Model Review MeetingYorkInfo Partnership

Page 2: Parks Data Model  Review Meeting YorkInfo  Partnership

2

Parks Data Model Review MeetingYorkInfo Partnership

Steve GriséSolution Architect, Vertex3October 11, 2013

Page 3: Parks Data Model  Review Meeting YorkInfo  Partnership

3

Agenda

Introductions and background – DebData Model Presentation – SteveDiscussion - AllNext Steps and Meeting Close - Deb

Page 4: Parks Data Model  Review Meeting YorkInfo  Partnership

4

Data Model PurposeBuild Region-wide Parks Datasets

Consistent and reliable data about ParksSupport multiple needs

MappingPublic SafetyAddressing

Must be Manageable and PracticalShare the data appropriately

A template for this type of projectYorkInfo Partnership collaboration

Page 5: Parks Data Model  Review Meeting YorkInfo  Partnership

5

Data Model Context

Addressing

Public Facilities

Recreation

Public Safety

Parks Data

Emergency Response

Page 6: Parks Data Model  Review Meeting YorkInfo  Partnership

6

Information Products

Information Products Information Needs

 Data Sharing Model

MapsBasemapsOperational LayersReportsRequiredAdvanced/NovelToolsApplicationsFunctions

ServicesLayersFields

TablesFeature ClassesFieldsRules

Page 7: Parks Data Model  Review Meeting YorkInfo  Partnership

7

Basemaps

Parks are part of every basemap (Green areas)

Typically park boundariesCan include trails and other park featuresLittle or no attributes except for map display needs (Provincial Park, Local Park, etc.)

Page 8: Parks Data Model  Review Meeting YorkInfo  Partnership

8

Open StreetMap

Page 9: Parks Data Model  Review Meeting YorkInfo  Partnership

9

Esri Topographic

Page 10: Parks Data Model  Review Meeting YorkInfo  Partnership

10

Google Maps

Page 11: Parks Data Model  Review Meeting YorkInfo  Partnership

11

Bing Maps

Page 12: Parks Data Model  Review Meeting YorkInfo  Partnership

12

Information NeedsMapping

Polygons & Points for Parks and other AttractionsTrailsImagery

Public SafetyMapping needs as aboveAddressing and location finding within ParksPlanning and utilization of Parks for Response, Sheltering, Base of Operations, etc.Enforcement

Page 13: Parks Data Model  Review Meeting YorkInfo  Partnership

13

Information NeedsAddressing

Address Points and Entrance pointsRoads and Addresses important but optional (really part of another data sharing project)

Park Management – Assets and OperationsAssets and other details not part of current scopeMust ensure that this work does not conflict with current/future expansion into this detailed view

Page 14: Parks Data Model  Review Meeting YorkInfo  Partnership

14

Proposed Data Content for Parks

Page 15: Parks Data Model  Review Meeting YorkInfo  Partnership

15

Proposed Data Content for Parks

Page 16: Parks Data Model  Review Meeting YorkInfo  Partnership

16

York Maps

Page 17: Parks Data Model  Review Meeting YorkInfo  Partnership

17

ParksPark Polygons that represent the boundary or management area

for significant Parks and Public AttractionsFacility IdentifierName of FacilityPark TypeDescriptionCreate DateCreated ByMod DateMod By

Facility IdentifierName of FacilityList of Park TypesDescriptionCreate DateCreated ByModification DateModified By

ParkPoint Points that represent the boundary or management area for significant Parks and Public Attractions.

Facility IdentifierName of FacilityPark TypeOwned ByOwner TypeManaged ByFull AddressMunicipal NameDescriptionPOC NamePOC PhoneEmergency PhoneCreate DateCreated ByMod DateMod By

Facility IdentifierName of FacilityList of Park TypesOwned ByOwner TypeManaged ByFull AddressMunicipality NameDescriptionPoint of Contact Name/RolePoint of Contact Phone NumberEmergency Contact Phone NumberCreate DateCreated ByModification DateModified By

Page 18: Parks Data Model  Review Meeting YorkInfo  Partnership

18

Addresses

AddressEntrancePoint Points that represent access location for properties and buildings

Entrance IDAddress Point IDEntrance TypeDescriptionCreate DateCreated ByMod DateMod By

Entrance IDAddress Point IDEntrance TypeDescriptionCreate DateCreated ByModification DateModified By

AddressPoint Municipal Address Locations

Address Point IDBuilding IDAddress Point TypeConfidenceStreet Name IDFull Street NameAddress NumberAddress Number SuffixUnit NumberUnit TypeFull AddressMunicipal NameCreate DateCreated ByMod DateMod By

Address Point IDBuilding IDAddress Point TypeConfidenceStreet Name IDFull Street NameAddress NumberAddress Number SuffixUnit NumberUnit TypeFull AddressMunicipality NameCreate DateCreated ByModification DateModified By

Page 19: Parks Data Model  Review Meeting YorkInfo  Partnership

19

Trails and Buildings

Building Building polygons that represent footprints

Building IDBuilding NameBuilding TypeStoriesBuilding ShapeHeightGross Floor AreaYear BuiltDaytime PopulationNight time PopulationCreate DateCreated ByMod DateMod By

Building IDBuilding NameBuilding TypeStoriesBuilding ShapeHeightGross Floor AreaYear BuiltDaytime PopulationNight time PopulationCreate DateCreated ByModification DateModified By

Trail Recreation trails

Trail IDTrail TypeNameCommentsSurfaceTrail SystemStatusClassTrail SegmentConstruct StartActual LengthCars/TrucksATVMotorcyclesHorsebackCyclingHikingPedestrianCreate DateCreated ByMod DateMod By

Trail IdentifierTrail TypeTrail NameCommentsTrail Surface MaterialTrail SystemTrail StatusTrail ClassTrail segment based on forest tractConstruction Start DateActual LengthCars/Trucks permittedAll Terrain Vehicles permittedMotorcycles permittedHorseback permittedCycling permittedHiking permittedPedestrian permittedCreate DateCreated ByModification DateModified By

Page 20: Parks Data Model  Review Meeting YorkInfo  Partnership

20

Discussion and Comments

Page 21: Parks Data Model  Review Meeting YorkInfo  Partnership

21

Comments

Trails Feature Class

Should have the Park ID as part of its attributes

What about trails that connect parks or aren’t in a park. Just have that as null?

Page 22: Parks Data Model  Review Meeting YorkInfo  Partnership

22

CommentsDatesThere are a number of datesDesign DateTender DateBuild DateRegistered DateAcceptance DateFor Asset Management and Operations the most important date is the Acceptance Date (when it becomes the responsibility of the Operations Department) but in some cases the Park may be useable by the Public before this date. We turn on the Park on the web site map as a present (not future) park after it has been accepted.

Each park may have different values for each of these due to different parcels making up the park.

Needs group discussion, status if not dates can be useful

Page 23: Parks Data Model  Review Meeting YorkInfo  Partnership

23

Comments

Parks are based on Parcels. In many cases there are more than 1 parcel per park and more than 1 Park Type per Park.For this reason we used an ID for the Park plus an ID for each parcel.

Is this for record keeping and asset management purposes, or is it important to everyone for Parks? Implies multiple

polygons per park which can be complicated.

Page 24: Parks Data Model  Review Meeting YorkInfo  Partnership

24

Comments

Ownership should include Regional Conservation Authority

Added to list of owner types, and included Lake Simcoe CA and Toronto Region CA in owners/managers. Also need York Region DSB

Page 25: Parks Data Model  Review Meeting YorkInfo  Partnership

25

CommentsNoting what actual facilities are located in each park (playgrounds, tennis courts, washroom, splash pads, soccer fields etc)Have we gone out of scope of the PARKS model by including the recreation facilities? No recreation facility within our town is located in a park, does this mean I would still be including my recreation facilities? What about the individual features within the facility, are we going to indicate that this rec complex has skating, swimming and fitness?The point feature class which had more information about parks were indicated as parks/attractions. I know Steve indicated that the list in the domain may be too big, however I felt the domain was lacking. What about the soccer pitches, baseball diamonds (hardball, softball), basketball courts, tennis courts, volleyball courts, playgrounds, skate parks, picnic/shelter areas, splash pads, washrooms, parking, etc.

Needs group discussion: Convention Centre, Rec Centre, Casino, Golf Course, Arena, Stadiums, Zoo, and others could be removed. 60 types in current Parks dataset…

Page 26: Parks Data Model  Review Meeting YorkInfo  Partnership

26

CommentsBall Diamond, ArenaBufferClubhouseCommunity CentreCommunity GardenCommunity InstituteConstructionCraft GuildFire HallGreenwayHard Serviced BlockLandscape BufferLibraryMuseumOPEN SPACEOpenOpen SpaceOpen Space ChannelOpen Space LandscapeOpen Space, Walking TrailsOtherPARKParkParketteParking, Tennis Court(s)Play EquipmentPlay Equipment, Ball Diamond(s), ParkingPlay Equipment, Ball Diamond(s), Soccer Field(s)Play Equipment, Ball Diamond(s), Soccer Field(s), ParkingPlay Equipment, Ball Diamonds, ParkingPlay Equipment, Parking

Play Equipment, Picnic Tables, Picnic Shelter, Walking Trails, Ball Diamond(s), Soccer Field(s), Parking, BMX ParkPlay Equipment, Picnic Tables, Picnic Shelter, Walking Trails, Soccer Field(s), Basketball Court, Spray PadPlay Equipment, Walking TrailsProposedRecycling DepotSWMSWM_XSchoolSchool Sport FieldServicing BlockServicing BufferStormwater Management PondTrain StationTransit Right of WayUrban Open SpaceValleyValley / Open SpaceWOODLOTWalkwayWashrooms, Play Equipment, Parking, Tennis Court(s), Basketball CourtWashrooms, Play Equipment, Picnic Tables, Picnic Shelter,Washrooms, Play Equipment, Picnic Tables, Picnic Shelter, Ball Diamond(s), Parking, Basketball CourtWashrooms, Play Equipment, Picnic Tables, Picnic Shelter, Ball Diamond(s), Parking, Tennis Court(s)Washrooms, Play Equipment, Picnic Tables, Picnic Shelter, Walking Trails, Ball Diamond(s), Soccer Field(s), Parking, Mountain BikingWashrooms, Soccer Field(s), Parking, Splash PadWoodlotWorks Yard

Page 27: Parks Data Model  Review Meeting YorkInfo  Partnership

27

Next Steps

Page 28: Parks Data Model  Review Meeting YorkInfo  Partnership

28

Process

Draft Model – 30 days (now)Project work – 60-90 days +Final model - ~3-6 months

Draft Model Projects Final

Model

Page 29: Parks Data Model  Review Meeting YorkInfo  Partnership

29

Next Steps

Technical workUpdate materials on partner website

Link to projects/activities in different orgsGet materials to groups working on projects Set up monthly (or so) review meetings

A Guide for Data Collaboration in Draft formLooking for feedback in OctPresentation in Toronto next Wed. (Oct. 16)

Page 30: Parks Data Model  Review Meeting YorkInfo  Partnership

30

Page 31: Parks Data Model  Review Meeting YorkInfo  Partnership

31

Contact:Steve Grisé[email protected] 444 0323