2007 Palm Beach County Essential Fish Habitat Mapping of Seagrass, Mangroves, Oysters, and Spartina in estuarine waters. (NODC Accession 0061752)

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:


What does this data set describe?

Title:
2007 Palm Beach County Essential Fish Habitat Mapping of Seagrass, Mangroves, Oysters, and Spartina in estuarine waters. (NODC Accession 0061752)
Abstract:
2007 Palm Beach County Mapping Project photointerpreted from June 20 & 22, July 21, and August 4 & 8, 2007 1:10,000 scale and July 1, 2007 1:4,800 scale natural color aerial photography of the entire Lake Worth Lagoon system and the ICW throughout Palm Beach County (excluding the ICW north of Jupiter Inlet and the Loxahatchee River). Features are classified according to PBC ERM modified FLUCCS. The 2007 photointerpretation for the project was accomplished on Avineon's ImageStation Stereo Display (ISSD).

Habitat cover type boundaries were photogrammetrically digitized using CadMap/dgn software in conjunction with ISSD, running on Pentium workstations with Windows XP. This software directly captures digital data into MicroStation (Bentley Microsystems, Inc.) for later importation to ARC/INFO.

Photointerpreters utilized previously collected field data along with other available collateral data to assist in their interpretation. Throughout the photointerpretation process, positional accuracy of feature boundaries was maintained according to the photographic signatures apparent on the photography. The minimum mapping unit for classification is 0.25 acres (=0.1 hectares). The horizontal accuracy of the data meets NMAS for 1:24,000 scale maps (+/- 40 feet).

  1. How might this data set be cited?
    Avineon, Inc., and NOAA/NMFS/Southeast Regional Office - PI Jocelyn Karazsia, 20080429, 2007 Palm Beach County Essential Fish Habitat Mapping of Seagrass, Mangroves, Oysters, and Spartina in estuarine waters. (NODC Accession 0061752): Avineon, Inc., Clearwater, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -80.133889
    East_Bounding_Coordinate: -80.030566
    North_Bounding_Coordinate: 26.973914
    South_Bounding_Coordinate: 26.316604
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 20-Jun-2007
    Currentness_Reference: Source photography date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Complete Chain (2450)
      • Label Point (1037)
      • GT-Polygon Composed of Chains (1037)
    2. What coordinate system is used to represent geographic features?
      The map projection used is Transverse Mercator.
      Projection parameters:
      Scale_Factor_at_Central_Meridian: 0.999941
      Longitude_of_Central_Meridian: -81.000000
      Latitude_of_Projection_Origin: 24.333333
      False_Easting: 656166.666667
      False_Northing: 0.000000
      Planar coordinates are encoded using Coordinate Pair
      Abscissae (x-coordinates) are specified to the nearest 0.001112
      Ordinates (y-coordinates) are specified to the nearest 0.001112
      Planar coordinates are specified in survey feet
      The horizontal datum used is D_North_American_1983_HARN.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.
  7. How does the data set describe geographic features?
    sav07.aat
    Unknown (Source: Unknown)
    FID
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: ESRI) Coordinates defining the features.
    FNODE#
    Internal node number for the beginning of an arc (from-node). (Source: ESRI) Whole numbers that are automatically generated.
    TNODE#
    Internal node number for the end of an arc (to-node). (Source: ESRI) Whole numbers that are automatically generated.
    LPOLY#
    Internal node number for the left polygon. (Source: ESRI) Whole numbers that are automatically generated.
    RPOLY#
    Internal node number for the right polygon. (Source: ESRI) Whole numbers that are automatically generated.
    LENGTH
    Length of feature in internal units. (Source: ESRI) Positive real numbers that are automatically generated.
    SAV07#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    SAV07-ID
    User-defined feature number. (Source: ESRI) Unknown
    sav07.pat
    Unknown (Source: Unknown)
    FID
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: ESRI) Coordinates defining the features.
    AREA
    Area of feature in internal units squared. (Source: ESRI) Positive real numbers that are automatically generated.
    PERIMETER
    Perimeter of feature in internal units. (Source: ESRI) Positive real numbers that are automatically generated.
    SAV07#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    SAV07-ID
    User-defined feature number. (Source: ESRI) Unknown
    FLUCCS
    Unknown (Source: Unknown) Unknown
    COMMON_NAME
    Unknown (Source: Unknown) Unknown
    ACRES
    Unknown (Source: Unknown) Unknown

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?
    Avineon Inc. Photointerpretation Staff- Daniel Bubser, Joseph Muller,Ryan Ligon Palm Beach County- Eric Anderson Applied Technology and Management- Michael Jenkins
  3. To whom should users address questions about the data?
    Keith Patterson
    Avineon, Inc.
    Director- Photogrammetry, Mapping, GIS
    15500 Lightwave Drive, Suite 200
    Clearwater, FL
    United States of America

    (727)539-1661 (voice)
    (727)539-6954 (FAX)
    kpatterson@avineon.com
    Hours_of_Service: 9:00AM to 5:00PM

