SDETrims.DBO.Trans_Roads

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  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?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How should this data set be cited?

   The data was created and provided by TeleAtlas North America through a StratMap contract., Unknown, SDETrims.DBO.Trans_Roads.

   Online Links:

   • Service=sde:sqlserver:CHUCKNORRIS; Database=SDETrims; Version=dbo.DEFAULT

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -98.971382

   East_Bounding_Coordinate: -94.083461

   North_Bounding_Coordinate: 34.144092

   South_Bounding_Coordinate: 29.524636

3. What does it look like?

4. Does the data set describe conditions during a particular time period?

   Calendar_Date: Aug-2006

   Currentness_Reference: publication 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):

      • String (1029365)

   2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      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.
      

      Vertical_Coordinate_System_Definition:

      Altitude_System_Definition:

      Altitude_Resolution: 1.000000

      Altitude_Encoding_Method:

      Explicit elevation coordinate included with horizontal coordinates

7. How does the data set describe geographic features?

   SDETrims.DBO.Trans_Roads

   OBJECTID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   STRATMAPID

   7-digit sequential number prefixed with a 3-character jurisdiction code (County FIPS Code). (Source: TNRIS)

   PREFIX

   Modifier to street name. (Source: TNRIS)

   PRETYPE

   Supports geocoding, which allows for additional parsing of segment names. (Source: TNRIS)

   NAME

   FEATURE NAME (Source: TNRIS)

   TYPE

   FEATURE STREET TYPE: ST, RD, HWY, etc. (Source: TNRIS)

   EXT

   FEATURE EXTENSION (Source: TNRIS)

   SUFFIX

   FEATURE SUFFIX: Modifier to street name. (Source: TNRIS)

   FCC

   FEATURE CLASS CODE: 1st character (letter) classifies the feature. 2nd character (number) describes the major category. 3rd character (number) describes the minor category. (Source: TNRIS)

   POSTAL_L

   5-digit ZIP Code area on the left side of the street segment. (Source: TNRIS)

   POSTAL_R

   5-digit ZIP Code area on the right side of the street segment. (Source: TNRIS)

   NAME_TYPE

   Indicates whether the street name can be used for geocoding or routing. (Source: TNRIS)

   SHIELD

   The first character of the shield field indicates what shield should be sued to represent each name based on its Primary Name. (Source: TNRIS)

   HWY_NUM

   Field will be populated only on FCC segments of A1, A2 and A3

   SEG_LEN

   Length of Segment (Source: TNRIS)

   FT_DIR

   Field conveys information about the described direction of travel along highways in the digitized From-to direction. Permissible values for this field are N, S, E, W, NE, SE, NW, SW. (Source: TNRIS)

   TF_DIR

   Field conveys information about the described direction of travel along highways in the digitized To-from direction. Permissible values for this field are N, S, E, W, NE, SE, NW, SW. (Source: TNRIS)

   NAME_FLAG

   Field is a coded indicator of whether a street name is most apporpriate for statewide or cross-country routing (field content = '1'); whether a street name is most appropriate for geocoding (field content = '2'); and whether the routing name is also appropriate for geocoding purposes (field content = '3'). (Source: TNRIS)

   NAME_SRCE

   Field conveys where the name on a segment was derived from. (Source: TNRIS)

   GEOM_SRCE

   Field conveys what was used to modify the position of a street segment. (Source: TNRIS)

   GEOM_ACC

   Field conveys what was used to modify the position of a street segment. (Source: TNRIS)

   A1_PREFIX

   ALT. 1 PREFIX (Source: TNRIS)

   A1_PRETYPE

   ALT. 1 PRETYPE (Source: TNRIS)

   A1_NAME

   ALT. 1 NAME (Source: TNRIS)

   A1_TYPE

   ALT. 1 TYPE (Source: TNRIS)

   A1_EXT

   ALT. 1 EXT (Source: TNRIS)

   A1_SUFFIX

   ALT. 1 SUFFIX (Source: TNRIS)

   A1_NM_TYPE

   ALT. 1 NM_TYPE (Source: TNRIS)

   A1_SHIELD

   ALT. 1 SHIELD (Source: TNRIS)

   A1_HWY_NUM

   ALT. 1 HWY_NUM (Source: TNRIS)

   A1_NM_FLAG

   ALT. 1 NM_FLAG (Source: TNRIS)

   A1_NM_SRCE

   ALT. 1 NM_SRCE (Source: TNRIS)

   A2_PREFIX

   ALT. 2 PREFIX (Source: TNRIS)

   A2_PRETYPE

   ALT. 2 PRETYPE (Source: TNRIS)

   A2_NAME

   ALT. 2 NAME (Source: TNRIS)

   A2_TYPE

   ALT. 2 TYPE (Source: TNRIS)

   A2_EXT

   ALT. 2 EXT (Source: TNRIS)

   A2_SUFFIX

   ALT. 2 SUFFIX (Source: TNRIS)

   A2_NM_TYPE

   ALT. 2 NM_TYPE (Source: TNRIS)

   A2_SHIELD

   ALT. 2 SHIELD (Source: TNRIS)

   A2_HWY_NUM

   ALT. 2 HWY_NUM (Source: TNRIS)

   A2_NM_FLAG

   ALT. 2 NM_FLAG (Source: TNRIS)

   A2_NM_SRCE

   ALT. 2 NM_SRCE (Source: TNRIS)

   A3_PREFIX

   ALT. 3 PREFIX (Source: TNRIS)

   A3_PRETYPE

   ALT. 3 PRETYPE (Source: TNRIS)

   A3_NAME

   ALT. 3 NAME (Source: TNRIS)

   A3_TYPE

   ALT. 3 TYPE (Source: TNRIS)

   A3_EXT

   ALT. 3 EXT (Source: TNRIS)

   A3_SUFFIX

   ALT. 3 SUFFIX (Source: TNRIS)

   A3_NM_TYPE

   ALT. 3 NM_TYPE (Source: TNRIS)

   A3_SHIELD

   ALT. 3 SHIELD (Source: TNRIS)

   A3_HWY_NUM

   ALT. 3 HWY_NUM (Source: TNRIS)

   A3_NM_FLAG

   ALT. 3 NM_FLAG (Source: TNRIS)

   A3_NM_SRCE

   ALT. 3 NM_SRCE (Source: TNRIS)

   A4_PREFIX

   ALT. 4 PREFIX (Source: TNRIS)

   A4_PRETYPE

   ALT. 4 PRETYPE (Source: TNRIS)

   A4_NAME

   ALT. 4 NAME (Source: TNRIS)

   A4_TYPE

   ALT. 4 TYPE (Source: TNRIS)

   A4_EXT

   ALT. 4 EXT (Source: TNRIS)

   A4_SUFFIX

   ALT. 4 SUFFIX (Source: TNRIS)

   A4_NM_TYPE

   ALT. 4 NM_TYPE (Source: TNRIS)

   A4_SHIELD

   ALT. 4 SHIELD (Source: TNRIS)

   A4_HWY_NUM

   ALT. 4 HWY_NUM (Source: TNRIS)

   A4_NM_FLAG

   ALT. 4 NM_FLAG (Source: TNRIS)

   A4_NM_SRCE

   ALT. 4 NM_SRCE (Source: TNRIS)

   A5_PREFIX

   ALT. 5 PREFIX (Source: TNRIS)

   A5_PRETYPE

   ALT. 5 PRETYPE (Source: TNRIS)

   A5_NAME

   ALT. 5 NAME (Source: TNRIS)

   A5_TYPE

   ALT. 5 TYPE (Source: TNRIS)

   A5_EXT

   ALT. 5 EXT (Source: TNRIS)

   A5_SUFFIX

   ALT. 5 SUFFIX (Source: TNRIS)

   A5_NM_TYPE

   ALT. 5 NM_TYPE (Source: TNRIS)

   A5_SHIELD

   ALT. 5 SHIELD (Source: TNRIS)

   A5_HWY_NUM

   ALT. 5 HWY_NUM (Source: TNRIS)

   A5_NM_FLAG

   ALT. 5 NM_FLAG (Source: TNRIS)

   A5_NM_SRCE

   ALT. 5 NM_SRCE (Source: TNRIS)

   STATE00_L

   STATE FIPS CODE: Used for geocoding (L=Left) (Source: TNRIS)

   STATE00_R

   STATE FIPS CODE: Used for geocoding (R=Right) (Source: TNRIS)

   COUNTY00_L

   COUNTY FIPS CODE: Used for geocoding (L=Left) (Source: TNRIS)

   COUNTY00_R

   COUNTY FIPS CODE: Used for geocoding (R=Right) (Source: TNRIS)

   MCD00_L

   MINOR CIVIL DIVISIONS: Used for geocoding (L=Left) (Source: TNRIS)

   MCD00_R

   MINOR CIVIL DIVISIONS: Used for geocoding (R=Right) (Source: TNRIS)

   PLACE00_L

   PLACE FIPS CODE (Used for geocoding (L=Left) (Source: TNRIS)

   PLACE00_R

   PLACE FIPS CODE (Used for geocoding (R=Right) (Source: TNRIS)

   FULL_NAME

   Concatenated primary FULL NAME of the street segment. (Source: TNRIS)

   A1_FULL_NA

   ALT. 1: Concatenated primary FULL NAME of the street segment. (Source: TNRIS)

   A2_FULL_NA

   ALT. 2: Concatenated primary FULL NAME of the street segment. (Source: TNRIS)

   A3_FULL_NA

   ALT. 3: Concatenated primary FULL NAME of the street segment. (Source: TNRIS)

   A4_FULL_NA

   ALT. 4: Concatenated primary FULL NAME of the street segment. (Source: TNRIS)

   A5_FULL_NA

   ALT. 5: Concatenated primary FULL NAME of the street segment. (Source: TNRIS)

   F_TYPE

   FEATURE TYPE (Source: TNRIS)

   RD_CLASS

   ROAD CLASS (Source: TNRIS)

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   Shape.len

   Length of feature in internal units. (Source: ESRI)

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • The data was created and provided by TeleAtlas North America through a StratMap contract.

2. Who also contributed to the data set?

3. To whom should users address questions about the data?
   Texas Natural Resources Information System: Stratmap
   

   512-463-8337 (voice)
   512-463-7274 (FAX)
   stratmap@tnris.state.tx.us
   

   Hours_of_Service: 8:00am to 5:00pm (M-F) CST

   Contact_Instructions: More information: www.tnris.state.tx.us

Why was the data set created?

The primary purpose of the StratMap Phase 2 Transportation Layer is for cartographic and basemap functionality. The layer remains in the public domain and serves as a seamless transportation layer for emergency response and recovery, site location, and general mapping.

How was the data set created?

1. From what previous works were the data drawn?

2. How were the data generated, processed, and modified?

   (process 1 of 1)

   Metadata imported.

   Data sources used in this process: M:\TNRIS-StratMap\TeleAtlas_TX\Metadata\TANA_metadata_FINAL.xml

   Data sources used in this process:

   • C:\DOCUME~1\adube\LOCALS~1\Temp\xml16D.tmp

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?

   Stratmap street segments allow for six implied decimal places of precision. While minimum accuracy is consistent with 1990 TIGER/Line(R) files, accuracy is dependent on geographic area and sources used to update those areas. Realignment priority was given to 8 counties (Coryell, Jim Hogg, Kendall, Nacogdoches, Panola, Starr, Tom Green, and Zapata).

   Tests are performed for invalid names, Feature Class Codes and characters. Tests are constantly running on the Tele Atlas(R) database to ensure segment topology meets Tele Atlas(R) specifications. The Streets layer is not generalized.

2. How accurate are the geographic locations?

3. How accurate are the heights or depths?

4. Where are the gaps in the data? What is missing?

   All street segments in the Tele Atlas(R) database with an FCC = A* are considered. A74 (driveways) and A75 (parking areas) are not selected. After processing, the dataset is checked for drawing display, correct number of records, record schema consistency with specifications, correct file naming, file sizes and a comparison check with the contents of the Tele Atlas(R) database at the time of creation.

5. How consistent are the relationships among the observations, including topology?

   Street data is crosschecked and verified using numerous independent mapping sources. More than 500 algorithmic QC checks are applied against the database to ensure that changes to geography and attribution conform to the Tele Atlas(R) internal Database Feature Modeling Specifications.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints:

The StratMap transportation layer is organized by county in both ESRI 9.x Personal GeoDatabase and Shapefile formats. The layer is available for free at www.tnris.state.tx.us, or can be purchased on CD. Contact TNRIS for more information.

Use_Constraints:

StratMap does not warrant this data for any particular use and is not responsible for any damages resulting from the use of the data. Users of the layer should be aware that (1) StratMap data are not authoritative representations of boundaries derived from transportation features, (2) StratMap transportation lines are subject to change and corrections, (3) StratMap transportation was generated from the best available data which is subject to change, and (4) StratMap is updating transportation data and has a process for collecting and noting transportation changes. Contact StratMap for more details. Acknowledgement of the StratMap program is appreciated in products derived and used from the data.

1. Who distributes the data set? (Distributor 1 of 1)
   Texas Natural Resources Information System: StratMap
   P.O. Box 13231
   Austin, TX 78711-3231
   USA
   

   512-463-8337 (voice)
   512-463-7274 (FAX)
   

   Hours_of_Service: 8:00am to 5:00pm (M-F) CST

   Contact_Instructions: More information: www.tnris.state.tx.us

2. What's the catalog number I need to order this data set?

   Downloadable Data

3. What legal disclaimers am I supposed to read?

   No warranty, expressed or implied, is made and no liability is assumed by TNRIS as to the positional or attribute accuracy of the data. The act of distribution shall not constitute any such warranty and no responsibility is assumed by TNRIS in the use of these files.

4. How can I download or order the data?
   • Cost to order the data:
   • Special instructions:

     StratMap data is downloadable, and is also avaible by CD. Contact TNRIS for details. Data is available at no charge online: www.tnris.state.tx.us

Who wrote the metadata?

Dates:

Last modified: 13-Aug-2007

Metadata author:

Texas Natural Resources Information System: StratMap
c/o REQUIRED: The person responsible for the metadata information.
REQUIRED: The city of the address., REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address.

512-469-8337 (voice)
512-463-7274 (FAX)
stratmap@tnris.state.tx.us

Hours_of_Service: 8:00am to 5:00pm (M-F) CST

Contact_Instructions: More information: www.tnris.state.tx.us

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:

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