RGIS::2979458e-2d51-40bf-8df3-7c4ba7bb6b40::ISO-19115:2003 eng; USA U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch 301-763-1128 301-763-4710 4600 Silver Hill Road, Stop 7400 Washington DC 20233-7400 United States geo.tiger@census.gov pointOfContact 2014-06-16 ISO 19115 Geographic Information - Metadata ISO 19115 9308 Socorro County (35053) North American Datum of 1983 in the 48 contiguous states, the District of Columbia, Alaska, Hawaii, Puerto Rico, the Virgin Islands of the United States, and the Pacific Island Areas. revision http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 resourceProvider 4269 Geodetic Reference System 80 revision http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:ellipsoid:EPSG::7019 resourceProvider 7019 Catron County 2010 Census Roads 2011-06-06T15:00:59 publication Downloadable Data U.S. Department of Commerce, U.S. Census Bureau, Geography Division originator The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB tha begin with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways. In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles. U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch 301-763-1128 301-763-4710 4600 Silver Hill Road, Stop 7400 Washington DC 20233-7400 United States geo.tiger@census.gov County or equivalent entity Linear Feature Address Range Street Centerline Road Feature Roads None United States U.S. County or Equivalent Entity Catron 35003 INCITS.38-200x (R2004),INCITS.31-200x (R2007),INCITS.454-200x,INCITS 455-200x,INCITS 446-2008 Access Constraints: None. Use Constraints: The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The horizontal spatial accuracy information present in these files is provided for the purposes of statistical analysis and census operations only. No warranty, expressed or implied is made with regard to the accuracy of the spatial accuracy, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau, specifically as to the spatial or attribute accuracy of the data. The TIGER/Line Shapefiles may not be suitable for high-precision measurement applications such as engineering problems, property transfers, or other uses that might require highly accurate measurements of the earth's surface.Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest. The data are free from Title 13 restrictions. eng; USA transportation -109.047309 -107.711924 33.200967 34.581008 publication date 2010-01-01 2010-07-01 true Entity and Attribute Information http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/ISO-19110.xml http Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu ZIP 4 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.original.zip Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu ESRI Shapefile (shp) 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.shp Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu GML 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.gml Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu KML 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.kml Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu GeoJSON 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.geojson Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu JSON 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.json Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu Comma Separated Values (csv) 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.csv Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu MS Excel format (xls) 25 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.xls http://www.census.gov/geo/www/tiger http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/services/ogc/wms?SERVICE=wms&REQUEST=GetCapabilities&VERSION=1.1.1 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/services/ogc/wfs?SERVICE=wfs&REQUEST=GetCapabilities&VERSION=1.0.0 http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.shp http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.original.zip http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.gml http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.kml http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.geojson http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.json http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.csv http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/tl_2010_35003_roads.derived.xls http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/FGDC-STD-001-1998.xml http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/FGDC-STD-001-1998.html http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/ISO-19115:2003.xml http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/ISO-19115:2003.html http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/ISO-19119:WMS.xml http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/ISO-19119:WFS.xml http://gstore.unm.edu/apps/rgisarchive/datasets/2979458e-2d51-40bf-8df3-7c4ba7bb6b40/metadata/ISO-19110.xml Horizontal Positional Accuracy The Census Bureau uses root mean square error (RMSE) as stated in the FGDC-STD-007. 3-1998, Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy. The Census Bureau uses Global Positioning System (GPS) coordinates at road centerline intersections to evaluate the horizontal spatial accuracy of source files that may be used to realign road features in the MAF/TIGER database and test the horizontal spatial accuracy of the road features in the TIGER/Line Shapefiles. The test compares a survey-grade GPS coordinate to its associated road centerline intersection in the TIGER/Line Shapefiles. The test is based on an independent collection of GPS coordinates for a random sample of road intersections from a centerline file that meet certain criteria. The points are referred to as the sample points and are gathered through a private contractor working for the Census Bureau. Since the collection method uses survey-quality GPS-based field techniques, the resulting control points are considered 'ground truth' against which the TIGER road centerline intersection coordinates are compared. The distances between the coordinates are calculated and the Census Bureau determines the Circular Error 95% (CE95). That is, the accuracy of the file in meters with 95% confidence. The CE95 can be calculated from the mean and standard deviation by using the formula: mean of differences plus (2.65 times the standard deviation). CE95 results reported for each file tested are determined using a spreadsheet with embedded statistical formula. The use and applicability of the spreadsheet and its embedded formula have been verified by Census Bureau statisticians. The basis of the calculation is the use of the root mean square error (RMSE). This is the method as stated in the U.S. Government's Federal Geographic Data Committee Standard FGDC-STD-007.3-1998, Geospatial Positioning Accuracy Standards. Part 3: National Standard for Spatial Data Accuracy. The results of using this measure of accuracy are in compliance with Federal Spatial Data requirements. In terms of the Census Bureau application, the dataset coordinate values are those taken from the centerline file and the coordinate values from an independent source of higher accuracy are those acquired through the Census Bureau's contractor. Please note that the horizontal spatial accuracy, where reported, refers only to the realigned road features identified as matched to the positionally accurate source file with that accuracy. It is not the spatial accuracy of the TIGER/Line Shapefile as a whole. 4.517 Horizontal Positional Accuracy The Census Bureau uses root mean square error (RMSE) as stated in the FGDC-STD-007. 3-1998, Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy. The Census Bureau uses Global Positioning System (GPS) coordinates at road centerline intersections to evaluate the horizontal spatial accuracy of source files that may be used to realign road features in the MAF/TIGER database and test the horizontal spatial accuracy of the road features in the TIGER/Line Shapefiles. The test compares a survey-grade GPS coordinate to its associated road centerline intersection in the TIGER/Line Shapefiles. The test is based on an independent collection of GPS coordinates for a random sample of road intersections from a centerline file that meet certain criteria. The points are referred to as the sample points and are gathered through a private contractor working for the Census Bureau. Since the collection method uses survey-quality GPS-based field techniques, the resulting control points are considered 'ground truth' against which the TIGER road centerline intersection coordinates are compared. The distances between the coordinates are calculated and the Census Bureau determines the Circular Error 95% (CE95). That is, the accuracy of the file in meters with 95% confidence. The CE95 can be calculated from the mean and standard deviation by using the formula: mean of differences plus (2.65 times the standard deviation). CE95 results reported for each file tested are determined using a spreadsheet with embedded statistical formula. The use and applicability of the spreadsheet and its embedded formula have been verified by Census Bureau statisticians. The basis of the calculation is the use of the root mean square error (RMSE). This is the method as stated in the U.S. Government's Federal Geographic Data Committee Standard FGDC-STD-007.3-1998, Geospatial Positioning Accuracy Standards. Part 3: National Standard for Spatial Data Accuracy. The results of using this measure of accuracy are in compliance with Federal Spatial Data requirements. In terms of the Census Bureau application, the dataset coordinate values are those taken from the centerline file and the coordinate values from an independent source of higher accuracy are those acquired through the Census Bureau's contractor. Please note that the horizontal spatial accuracy, where reported, refers only to the realigned road features identified as matched to the positionally accurate source file with that accuracy. It is not the spatial accuracy of the TIGER/Line Shapefile as a whole. 6.2 There may be some inconsistencies in feature names along features. An anomaly exists with the sporadic occurrence of road segments comprising a complete chain with different MAF/TIGER Feature Census Class Code (MTFCC) values assigned. This problem could affect applications that use the MTFCC values for network analysis, routing, or for assigning symbology to a feature when creating a map. The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Node/geometry and topology relationships are collected or generated to satisfy topological edit requirements. These requirements include: (1) Complete chains must begin and end at nodes. (2) Complete chains must connect to each other at nodes. (3) Complete chains do not extend through nodes. (4) Left and right polygons are defined for each complete chain element and are consistent throughout the extract process. (5) The chains representing the limits of the files are free of gaps. TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for all of the aforementioned geographic entities are then distributed among the shapefiles each containing attributes for line, polygon, or landmark geographic data. 2010-01-01T00:00:00 MAF/TIGER The selected geographic and cartographic information (line segments) are derived from the U.S. Census Bureau's Master Address File Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. Census MAF/TIGER database MAF/TIGER U.S. Department of Commerce, U.S. Census Bureau, Geography Division publication date 2010-01-01 2010-07-01 Coordinates to realign selected road features in the Census MAF/TIGER database. Catron Co. NM - From NAIP Catron 3978 Harris Corporation Unknown Coordinates to realign selected hydrographic features in the Census MAF/TIGER database. National Hydrography Dataset - High Res. National 3979 USGS - National Hydrography Dataset Coordination and Requirements (C&R) Unknown Coordinates to realign selected road features in the Census MAF/TIGER database. Socorro Co., NM - Harris Centerline Socorro 5793 Harris Corporation Unknown Coordinates to realign selected road features in the Census MAF/TIGER database. 2010 ADCAN GPS Feature Updates 2010 7190 Census Bureau - Geography Division US Census Bureau - Geo Div - LFGPB Unknown Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT custodian