Why was the data set created?

A major objective of the Lake Worth Lagoon Management Plan is to restore, preserve and create seagrass beds, oyster bars and other submerged benthic habitat. Aerial surveys will enable Palm Beach County Department of Environmental Resources Management to determine the aerial extent of seagrass beds, mangrove habitat, oyster reefs, and spartina within the Lake Worth Lagoon and Intracoastal Waterway, while the fixed transect survey will reveal whether selected seagrass beds are stable, expanding or receding.

How was the data set created?

  1. From what previous works were the data drawn?
    (none) (source 1 of 3)
    Imaging, US, Unknown, Lake Worth Lagoon.

    Type_of_Source_Media: True color diapositives, stereo coverage
    Source_Scale_Denominator: 10000
    Source_Contribution:
    Photographic signature for interpretation of benthic habitat data.
    (none) (source 2 of 3)
    Imaging, US, Unknown, Loxahatchee River.

    Type_of_Source_Media: True color diapositives, stereo coverage
    Source_Scale_Denominator: 4800
    Source_Contribution:
    Photographic signature for interpretation of benthic habitat data.
    (none) (source 3 of 3)
    Imaging, US, Unknown, Indian River Lagoon.

    Type_of_Source_Media: True color diapositives, stereo coverage
    Source_Scale_Denominator: 10000
    Source_Contribution:
    Photographic signature for interpretation of benthic habitat data.
  2. How were the data generated, processed, and modified?
    Date: Unknown (process 1 of 3)
    Avineon utilized Ground control from previous mapping efforts within Palm Beach County. Additional points were selected from DOQQ's. Most of the original control points were recovered from documentation and used. The pixel coordinate values, which are embedded within the digital orthophotographic imagery, were collected for photoidentifiable features on the DOQQ image.
    Date: Unknown (process 2 of 3)
    Metadata imported. Data sources used in this process:
    • C:\DOCUME~1\jmuller\LOCALS~1\Temp\xml2EC.tmp
    Date: Unknown (process 3 of 3)
    Metadata imported. Data sources used in this process:
    • F:\ATM_PBC\Lake_Worth\Final_Inspection\Final_Revisions_June\Final_CD\Reports\Metadata\Sav_07_Metadata.xml
  3. What similar or related data should the user be aware of?

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Attribute accuracy was tested by visual comparison of the aerial photographs with the habitat data to ensure consistency with the classification system and photo signatures. Pre-interpretation groundtruthing was also performed to aid in delineation and classification of photo signatures. Additional checks for valid attributes, as defined by the PBC ERM modified FLUCCS, were performed.
  2. How accurate are the geographic locations?
    Avineon utilized Ground control from previous mapping efforts within Palm Beach County. Additional points were selected from DOQQ's. Most of the original control points were recovered from documentation and used. Horizontal positional accuracy of the data meets NMAS for 1:24000 scale maps, approximately +/- 40 feet.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Minimum mapping unit for all feature class polygons is 0.25 acres. The study area boundary for the project was defined by Palm Beach County, Department of Environmental Resources Management . Features were captured and classified according to the minimum mapping unit guideline and the PBC ERM modified FLUCCS.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present. NODEERRORS run with Dangle option. No dangles present. UNSPLIT used to remove superfluous pseudo-nodes. LABELERRORS run, with all polygons attributed. RELATE was employed to check for contiguous arcs. No arcs have the same attribute on both sides.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None
Use_Constraints:
Acknowledgement of Avineon Inc. would be appreciated in products derived from this data. The positional accuracy of this data meets USGS NMAS for 1:24000 scale maps (+/- 40 feet).
  1. Who distributes the data set? (Distributor 1 of 1)
    Palm Beach County- Department of Environmental Resources Management
    2300 North Jog Road, 4th Floor
    West Palm Beach, FL
    United States

    (561) 233-2514 (voice)
    Eanderson1@co.palm-beach.fl.us
    Contact_Instructions: (contact via e-mail)
  2. What's the catalog number I need to order this data set? Downloadable Data
  3. What legal disclaimers am I supposed to read?
    This data is provided "as is" without warranty or any representation of accuracy, timeliness or completeness. The burden for determining accuracy, completeness, timeliness, merchantability and fitness for or the appropriateness for use rests solely on the requester. The County makes no warranties, express or implied, as to the use of the data. There are no implied warranties of merchantability or fitness for a particular purpose. The requester acknowledges and accepts the limitations of the data, including the fact that the data is dynamic and is in a constant state of maintenance, correction and update.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 06-Jan-2021
Last Reviewed: 24-Apr-2009
Metadata author:
Avineon Inc.
Attn: Keith Patterson
Director- Photogrammetry, Mapping, GIS
15500 Lightwave Drive, Suite 200
Clearwater, FL
USA

727-539-1661 (voice)
727-539-6954 (FAX)
kpatterson@avineon.com
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Generated by mp version 2.9.48 on Thu Mar 28 11:04:07 2024