Name: General Oil Spill Booming Strategies - Length in Ft
Display Field: GEO_NOTES
Type: Feature Layer
Geometry Type: esriGeometryPolyline
Description: These data have been created to represent General/Suggested Oil Spill Protective Booming Strategies designed to protect areas that are environmentally and economically sensitive to oil and hazardous material spills (Oil Spill Sensitive Areas). These data were originally created and assembled by the NOAA Scientific Support Coordinator for US Coast Guard District Seven in circa 1992-1993 in cooperation with local Area Committees in accordance with regulations set forth by the National Response Plan of the Oil Pollution Act of 1990. They were provided to FWC-FWRI (Florida Fish and Wildlife Conservation Commission - Fish and Wildlife Research Institute, (at that time known as the Florida Marine Research Institute) in the fall of 2003 as paper maps and PDF maps for each of the US Coast Guard's Marine Safety Office (MSO) Areas of Responsibility (Captain of the Port Zones for Miami (at that time consisting of both what are now known as Sector Miami and Sector Key West), Tampa (now Sector Saint Petersburg), Jacksonville, Savannah, Charleston, and San Juan (Puerto Rico/US Virgin Islands)). In 1999-2000, FWC-FWRI began the process of digitizing the boom strategies depicted on these paper and PDF maps into arc (line) shapefiles, beginning with the maps from MSO Tampa, followed by MSO Miami, then MSO Jacksonville. In the Winter & Spring of 2003-2004 FWC-FWRI mapjoined these data to expand and improve upon the database so it could be used as a core business data layer for the Marine Resources Geographic Information System (MRGIS) library. Using various spatial coding functions, such as "calculate length" and "build geometry", additional attribute information has been added to the spatial database to generate length in feet and meters for summary and reporting purposes. An example of where this can be useful is when performing a spatial selection a summary of the total length of boom can be easily generated. These data are maintained as a part of the MRGIS Library and used with automated map production software to create new printed Geographic Response Plan maps for spill contingency planning and response purposes. Through the years of 2008-2009, FWC-FWRI partnered with the US Coast Guard and Florida Department of Environmental Protection - Bureau of Emergency Response to conduct a series of workshops to review and update these detailed Geographic Response Plan (GRP) data and maps for revised Digital Area Contingency Plans. The GRP revision workshop attendees were from or determined by the specific Area Committee of each Sector. The process of data entry and maintenance is ongoing at FWRI as of July 2011. Data will be entered and undergo quality assurance/quality control processes before new maps are re-produced for distribution and inclusion into Digital Area Contingency Plans and other GIS and/or map products. A versioned geodatabase has been created in SQL/SDE to track changes and manage data entry as well as digital QA/QC processes, such as consistency checks. A map service has also been created that is available to all the public and stakeholder community to view the latest version of this geodata. The map service displays data directly from the Enterprise versioned database. http://ocean.floridamarine.org/acpgrp/default.aspx The spatial data is used to produce response maps and in a GIS (The Florida Marine Spill Analysis System and Digital Area Contingency Plans) to provide timely, accurate, and valuable information to oil spill responders. Maps are produced (as PDF) with the sensitive area sites and protective boom strategies depicted on them. The maps are then "hyperlinked" in PDF to the sensitive area detail data sheets that contain the attribute data for the site in a data report form. The report form contains information on key stakeholders for the area, wildlife resources to be protected, nearby staging areas, recommended protection strategies (a verbal description of the booming strategy depicted on the map), the latitude/longitude of the site, and other response related information needed by first responders. The Booming Strategies have been developed by professional oil spill responders who have participated in the Geographic Response Plan Revision Workshops described. Please see process steps for more information about the history of the GRP revision workshops. NOTE: Booming Strategies were not done at the Sector Mobile (USCG District 7) GRP Workshop. These have been compiled from approved booming strategies related to the Deepwater Horizon oil spill response and are NOT YET approved as "Official Area Contingency Plan" booming strategies.
Service Item Id: 951b30f159d9488fa7aad5d65c243966
Copyright Text: Florida Fish and Wildlife Conservation Commission, U.S. Coast Guard
Default Visibility: false
MaxRecordCount: 2000
MaxSelectionCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 1000000.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: -1.369537162952334E7
YMin: -7525621.83366623
XMax: 3538145.4177330136
YMax: 4393983.527202011
Spatial Reference: 102967
(6439)
LatestVCSWkid(0)
Drawing Info:
Renderer:
Simple Renderer:
Symbol: Style: esriSLSSolid
Color: [255, 176, 0, 255]
Width: 2
Label: Oil Spill Boom
Description: N/A
Transparency: 0
Labeling Info:
Feature Draw Order:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: SUBTYPE
Fields:
-
OBJECTID
(
type: esriFieldTypeOID, alias: OBJECTID
)
-
GEO_NOTES
(
type: esriFieldTypeString, alias: GIS Analyst Notes, length: 254
)
-
ID
(
type: esriFieldTypeString, alias: Unique Boom ID, length: 20
)
-
SITE_ID
(
type: esriFieldTypeString, alias: Boom Site ID, length: 20
)
-
METHOD
(
type: esriFieldTypeString, alias: Protection Strategy, length: 100
)
-
TYPE
(
type: esriFieldTypeString, alias: Type of Boom, length: 50
)
-
SIZE
(
type: esriFieldTypeString, alias: Size of Boom, length: 20
)
-
LENGTH_FT
(
type: esriFieldTypeDouble, alias: Length in Feet
)
-
LENGTH_M
(
type: esriFieldTypeDouble, alias: Length in Meters
)
-
LON_FRM_DD
(
type: esriFieldTypeDouble, alias: Starting Longitude Coordinate in Decimal Degrees
)
-
LAT_FRM_DD
(
type: esriFieldTypeDouble, alias: Starting Latitude Coordinate in Decimal Degrees
)
-
LON_TO_DD
(
type: esriFieldTypeDouble, alias: Ending Longitude Coordinate in Decimal Degrees
)
-
LAT_TO_DD
(
type: esriFieldTypeDouble, alias: Ending Latitude Coordinate in Decimal Degrees
)
-
GRP_MAP
(
type: esriFieldTypeString, alias: GRP Map Index Number, length: 30
)
-
SCAT_DIV
(
type: esriFieldTypeString, alias: SCAT Division, length: 100
)
-
COUNTY
(
type: esriFieldTypeString, alias: County, length: 150
)
-
STATE
(
type: esriFieldTypeString, alias: US State or Territory, length: 20
)
-
SECTOR
(
type: esriFieldTypeString, alias: USCG Sector AOR, length: 30
)
-
PRIORITY
(
type: esriFieldTypeString, alias: Priority Status Based on Tier Level, length: 20
)
-
CONDITION
(
type: esriFieldTypeString, alias: Boom Condition, length: 25
)
-
STATUS
(
type: esriFieldTypeString, alias: Boom Status, length: 20
)
-
SUBTYPE
(
type: esriFieldTypeInteger, alias: Subtype
)
-
BOOM_LEN
(
type: esriFieldTypeDouble, alias: Boom Length Rounded by 50ft
)
-
Shape
(
type: esriFieldTypeGeometry, alias: Shape
)
-
REVIEW_DATE
(
type: esriFieldTypeDate, alias: Review Date, length: 8
)
-
REVIEW_LEVEL
(
type: esriFieldTypeString, alias: Review Level, length: 255
, Coded Values:
[1: 1. Desktop]
, [2: 2. Visual]
, [3: 3. Equipment deployment]
, ...2 more...
)
-
ANCHOR
(
type: esriFieldTypeString, alias: Anchor Sets, length: 255
)
-
created_user
(
type: esriFieldTypeString, alias: created_user, length: 255
)
-
created_date
(
type: esriFieldTypeDate, alias: created_date, length: 8
)
-
last_edited_user
(
type: esriFieldTypeString, alias: last_edited_user, length: 255
)
-
last_edited_date
(
type: esriFieldTypeDate, alias: last_edited_date, length: 8
)
-
Shape.STLength()
(
type: esriFieldTypeDouble, alias: Shape.STLength()
)
Types:
ID: 0
Name: New Subtype
Domains:
-
METHOD:
Coded Values:
[NA: N/A]
, [No Information Provided: No Information Provided]
, [Containment: Containment]
, ...15 more...
-
STATE:
Coded Values:
[NA: N/A]
, [Alabama: Alabama]
, [Florida: Florida]
, ...5 more...
-
SECTOR:
Coded Values:
[NA: N/A]
, [Charleston: Charleston]
, [Jacksonville: Jacksonville]
, ...6 more...
-
PRIORITY:
Coded Values:
[NA: N/A]
, [T1: T1]
, [T2: T2]
, ...3 more...
-
CONDITION:
Coded Values:
[NA: N/A]
, [Damaged: Damaged]
, [Good: Good]
, ...2 more...
-
STATUS:
Coded Values:
[NA: N/A]
, [Deployed: Deployed]
, [Prepositioned Dry: Prepositioned Dry]
, ...4 more...
-
REVIEW_LEVEL:
Inherited
Supported Operations:
Query
Query Attachments
Query Analytic
Generate Renderer
Return Updates
Iteminfo
Thumbnail
Metadata