cmta_stops

Metadata also available as

Frequently-anticipated questions:

What does this data set describe?

Title: cmta_stops
Abstract: Active Capital Metro transit stops.
  1. How should this data set be cited?

    Capital Metropolitan Transportation Authority, Unpublished Material, cmta_stops.

    Online Links:

    • \\cmtagis1\gis\Download_Folder\cmta_stops.shp

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -97.998776
    East_Bounding_Coordinate: -97.547759
    North_Bounding_Coordinate: 30.589487
    South_Bounding_Coordinate: 30.146068

  3. What does it look like?

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

    Calendar_Date: unknown
    Currentness_Reference: ground condition

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

      • Entity point (3097)

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

      The map projection used is Lambert Conformal Conic.

      Projection parameters:
      Standard_Parallel: 30.116667
      Standard_Parallel: 31.883333
      Longitude_of_Central_Meridian: -100.333333
      Latitude_of_Projection_Origin: 29.666667
      False_Easting: 2296583.333333
      False_Northing: 9842500.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000000
      Ordinates (y-coordinates) are specified to the nearest 0.000000
      Planar coordinates are specified in survey feet

      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?

    cmta_stops

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    ID
    Internal Scheduling ID

    STOPABBR
    Internal Scheduling ID

    STOPNAME
    Name of transit stop

    ONSTREET

    ATSTREET

    GIS_ID
    Internal GIS ID

    CORNER
    Location of stop in relation to nearest intersection

    ValueDefinition
    1Northwest corner
    2Northeast corner
    3Southeast corner
    4Southwest corner

    PLACEMENT
    Stop placement in relation to nearest intersection

    ValueDefinition
    FFar side of intersection
    NNearside of intersection
    MMid-block

    BAY
    Bay assignment for park & ride / transit center

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    FACILITY_T
    Facility type

    ValueDefinition
    Transit Stop 
    Park and Ride 
    Transit Center 

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?

  3. To whom should users address questions about the data?

    Capital Metropolitan Transportation Authority
    c/o Van Sutherland
    GIS Coordinator
    2910 E. 5th St
    Austin, TX 78702
    USA

    512.369-6296 (voice)
    van.sutherland@capmetro.org

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?

    (process 1 of 1)
    Dataset copied.

    Data sources used in this process:

    • Server=cmtagis1_sqlexpress; Service=sde:sqlserver:cmtagis1\sqlexpress; Database=CMTS; Version=dbo.DEFAULT

  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 observations, including topology?

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:
Capital Metro specifically disclaims any and all liability for any claims or damages that may result from use of this data.

  1. Who distributes the data set? (Distributor 1 of 1)

    Capital Metropolitan Transportation Authority
    c/o Van Sutherland
    GIS Coordinator
    2910 E. 5th St
    Austin, TX 78702
    USA

    512.369.6296 (voice)
    van.sutherland@capmetro.org

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    Capital Metro specifically disclaims any and all liability for any claims or damages that may result from use of this data.

  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 13-Aug-2007
Metadata author:
Van Sutherland
Capital Metropolitan Transportation Authority
GIS Coordinator
2910 E. 5th St
Austin, TX 78702
USA

512.369.6296 (voice)
van.sutherland@capmetro.org

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used: