Parks Data Model Review Meeting YorkInfo Partnership

1. Parks Data Model Review MeetingYorkInfo Partnership

2. Parks Data Model Review MeetingYorkInfo Partnership Steve Grisé Solution Architect, Vertex3 October 11, 2013

3. Agenda • Introductions and background – Deb • Data Model Presentation – Steve • Discussion - All • Next Steps and Meeting Close - Deb

4. Data Model Purpose • Build Region-wide Parks Datasets • Consistent and reliable data about Parks • Support multiple needs • Mapping • Public Safety • Addressing • Must be Manageable and Practical • Share the data appropriately • A template for this type of project • YorkInfo Partnership collaboration

5. Data Model Context Recreation Addressing Parks Data Public Safety Public Facilities Emergency Response

6. InformationNeeds Information Products Information Products Data Sharing Model • Maps • Basemaps • Operational Layers • Reports • Required • Advanced/Novel • Tools • Applications • Functions Tables Feature Classes Fields Rules Services Layers Fields

7. Basemaps • Parks are part of every basemap (Green areas) • Typically park boundaries • Can include trails and other park features • Little or no attributes except for map display needs (Provincial Park, Local Park, etc.)

8. Open StreetMap

9. Esri Topographic

10. Google Maps

11. Bing Maps

12. Information Needs • Mapping • Polygons & Points for Parks and other Attractions • Trails • Imagery • Public Safety • Mapping needs as above • Addressing and location finding within Parks • Planning and utilization of Parks for Response, Sheltering, Base of Operations, etc. • Enforcement

13. Information Needs • Addressing • Address Points and Entrance points • Roads and Addresses important but optional (really part of another data sharing project) • Park Management – Assets and Operations • Assets and other details not part of current scope • Must ensure that this work does not conflict with current/future expansion into this detailed view

14. Proposed Data Content for Parks

15. Proposed Data Content for Parks

16. York Maps

17. Parks

18. Addresses

19. Trails and Buildings

20. Discussion and Comments

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

22. Comments Needs group discussion, status if not dates can be useful

23. Comments 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.

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

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

26. Comments

27. Next Steps

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

29. Next Steps • Technical work • Update materials on partner website • Link to projects/activities in different orgs • Get materials to groups working on projects • Set up monthly (or so) review meetings • A Guide for Data Collaborationin Draft form • Looking for feedback in Oct • Presentation in Toronto next Wed. (Oct. 16)

31. Contact: • Steve Grisé • steve@vertex3.com • 226 444 0323