TrafficAnalysisZones

Metadata also available as

Frequently-anticipated questions:

What does this data set describe?

Title: TrafficAnalysisZones
Abstract: Traffic Analysis Zones boundaries in Broward County, Florida.
  1. How should this data set be cited?

    Broward Metropolitan Planning Organization, May 2010, TrafficAnalysisZones.

    Online Links:

    • \\gisgc05\workspace\transpln\Projects\TAZ2010\geodata\TAZ2010.mdb

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -80.450972
    East_Bounding_Coordinate: -80.074345
    North_Bounding_Coordinate: 26.356192
    South_Bounding_Coordinate: 25.955038

  3. What does it look like?

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

    Calendar_Date: May 2010
    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):

      • G-polygon (922)

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

      The map projection used is Transverse Mercator.

      Projection parameters:
      Scale_Factor_at_Central_Meridian: 0.999941
      Longitude_of_Central_Meridian: -81.000000
      Latitude_of_Projection_Origin: 24.333333
      False_Easting: 656166.666667
      False_Northing: 0.000000

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

      The horizontal datum used is D_North_American_1983_HARN.
      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: 0.000010
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    TrafficAnalysisZones

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    SHAPE
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    TAZID
    Traffic Analysis Zone number

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

    Positive real numbers that are automatically generated.

    SHAPE_Area
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    CensusTract2000
    Year 2000 Census Tract where the TAZ is located.

    Region
    TAZs were divided into regions using planning districts. How the planning districts were defined was unknown.

    Region2
    TAZs were divided into region2 using freeways as dividing lines.

    Superzone
    TAZs were divided into super zones to facilitate the preparation of aggregated statistics.

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?

    Broward Metropolitan Planning Organization
    c/o Ricardo Gutierrez
    Associate Planner
    115 S. Andrews Ave.
    Fort Lauderdale, Florida 33301
    USA

    954-357-8665 (voice)
    rgutierrez@broward.org

Why was the data set created?

Traffic Analysis Zones are required for long-range transportation modeling purposes. Demographic, socio- economic, and other information can be summarized by TAZs. This information can then be used in transportation forecast models (i.e., FSUTMS) for trip generation and distribution.

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 3)
    This coverage was created based on the TAZ2000. Some zones were merged, split, or re-aligned to reflect the development changes in February 2007. Modifications prepared by A. Gray of Broward Metropolitan Planning Organization.

    (process 2 of 3)
    Attribute fields such as region, region_2, censustract2000, and superzones were prepared by L. Kulikowski of Broward Metropolitan Planning Organization.

    (process 3 of 3)
    TAZ 922 was added and included in superzone 4 (MAY 2010) by Ricardo Gutierrez

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

  1. Who distributes the data set?[Distributor contact information not provided.]

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 20-May-2010
Metadata author:
Broward Metropolitan Planning Organization
c/o Ricardo Gutierrez
Associate Planner
115 S. Andrews Ave.
Fort Lauderdale, Florida 33301
USA

954-357-8665 (voice)
954-357-6228 (FAX)
rgutierrez@broward.org

Hours_of_Service: 8:30 a.m. through 5:00 p.m. EST
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:

Generated by mp version 2.9.6 on Thu May 20 11:30:13 2010