Florida Public Land Survey System - Township and Range Level - Statewide

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: University of Florida GeoPlan Center

Publication_Date: 2004

Title:

Florida Public Land Survey System - Township and Range Level - Statewide

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Other_Citation_Details: State of Florida

Online_Linkage: <http://www.fgdl.org>

Description:

Abstract:

The Public Land Survey System (PLSS) is a legal land reference system created to facilitate the inventory and transfer of property. This system is divided into township, range, and sections. This shapefile contains PLSS boundaries to the township and range level. Further PLSS data down to the section level can be found on the FGDL website. This dataset was created by GeoPlan using data from the Bureau of Land Management (BLM) combined with existing PLSS data to fill in known gaps.

Purpose:

This polygon shapefile was created to facilitate the inventory and transfer of property.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 2004

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -87.429040

East_Bounding_Coordinate: -79.872251

North_Bounding_Coordinate: 30.983191

South_Bounding_Coordinate: 24.492815

Keywords:

Theme:

Theme_Keyword_Thesaurus: NONE

Theme_Keyword: planningCadastre

Theme:

Theme_Keyword_Thesaurus: NONE

Theme_Keyword: PLSS

Theme_Keyword: Townships

Theme_Keyword: Ranges

Theme_Keyword: TRS

Place:

Place_Keyword_Thesaurus: NONE

Place_Keyword: Florida

Access_Constraints: NONE

Use_Constraints:

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.
A note about data scale:
Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modelling purposes. Please be sure you are using the best available data.
1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger.
Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: <http://geoplan.ufl.edu/education.html>

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Florida Geographic Data Library (FGDL)

Contact_Person: GIS Specialist

Contact_Position: Data Manager

Contact_Address:

Address_Type: mailing address

Address: 431 Architecture PO Box 115706

City: Gainesville

State_or_Province: Florida

Postal_Code: 32611-5706

Contact_Electronic_Mail_Address:

Web site: <http://www.fgdl.org>

Contact_Electronic_Mail_Address:

Technical Support: <http://www.fgdl.org/fgdlfeed.html>

Contact_Electronic_Mail_Address:

For FGDL Software: <http://www.fgdl.org/software.html>

Contact_Electronic_Mail_Address:

FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>

Contact_Electronic_Mail_Address:

Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>

Native_Data_Set_Environment:

Microsoft Windows Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.4000

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

GeoPlan relied on the integrity of the attribute information within the original data.

Quantitative_Attribute_Accuracy_Assessment:

Attribute_Accuracy_Explanation:

This data set was modified by GeoPlan center in 2002 using GIS techniques to summarize sections. This eliminated many slivers and drastically reduced the size of the dataset. This causes the county boundary field in the shapefile to be slightly inaccurate. Sections that cross over county boundary lines will only get one county name. This data set documents how the original PLSS looked when it was created in the early 1800's. This, along with the original field notes, serve as the documentation for many legal boundaries in Florida. These boundaries are set and the data layer will not change.
Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modelling purposes. Please be sure you are using the best available data.
1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries.
1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger.
Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: <http://geoplan.ufl.edu/education.html>. These data are based on interpretation of available information and should not be construed as legally binding.

Logical_Consistency_Report:

Relied on the integrity of the attribute information within the original data layer.

Completeness_Report:

Relied on the integrity of the attribute information within the original data layer.

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan

Vertical_Positional_Accuracy:

Vertical_Positional_Accuracy_Report:

This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: FLORIDA RESOURCES & ENVIRONMENTAL ANALYSIS CENTER

Originator: SOUTH FLORIDA WATER MANAGEMENT DISTRICT

Originator: SOUTH WEST FLORIDA WATER MANAGEMENT DISTRICT

Originator: SUWANNEE RIVER WATER MANAGEMENT DISTRICT

Originator: ST. JOHN'S RIVER WATER MANAGEMENT DISTRICT

Title: Public Land Survey System (PLSS)

Source_Scale_Denominator: 1:24,000

Type_of_Source_Media:

Source_Citation_Abbreviation: GeoPlan

Source_Contribution: Spatial and Attribute Information

Process_Step:

Process_Description:

The original data was in both DLG and Coverage format depending on the source. Source data was converted to coverage. The data then existed in previous versions of FGDL (i.e. FGDL V3 or less) as county data sets. The coverages were merged together. Next the eliminate command was run in ArcInfo Workstation. Then the Coverage was converted to a shapefile and a dissolve was executed. The dissolve was used in order to change all sections with multiple polygons into one section.

Process_Date: Unknown

Process_Step:

Process_Description:

