1 / 25

Identifying the Spatial Location of Land Use Permit & Water License Applications in the NWT

Identifying the Spatial Location of Land Use Permit & Water License Applications in the NWT. Colin Daniel & Philip Bailey ESSA Technologies December 19, 2006. Draft Findings & Recommendations. Project Overview. Objectives: review current processes identify possible changes  tool

cooper
Download Presentation

Identifying the Spatial Location of Land Use Permit & Water License Applications in the NWT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Identifying the Spatial Locationof Land Use Permit & Water License Applications in the NWT Colin Daniel & Philip Bailey ESSA Technologies December 19, 2006 Draft Findings & Recommendations

  2. Project Overview Objectives: • review current processes • identify possible changes  tool • evaluate GNWT Spatial Data Warehouse Approach: • interviews • functional requirements • technical requirements • implementation plan

  3. Project Overview:System Development Stages

  4. Project Overview:Deliverables & Schedule

  5. Today’s Agenda • Functional Requirements (09:15-11:30) • current process • system objectives & users • key functions • inputs & outputs • Technical Requirements(11:30-12:15) • feasibility analysis & recommended solution • Implementation Plan(12:45-13:30) • possible phases • schedule & budget • Next steps(13:30-14:00) • review project workplan and schedule

  6. Today’s Agenda • Functional Requirements (09:15-11:30) • current process • system objectives & users • key functions • inputs & outputs • Technical Requirements(11:30-12:15) • feasibility analysis & recommended solution • Implementation Plan(12:45-13:30) • possible phases • schedule & budget • Next steps(13:30-14:00) • review project workplan and schedule

  7. Current Process:Boards & Applications

  8. Current Process:Spatial Data Requirements • Mackenzie Valley Resource Mgmt. Act: • Latitude/Longitude Rectangle • Maps & sketches • Preliminary plan • NWT Water Regulations: • Latitude/Longitude • Map (watercourses & waste deposits) • Plan • Additional guidelines for each board

  9. Current Process:Key Issues and Opportunities • Variation in spatial data requirements • Spatial extent and site plan • Hard-copy submissions • Existing spatial database • Lack of digital data for reviewers • Variation in GIS capacity • Cumulative effects assessment

  10. Overall System Objective To develop a integratedsystem that will allow for the electronic acquisition, storage and retrieval of location information associated with land use permit and water license applications in the NWT.

  11. Additional System Objectives • Allow for future expansion • Store data centrally • Allow for agency control • Accessible to wide range of users • Capability to define overall extent • Capability to define optional site plan • Allow for GIS data exchange • Allow for historical data entry • Scientific review only – not application fees

  12. System Functions:Overall Concept • All applications accompanied by GIS maps • Internet software tool • Overall extent and site plan • On-screen digitizing or GIS file upload • Tool assigns Confirmation # • Confirmation # submitted with application • Map available for viewing

  13. System Users

  14. Edit Functions

  15. Review Functions

  16. Inputs and Outputs User Inputs: • spatial extent: • point, rectangle, line, polygon OR • single GIS map file with single polygon • site plan: • one GIS map file per development type System Inputs: • GIS base maps (1:50,000 NTS) • possible development types • application data from participating boards Outputs: • Extent: Confirmation # and GIS map • Site Plan: Confirmation # and GIS map(s)

  17. Today’s Agenda • Functional Requirements (09:15-11:30) • current process • system objectives & users • key functions • inputs & outputs • Technical Requirements (11:30-12:15) • feasibility analysis & recommended solution • Implementation Plan(12:45-13:30) • possible phases • schedule & budget • Next steps(13:30-14:00) • review project workplan and schedule

  18. Technical Options Option 1: Internet Mapping Framework • extend existing SDW technology • add IMF editing suite • customize web interface: editing & review Option 2: ESRI ArcGIS Server • new architecture from ESRI • replace portion of current SDW technology • customize web interface

  19. Feasibility Analysis

  20. Feasibility Analysis of Technical Options

  21. Feasibility Analysis of Technical Options

  22. Technical Recommendation  Option 1: IMF is recommended • less custom development required • rapid development possible • less disruptive: can be implemented in smaller pieces • lower cost: both initial and total

  23. Today’s Agenda • Functional Requirements (09:15-11:30) • current process • system objectives & users • key functions • inputs & outputs • Technical Requirements(11:30-12:15) • feasibility analysis & recommended solution • Implementation Plan (12:45-13:30) • possible phases • schedule & budget • Next steps(13:30-14:00) • review project workplan and schedule

  24. Possible Implementation Plan • Extent mapping only • 1a: on-screen digitizing • 1b: GIS shapefile upload • simple map display • Link to application data • application data display • enhanced map display • Site plan mapping - rough it out a high priority • Load historical data – extents; site plans • Database design – extent mapping

  25. Today’s Agenda • Functional Requirements (09:15-11:30) • current process • system objectives & users • key functions • inputs & outputs • Technical Requirements(11:30-12:15) • feasibility analysis & recommended solution • Implementation Plan(12:45-13:30) • possible phases • schedule & budget • Next steps (13:30-14:00) • review project workplan and schedule

More Related