20140818 12232200 FALSE 20121010 17062900 20121010 17062900 1.0 PLSSTownships_GCDB1 002 228583.430000 673944.590000 4094743.900000 4653571.760000 1 Projected GCS_North_American_1983 NAD_1983_UTM_Zone_12N <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.1'><WKT>PROJCS[&quot;NAD_1983_UTM_Zone_12N&quot;,GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433]],PROJECTION[&quot;Transverse_Mercator&quot;],PARAMETER[&quot;False_Easting&quot;,500000.0],PARAMETER[&quot;False_Northing&quot;,0.0],PARAMETER[&quot;Central_Meridian&quot;,-111.0],PARAMETER[&quot;Scale_Factor&quot;,0.9996],PARAMETER[&quot;Latitude_Of_Origin&quot;,0.0],UNIT[&quot;Meter&quot;,1.0],AUTHORITY[&quot;EPSG&quot;,26912]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26912</WKID><LatestWKID>26912</LatestWKID></ProjectedCoordinateSystem> Linear Unit: Meter (1.000000) ItemDescription FGDC CSDGM Metadata PLSSTownships_GCDB1 -114.276444 -108.899225 42.034185 36.959686 1 -114.276444 -108.899225 42.034185 36.959686 1 The CADNSDI or the Cadastral Publication Data Standard is the cadastral data component of the NSDI. This is the publication guideline for cadastral data that is intended to provide a common format and structure and content for cadastral information that can be made available across jurisdictional boundaries, providing a consistent and uniform cadastral data to meet business need that includes connections to the source information from the data stewards. The data stewards determine which data are published and should be contacted for any questions on data content or for additional information. The cadastral publication data is data provided by cadastral data producers in a standard form on a regular basis. Cadastral publication data has two primary components, land parcel data and cadastral reference data. It is important to recognize that the publication data are not the same as the operation and maintenance or production data. The production data is structured to optimize maintenance processes, is integrated with internal agency operations and contains much more detail than the publication data. The publication data is a subset of the more complete production data and is reformatted to meet a national standard so data can be integrated across jurisdictional boundaries and be presented in a consistent and standard form nationally. <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>PLSSTownship_GCDB is the first level of a hierarchical break down of the Public Land Survey System Rectangular surveys. </SPAN><SPAN>This data is Version 1.10 of the Utah GCDB. This data set represents the GIS Version of the Public Land Survey System. Updates are expected annually as horizontal control positions from published sources and global positioning system (GPS) observations are added. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. This data was orginally published on 1/21/2011</SPAN></P><P><SPAN /></P></DIV></DIV></DIV> Utah BLM, Utah Automated Geographic Reference Center (AGRC),Utah Counties, Premier Data Services planningCadastre Cadastral PLSS Public Land Survey System Cadastral Reference PLSS Sections PLSS Divisions PLSS Special Surveys Parcels PLSS Corners This data is for GIS and mapping purposes and is not intended to support or replace land survey data or the information provided by land survey. Esri ArcGIS 10.1.0.3035 002 0 File Geodatabase Feature Class dataset EPSG 7.9.4 PLSSID Simple FALSE 0 TRUE FALSE PLSSTownships_GCDB1 Feature Class 0 In the Public Land Survey System a Township refers to a unit of land, that is nominally six miles on a side, usually containing 36 sections. OBJECTID OBJECTID OID 4 0 0 Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 0 0 0 Feature geometry. ESRI Coordinates defining the features. PLSSID PLSS Township Identifer String 16 0 0 Concatenation of the principal meridian, township, range, and duplication code that form a unique id. TOWNSHIP TOWNSHIP String 5 0 0 Principal meridian name as a text RANGE RANGE String 5 0 0 Principal meridian code from the BLM PM Code list BASEMERIDIAN BASEMERIDIAN String 2 0 0 Range direction. The direction of a column of townships from a Public Land Survey System Origin. These are typcially East or West in the west but may be north or south in Ohio LABEL LABEL String 20 0 0 Range fraction. Range Fractions are created when there are gaps between surveyed Township boundaries or due to excess size in Townships that arose from executing original surveys. STATEABBR State Abbreviation String 2 0 0 Range number. The Range Number indicates the number of columns of townships, east or west from a Public Land Survey System Origin. PRINMERCD Prime Meridian Code String 2 0 0 The secondary name for Ohio survey area, PLSS original survey areas PRINMER Prime Meridian Text String 40 0 0 The Ohio Named survey area, PLSS original survey areas TWNSHPNO PLSS Township Number String 3 0 0 State abbreviation code two letter postal code TWNSHPFRAC PLSS Township Fraction String 1 0 0 Data steward for a township. TWNSHPDIR PLSS Township Direction String 1 0 0 Township direction. The direction of a row of Townships from a Public Land Survey System Origin. These are typcially North and South in the West but may be East and West in Ohio RANGENO PLSS Range Number String 3 0 0 If there are multiple townships in a Public Land Survey System Origin, State and Survey Name, the Township Duplicate Status is used to establish uniqueness. When more than one Public Land Survey System Township has the same Township and Range numbers and directions and fractions, and are in the same State, this attribute is used to distinguish among duplicate values. RANGEFRAC PLSS Range Fraction String 1 0 0 Township fraction. Township Fractions are created when there are gaps between surveyed Township boundaries or due to excess size in Townships that arose from executing original surveys. RANGEDIR PLSS Range Direction String 1 0 0 Township label that is used for cartographic output or web display TWNSHPDPCD PLSS Township Duplicate Code String 1 0 0 Township number. The Township Number indicates the number of rows of townships, north or south from a Public Land Survey System Origin. STEWARD Data Steward for PLSS Township Data String 50 0 0 TWNSHPLAB PLSS Township Label String 20 0 0 SRVNAME Survey Name for Ohio PLSS Surveys String 60 0 0 SECSRVNAME Secondary Survey Name for Ohio Surveys String 60 0 0 SURVTYP Survey Type Code String 2 0 0 SURVTYPTXT SurveyType Text String 50 0 0 TNUM TNUM Double 8 0 0 RNUM RNUM Double 8 0 0 QNUM QNUM Integer 4 0 0 Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. Shape_Area Shape_Area Double 8 0 0 Area of feature in internal units squared. Esri Positive real numbers that are automatically generated. 20121010 BLM Utah State Office GCDB Manager (801) 539-4160 shope@blm.gov BLM Cadastral Survey June 1, 2010 PLSSTownships Final vector digital data withheld planningCadastre IOS 19115 Topic Category planningCadastre IOS 19115 Topic Category planningCadastre Geographic Names Information System (GNIS) United States PLSSTownship_GCDB is the first level of a hierarchical break down of the Public Land Survey System Rectangular surveys. This data is Version 1.10 of the Utah GCDB. This data set represents the GIS Version of the Public Land Survey System. Updates are expected annually as horizontal control positions from published sources and global positioning system (GPS) observations are added. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. This data was orginally published on 1/21/2011 The CADNSDI or the Cadastral Publication Data Standard is the cadastral data component of the NSDI. This is the publication guideline for cadastral data that is intended to provide a common format and structure and content for cadastral information that can be made available across jurisdictional boundaries, providing a consistent and uniform cadastral data to meet business need that includes connections to the source information from the data stewards. The data stewards determine which data are published and should be contacted for any questions on data content or for additional information. The cadastral publication data is data provided by cadastral data producers in a standard form on a regular basis. Cadastral publication data has two primary components, land parcel data and cadastral reference data. It is important to recognize that the publication data are not the same as the operation and maintenance or production data. The production data is structured to optimize maintenance processes, is integrated with internal agency operations and contains much more detail than the publication data. The publication data is a subset of the more complete production data and is reformatted to meet a national standard so data can be integrated across jurisdictional boundaries and be presented in a consistent and standard form nationally. en publication date 1/21/2011 Complete Irregular none This data is for GIS and mapping purposes and is not intended to support or replace land survey data or the information provided by land survey. Utah BLM, Utah Automated Geographic Reference Center (AGRC),Utah Counties, Premier Data Services ESRI ArcCatalog 9.3.1.4000 File Geodatabase Feature Class Subcommittee Chair FGDC Cadastral Subcommittee 20110114 en FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time Data conforming to the Publication Guideline should follow for the format and structure of the standard for published data. This means that the topological relationships of the PLSS and parcels should be followed. Level 1 conformance to the guideline means that the data follows and conforms to the structure and an active data steward is identified and engaged in data creation and maintenance. Level 2 conformance all attributes that are necessary for essential query, extraction, labeling and use are present. Level 3 conformance all attributes as applicable are populated. The Utah Data Set is at Level 3 of 3 Conformance and fully complies with the national standard The Subcommittee recognizes that not all data is available in all places, but the data that is available should be provided for publication in the format provided in this guideleines. Exceptions to complete data should be noted by the data steward. The Utah Data Set contains all of the available GCDB PLSS data. In addition PLSS data from four counties, Webster, Salt Lake, Utah and Davis have been integrated into the data set. Note the Data Steward in the Metadata at a Glance Feature Class for these areas. Executive Order 12906 calls for the establishment of the National Spatial Data Infrastructure defined as the technologies, policies, and people necessary to promote sharing of geospatial data throughout all levels of government, the private and non-profit sectors, and the academic community. GCS_North_American_1983 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 The completed CADNSDI should be made available a public resource. There are many ways this data can be published included web services, data services or as a downloadable file. Data distributors should not modify the data in any way. The data stewards are responsible for the data content and quality. The data distributors should be providing access to the information but not changing the content.