This dataset was created by GeoPlan using information from two sources, the Bureau of Land Management (BLM) Public Land Survey System (PLSS) Data Download and the Florida Geographic Data Library (FGDL).
The first layer, from the BLM, contained data on the township and range level. However, this dataset had a few gaps across the state. These holes were filled in using the layer from FGDL. This layer had more detailed information, breaking the townships and ranges into sections. These sections were dissolved, using the ArcMap tool, into the larger townships and ranges so that they would match the data from the BLM. The BLM layer was projected into the projection type matching the FGDL layer, FGDL Albers.
After the FGDL layer was dissolved on township and range, the features from the FGDL layer that filled in the holes found in the BLM layer were selected and exported to a new layer. Some spatial discrepancy was present between the two layers, even though both had the same projection information (the BLM layer was projected into the correct projection), FGDL Albers. To repair these discrepancies, the layer from FGDL was edited using the Spatial Adjustment tool in conjunction with the Editor toolbar. The specific Spatial Adjustment method used was Rubbersheet. The rubbersheet process followed these steps: - Start an edit session, select the proper layer to edit, in this case the FGDL layer - Ensure the Spatial Adjustment toolbar is present on the toolbar section - In the Spatial Adjustment menu, hover over "Adjustment Method" and click "Rubbersheet" - In the Spatial Adjustment menu, click on "Set Adjust Data...", click "All features in these layers" and ensure the only layer being altered (the FGDL layer) is selected, click "OK" - Make sure the Snapping toolbar is present and is set to snap to vertexes, and not to edges - Now that all the preliminary settings are in place, select vertices from the FGDL layer and move them to the nearest vertex from the BLM layer - Periodically, in the Spatial Adjustment menu, click "Adjust" to move the vertices to the new locations selected and save edits to ensure work is not lost
After the Rubbersheet process was completed for all features of the layer where edits were necessary, the Integrate tool was used. This tool ensures that micro-scale discrepancies between polygon boundaries are repaired so they are right on top of each other. In the Integrate tool, two layers were used to repair the gaps, one with the features created by BLM and one with features created by GeoPlan. The BLM layer was ranked first and the GeoPlan layer was ranked second. The distance threshold was 0.5 meters. The GeoPlan layer was then merged with the non-integrated BLM data to ensure that no points were altered from the BLM data. This created the final layer. Then, the attribute information had to be edited using Xtools so that the merge could be completed effectively. After the merge, attribute information was cleaned so that it met GeoPlan's requirements. Fields were added, edited, or deleted so that the current fields are: FID, Shape, TOWN, TOWN_DIR, RANGE, RANGE_DIR, LABEL, F_SOURCE, DATEMODIFI, DATECREATE, FGDLAQDATE, DESCRIPT.
All of the records were upcased.

Source_Used_Citation_Abbreviation: GeoPlan

Process_Date: 20160308

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: G-polygon

Point_and_Vector_Object_Count: 1892

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Albers Conical Equal Area

Albers_Conical_Equal_Area:

Standard_Parallel: 24.000000

Standard_Parallel: 31.500000

Longitude_of_Central_Meridian: -84.000000

Latitude_of_Projection_Origin: 24.000000

False_Easting: 400000.000000

False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.002048

Ordinate_Resolution: 0.002048

Planar_Distance_Units: meters

Geodetic_Model:

Horizontal_Datum_Name: D_North_American_1983_HARN

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Vertical_Coordinate_System_Definition:

Altitude_System_Definition:

Altitude_Resolution: 1.000000

Altitude_Encoding_Method:

Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: PLSS_TR_2004

Entity_Type_Definition: PLSS_TR_2004.DBF

Entity_Type_Definition_Source: GeoPlan

Attribute:

Attribute_Label: OBJECTID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: TOWN

Attribute_Definition: Township Number

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: TOWN_DIR

Attribute_Definition: Township Direction (N=North, S=South)

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: RANGE

Attribute_Definition: Range Number

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: RANGE_DIR

Attribute_Definition: Range Direction (E= East, W=West)

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: LABEL

Attribute_Definition:

GeoPlan added field combining Township, Township Direction, Range, and Range Direction

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: F_SOURCE

Attribute_Definition: Source of Feature Information

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: DATEMODIFI

Attribute_Definition: Undefined by source

Attribute_Definition_Source: BLM

Attribute:

Attribute_Label: DATECREATE

Attribute_Definition: Undefined by source

Attribute_Definition_Source: BLM

Attribute:

Attribute_Label: FGDLAQDATE

Attribute_Definition: The date GeoPlan acquired the data from the source

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: DESCRIPT

Attribute_Definition: GeoPlan added field based on LABEL

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: AUTOID

Attribute_Definition: Unique ID added by GeoPlan

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: SHAPE.AREA

Attribute_Definition: Area in meters

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: SHAPE.LEN

Attribute_Definition: Perimeter in meters

Attribute_Definition_Source: GeoPlan

Distribution_Information:

Distributor:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Florida Geographic Data Library (FGDL)

Contact_Person:

Contact_Position:

Contact_Address:

Address_Type: mailing address

Address: 431 Architecture PO Box 115706

City: Gainesville

State_or_Province: Florida

Postal_Code: 32611-5706

Country: United States

Contact_Voice_Telephone:

Contact_TDD/TTY_Telephone:

Contact_Facsimile_Telephone:

Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>

Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>

Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>

Contact_Electronic_Mail_Address:

FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>

Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>

Hours_of_Service:

Contact_Instructions:

Resource_Description: DOWNLOADABLE DATA

Distribution_Liability:

The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist.
Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials.
A note about data scale:
Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data.
1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger.
Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: <http://geoplan.ufl.edu/education.html>

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Transfer_Size: 5.579

Technical_Prerequisites:

This data is intended for use with a Geographic Information Systems or Remote Sensing software package.

Metadata_Reference_Information:

Metadata_Date: 20160527

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: University of Florida GeoPlan Center

Contact_Address:

Address_Type: mailing address

Address: 131 Architecture PO Box 115706

Address: Florida State University

Address: UCC 2200

City: Gainesville

State_or_Province: FL

Postal_Code: 32611-5706

Country: USA

Contact_Electronic_Mail_Address: data@fgdl.org

Contact_Electronic_Mail_Address: maps@admin.fsu.edu

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Extensions:

Metadata_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile