Title: Martin County Coastal Geodatabase ESRI 2004
1Advancement of an Enterprise Coastal GIS in
Martin County, Florida
Alexandra Carvalho, Ph.D. Kathy Fitzpatrick,
P.E. Rob Hudson, AICP
Palm Beach County
2Martin County FACTS
OCEAN BREEZE PARK
3Coastal Programs
- 22 Miles of Coastline
- 2 Long Term Beach
- Renourishment Projects
-
- Federal Inlet Maintenance
- Program
- 2 Major Inland Waterways
- Many Federal, state and
- Local Waterfront Parks
- Active Artificial Reef Program
Atlantic Ocean
4Project Rationale
5Objectives
- Support the management of the habitat, beach,
waterway, and artificial reef programs - Manage project budgets
- Manage and track permit and grant requirements
- Automate the permit and grant application
submittals
6Objectives
- Support the management of the habitat, beach,
waterway, and artificial reef programs - Manage and analyze monitoring data and scientific
model results - Community outreach to Federal and State agencies,
scientific and engineering communities, public. - Plan Coastal Programs Future
7Coastal Information Management System
8Timeline
9 10General Business Processes
11Scoping Phase
- Needs Assessment Meetings
- Program and Project Management Requirements
- Permit and Grant Management Requirements
- Regulatory Agency Data Submission Requirements
- Data Inventory and Organization by Program Area
- Basemap Spatial Data
- Project Spatial and Non - Spatial Data
- Monitoring Spatial and Non - Spatial Data
- Design and Implementation of Geodatabase
Structure and Schema
12Scoping Phase Geodatabase Structure
- Domains
- Business
- Tables
-
- Feature
- Classes
- Relationships
13Scoping Phase
14Scoping Phase
- Needs Assessment Meetings
- Program and Project Management Requirements
- Permit and Grant Management Requirements
- Regulatory Agency Data Submission Requirements
- Data Inventory and Organization by Program Area
- Basemap Spatial Data
- Project Spatial and Non - Spatial Data
- Monitoring Spatial and Non - Spatial Data
- Design and Implementation of Geodatabase
Structure and Schema - Development of User Interface and Artificial Reef
Program Tools
15Scoping Phase User Interface
16Scoping Phase User Interface Artificial Reefs
17 18Assessment Phase
- Enterprise Geodatabase
- Needs Assessment
- Data Inventory
- Identification of Business Processes for each
Project Phase
19Business Processes Project Planning Phase
20Business Processes Project Execution Phase
21Business Processes Annual Monitoring Phase
22Assessment Phase
- Enterprise Geodatabase
- Needs Assessment
- Data Inventory
- Identification of Business Processes for each
Project Phase - Tool Inventory by Project Area
- Project Planning Tools
- Non - Spatial Data Handling Tools
- Spatial Data Handling and Analysis Tools
- Tool and User Interface Functionality
Requirements by Project Area
23 24Timeline
25Assessment Overview Implementation Framework
- Articulated specific Business Objectives of the
Coastal Program - Manage Martin Countys habitat, beach, inlet, and
artificial reef resources through the effective
implementation of engineering and restoration
projects. - Monitor and analyze the effectiveness of the
Coastal Programs engineering and restoration
projects. - Track permit requirements and automate the
required permit submittals. - Properly distribute, track, and manage the
Coastal Program budget and grant funding. - Collaborate with, and disseminate information to,
federal and state agencies and the public.
26Assessment Overview Implementation Framework
- Functional requirements realized in eight use
cases - Project Management Toolset
- Add new permit or project information.
- Query, view, or edit existing permit or project
information. - Access all Coastal Division contacts.
- Track grant and permit conditions.
- Provide analytical and characterization
functions. - Web Portal
- Data access.
- Data distribution.
- Data upload.
27Assessment Overview Implementation Framework
- EXAMPLE Use Case Realization 1 - Add new permit
or project information. - Use Case Summary
- Users will be able to generate permit and project
boundaries. - Users will be able to generate boundaries by
entering coordinates from permits into a form. - Users will be able to heads up digitize permit
and project boundaries using desktop GIS
functionality. - Users will be able to enter data in order to
store grant and permit information. - Interface Overview
- Users will be able to generate permit and project
boundaries through coordinate entry into a GUI
that computes the geometry of the polygon. - Users will be able to heads up digitize permit
and project boundaries using native GIS
functionality that is customized for ease of use. - Permit and project data entry forms will be
wizard-driven to allow for ease of use. - Details
- Each permit and project boundary will be appended
to a pre-existing feature class located in the
geodatabase. - All data entered through a form will be
associated with a permit or project boundary. - The Coastal GIS will interact with the Electronic
Document Management System (EDMS) (Documentuum)
to access manage documents, correspondence,
contracts, reports and studies, videos, photos,
and drawings. - The Coastal GIS will interact with the Martin
County Engineering Departments Financial System
to access funding sources and the dollar amounts
allocated for each project activity.
28Assessment Overview
29Assessment Overview Implementation Framework
- Non-Functional Business Requirements
- Approximate number of users
- Four concurrent Engineering Department staff
members - Five Contractors through the web portal
- Fifteen External agency staff (FDEP, USACE, FWC)
through the web portal - Undetermined number of citizens
- Disk space estimates
- Data located within ArcSDE
- 500 megabytes of vector spatial data (including
surveys and business tables) - 12 gigabytes of georeferenced imagery (aerial
photography 6 GB, LiDAR, etc.) - Data located on the file system
- 2 gigabytes of digital photos
- 250 megabytes of drawings
- 250 megabytes of documents
- 2 gigabytes of video
- Viewing and editing roles
30Assessment Overview Implementation Framework
- Non-Functional Business Requirements
- Geodatabase design will conform to the Marine
Data Model. - Components of the Marine Data Model that apply
will be used to implement the coastal
geodatabase. - Where the Marine Data Model can not contribute,
relationships will be built to meet the needs of
the County. - Locational data will conform to the Florida
Department of Environmental Protections
Locational Data Standards - Monitoring data will conform to the Florida
Department of Environmental Protections
Monitoring Standards for Beach Erosion Control
Projects - Vector spatial data in State Plane East, HPGN.
- Geodatabase extent includes the entire state of
Florida with a buffer out to the United States
Territorial Sea Boundary (12 nautical miles).
31Marine Data Model Implementation
- Geodatabase Schema Design
- Identify all primary coastal geospatial datasets
- Modify/customize the ESRI Marine Data Model
- Organize and identify feature datasets and
feature classes - Identification of all business tables
- Attribute refinement and creation on both spatial
data and business tables - Specify and determine subtypes and domains
- Create relationships between both spatial and
non-spatial data - Create topological and spatial rules
- Create FGDC compliant metadata
- Load GIS layers and related tables
- Implementation of the geodatabase object model in
ArcSDE. - Populate the coastal geodatabase with Martin
County coastal data. This should include both
vector data and related tables. - Procedures to connect to the Countys financial
database - QA/QC procedures for all ArcSDE coastal layers,
rules, and behaviors. - Coastal Geodatabase Implementation and Design
Summary Report - Narrative descriptions
32(No Transcript)
33(No Transcript)
34(No Transcript)
35Thank You