TPD.TrafficSignals

Frequently-asked questions:


What does this data set describe?

Title:
TPD.TrafficSignals

Abstract:
Traffic signal locations in Broward County, Florida.

Supplemental information:
Full-color signals only.  Does not include fire house signals, preempters, post or span beacons, U-turn signals, and  pedestrian signals.

  1. How should this data set be cited?

    Broward Metropolitan Planning Organization, 20080731, TPD.TrafficSignals: 21 , Broward County, Broward County, Florida.

    Online links:
  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -80.434497
    East: -80.077718
    North: 26.327271
    South: 25.958575

  3. What does it look like?

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

    Calendar date: 20080731
    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):
      • Entity point (1225)

    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.000256.
      Ordinates (y-coordinates) are specified to the nearest 0.000256.
      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: 1.000000
      Altitude encoding method: Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    TPD.TrafficSignals
    OBJECTID
    Internal feature number.
    (Source:
    ESRI
    )

    Sequential unique whole numbers that are automatically generated.

    ID
    Unique Id of the traffic signal used by the Broward MPO

    Value Definition
    some examples of the ids are: A347, A 45, A 7,B238, B 56, B 1,C124, C 78, C 3
    The characters A, B, and C indicate the locations of the signals as North Broward, Central Broward, or South Broward, respectively.

    EW_STREET
    Name of the east/west street at the signalized intersection

    NS_STREET
    Name of the north/south street at the signalized intersection

    CITY
    Name of the city where the signal is located

    MEMO_DATE
    Date of the BILLING ADJUSTMENT letter of the signal, only signals added since the creation of this coverage have values in memo_date.The memo dates are not the installation dates of the signals which are usually later.

    TMC
    value 'Y' indicates turning movement counts are available for this location

    SHAPE
    Feature geometry.
    (Source:
    ESRI
    )

    Coordinates defining the features.

    TE_SYSTEMNUMBER
    Unique Signal IDs used by Broward County Traffic Engineering Systems Group

    TE_FILE_NO
    Unique Signal IDs used by Broward County Traffic Engineering Division

    FPL_GRID
    Florida Power and Light grid number

Back to Top

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?

    The traffic signal locations were provided by Broward County Traffic Engineering Division

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

    Lina Kulikowski
    Broward Metropolitan Planning Organization
    Principal Planner
    115 S. Andrews Ave.
    Fort Lauderdale, Florida 33301

    954-357-6610 (voice)
    954-357-6228 (FAX)
    lkulikowski@broward.org
    Hours of Service: Monday - Friday 8:30 a.m. - 5:00 p.m. EST
Back to Top

Why was the data set created?

This coverage was created in 1994 to be used in traffic analyses of the Broward County Congestion Management System.  In addition to its use in the Congestion Management System analyses, maps of  the traffic signals have been prepared in response to general public's requests.
Maps of the traffic signals are also used by the County's staff including signal design engineers and transportation engineers/planners.

Back to Top

How was the data set created?

  1. Where did the data come from?

    (source 1 of 4)

    Broward County Traffic Engineering Division, Keith Smith (954-847-2741), 1994, Traffic Signal History Files.

    Other citation details:
    Report in ASCII format used to create the original coverage

    Source contribution:
    used to create the original coverage

    (source 2 of 4)

    Broward County Traffic Engineering Division, Keith Smith, 1994 to current, BILLING ADJUSTMENTS letters to FPL.

    Other citation details:
    e-mail notifications

    Source contribution:
    used to update the coverage

    (source 3 of 4)

    Broward County Traffic Engineering Division, Keith Smith (954-484-9600 ext 227), July 1997, Traffic Signal Inventory Database (energy.dbf).

    Source contribution:
    used to quality check the coverage

    (source 4 of 4)

    Broward County Traffic Engineering Division, Keith Smith, Florida Powere and Light grid numbers, 20060515, Florida Power and Light Grid Numbers.

    Other citation details:
    data provided in an Excel spreadsheet: GridNumberAlpha.xls

    Source contribution:
    used to create the FPL_grid attribute field

  2. What changes have been made?

    (change 1 of 4)
    This coverage was originally generated through address matching using the GIS coverage 'STREETS.'  Signals rejected during the address matching process were manually digitized.  Subsequent updates to the coverage were done by  manual digitization.

    (change 2 of 4)
    The FPL_grid attribute was added in June 2006 to assist in power restoration effors.

    Data sources used in this process:
    • D:\My Documents\temp\TPD.xml

    (change 3 of 4)
    The TE_SYSTEMNUMBER attribute was added in April 2007 per request from Traffic Engineering Division.

    (change 4 of 4)
    Dataset copied.

    Data sources used in this process:
    • Server=gisora01; Service=5152; User=tpd; Version=SDE.DEFAULT

Back to Top

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?

Back to Top

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

Distributor 1 of 1

  1. Who distributes the data set?

  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?

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20080801

Metadata author:
Lina Kulikowski
Broward Metropolitan Planning Organization
Principal Planner
115 S. Andrews Ave.
Fort Lauderdale, Florida 33301
USA

954-357-6610 (voice)
954-357-6228 (FAX)
lkulikowski@broward.org
Hours of Service: Monday - Friday 8:30 a.m. - 5:00 p.m. EST

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

Metadata extensions used:
  • http://www.esri.com/metadata/esriprof80.html

  • Back to Top