Traffic Pole

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: District Department of Transportation
Publication_Date: 20110107
Title: Traffic Pole
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher: DDOT
Online_Linkage: \\GIS-COMPUTER\G\Deliverable\TOAAssetInventory.mdb
Larger_Work_Citation:
Citation_Information:
Originator: DC GIS
Title: DC Geographic Information System
Geospatial_Data_Presentation_Form: vector digital data
Description:
Abstract:
The dataset contains location and attributes of traffic controls features located at each intersection in the District of Columbia. All traffic poles, pavement markings, traffic cabinets and cameras located within 10 meters of curb face intersections are collected. Poles must support traffic control devices in order to be collected. This includes traffic control signs, traffic signals, traffic arms and cameras. These traffic contorl devices are part the data sets tables and are related to there particular pole. The data set does not include poles supporting only name plate signs and parking enforcement signs.
Purpose:
This data is used for the planning and management of traffic controls - Assets, Activities, Incidents, as well as the maintenance of Traffic Pole Features of the District of Columbia, Department of Transportation (DDOT).
Supplemental_Information:
This dataset is the point geometry that represents Traffic Poles.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 4/16/2009
Beginning_Time: unknown
Ending_Date: 11/23/2010
Currentness_Reference: ground condition
Status:
Progress: In work
Maintenance_and_Update_Frequency: Unknown
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.114312
East_Bounding_Coordinate: -76.909326
North_Bounding_Coordinate: 38.995147
South_Bounding_Coordinate: 38.815842
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: transportation
Theme_Keyword: traffic control
Theme_Keyword: pavement marking
Theme_Keyword: traffic cabinet
Theme_Keyword: camera
Theme_Keyword: traffic detector
Theme_Keyword: traffic pole
Theme_Keyword: push button
Theme_Keyword: signal
Theme_Keyword: signal arm
Theme_Keyword: Manual of Uniform Traffic Controls
Theme_Keyword: MUTCD
Theme_Keyword: Transportation Operation Agency
Theme_Keyword: TOA
Place:
Place_Keyword: Washington, D.C.
Place_Keyword: DCGIS
Place_Keyword: DC GIS
Place_Keyword: District of Columbia
Place_Keyword: DC
Stratum:
Stratum_Keyword: terrestrial
Access_Constraints:
Contact DDOT / OCTO GIS. Any data obtained outside of DDOT / OCTO GIS are unauthorized copies.
Use_Constraints:
Data cannot be redistributed in any manner without written authorization. DDOT-OSAT / OCTO makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Markos K. Yeterawork
Contact_Organization:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Contact_Position: Sr GIS Analyst, Spatial Data Systems
Contact_Voice_Telephone: (202) 741-5391
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: markos.yeterawork@dc.gov
Hours_of_Service: 8:30 am - 5 pm
Data_Set_Credit:
District of Columbia, Department of Transportation. Operational Support and Applied Technology (OSAT) - Spatial Data Systems.
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Mercado will achieve 95% attribute accuracy on a maximum 10% random sample in order for data to be deemed acceptable. Collected attributes will be evaluated against field conditions and the calculation of accuracy will be based on total countable collected attributes. TrafficPole attributes will be quality controlled to an accuracy of 95% based on each counted attribute receiving equal weight. Attributes collected are as follows:
PoleID SteetJunctionID StreetJunctionID StreetSegID PoleType PoleMaterial PoleHeight PoleCondition BaseType IsPower IsAPS NoOfHeads Picture
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: PoleID
Attribute_Accuracy_Explanation:
Traffic Poles (where applicable) in wards 1-8 are tagged with a unique PoleID. with the following formats:
Digits are sequential from 1 to 99999.
Logical_Consistency_Report:
Consistency of the data is manually checked by a GIS technician to test the accuracy of the data at the completion of each ward. For each PoleType there are typical attribute vallues. Mercado Consultants has developed a proccess for checking the logical consistency of the data. The select by attributes tool is used to select features whose attributes do not fall into typical values expected for a particular feature class. For example, PoleTypes labeled Streetlights typically have PoleHeights valued between 25' and 30'. Streetlights with PoleHeights with value greater the 30' or lesser then 25' are selected and checked against the pole's picture and adjecent poles.
See Process Description under the Process Step to understand how logical consistency is achieved for each Traffic Pole at each street intersection.
Completeness_Report:
Mercado Consultants, Inc. performed an inventory of traffic poles at each intersection within the District of Columbia. The inventory was conducted in all of the Washington DC. The TrafficPole inventory includes the following items:
The collection of assets' attribute information as described in the Attribute Accuracy section of the Data Quality tab.
The collection of sub-meter GPS on traffic controll assets as described in the Positional Accuracy section of the Data Quality tab.
A supplemental datat set indicates all StreetIntersectionIDs without assets and an explanation. This data set will provide a completeness report.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
All traffic control assets are inventoried and placed relative to DDOT's source road network. The location of assets are established by using three different methods:
1. First, a sub-meter gps point is taken for each traffic pole with the exclusion of underpasses and tunnels. Each sub-meter gps point is stored in Trimble formatted .SSF files. The .SSF files are differentially corrected and exported to the NAD83 Maryland State Planes Meter coordinate system using Trimble's GPS Pathfinder Office software program.
2. In areas where a good satelite signal could not be established, locations are established from the intersection of two radial measurements from known locations on the existing DC planametrics.
3. GPS position are also established by digitizing the locations using 2008 Orthophotos.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: N/A
Horizontal_Positional_Accuracy_Explanation: See accuracy report for explanation
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report: No elevation value was collected
Quantitative_Vertical_Positional_Accuracy_Assessment:
Vertical_Positional_Accuracy_Value: N/A
Vertical_Positional_Accuracy_Explanation: All vector positions are planar
Lineage:
Process_Step:
Process_Description:
Operating Procedures Safety At Mercado Consulting safety is very important. To this end, there will be a safety meeting every Monday to discuss safety issues that had arise during the previous week. It is required that every Mercado emloyee who goes out in the field wear a Safety Vest while working in the field. While out in the field we are a team. As such, we will look out for each coworker and warn them when they are performing an unsafe act. Driving To perform this survey, it is necessary to drive a company vehicle and sometimes it necessary to drive a privately owned vehicle. When driving a vehicle to perform this project it necessary to follow certain procedures. Mileage While driving a company vehicle or a privately owned vehicle it is important to document the miles driven for that day to perform work. If you are driving your own vehicle with proper permission you are authorized compensation for miles driven to perform the task for that day. Gas Print receipts when fueling company vehicles and return to project manager. Accident Report all accidents to the proper authorities. Metro Traffic tickets are not tolerated. Please pay attention to where you are parking when you are performing company business. If you park at a meter, please pay the amount needed to complete the job. You will be compensated for any money used to pay for metered parking and parking tickets. Metro At times when it is more convenient you may have to ride the Metro run by the Washington Metropolitan Association Transit Authority. In these times you will be handed a Smart trip Card to ride the metro and will be provided with money to reload this card if it is necessary. Team A team is usually 2 people: a Trimble Operator and a Rod Man. Remember you are team and act accordingly. We must look after each other when we are out in the field. Preparation for Work Before leaving the office, verify that you all of the equipment for work. This includes a Trimble Data Collector, Camera, Telescoping Rod, Clip Board, Barcodes, Barcode Scanner and Step Stool for each team. In the Clip Board, there should be enough work to complete a day's work. Everyone is required to have a safety vest and ID badge. Arrange Intersection Intersection should be arranged in a logical order prior to reaching the intersections being worked today. Order of Collecting Data You collect data by starting on the Northwest Corner (Corner 1. See field sheet) and work clockwise from there until the final piece of data is inputted. After data is collected, a video will be taken when necessary to get a view of the pavement markings. Numbering of Numbered Items Items that are number should follow that following numbering convention: odd numbers for the red Trimble and even numbers for the blue Trimble; for example the numbers should go from 3001-4000 and then 5001-6000 for the red Trimble while the blue Trimble would go from 4001-5000 and 6001-7000 respectively.
Responsibilities Trimble Operator The Trimble Operator is responsible for establish GPS position for each asset and filling out their corresponding attributes. Input Data in Trimble The main data of the Trimble Operator is to collect information on the Trimble data collector. The information that is collected except for pavement marking will be collected on the Trimble data collector. The information that will vary depending on the type of information collected. Set up Trimble Geo XT In order to use the Trimble, you must locate yourself on the map. In the Trimble, there is a GPS receiver. The GPS receiver generally works but there are limitations such as it takes up to 15 minutes for the receiver to locate you on the map. If possible, you should try to find your location on the map before you the receiver finds your location and confirm it when the receiver finds your location. Once the GPS receiver has found your position, you can use the GPS receiver to plot your point by placing the point on the brown "x" that represent you location or using the auto plot point feature which requires you to stand next to the feature that is being plotted until 20 satellite signals are received. Data Collections It is the responsibility for the Trimble Operator to input data for the following Traffic Controls: Pole, Sign, Signal, Signal Arm, Cabinet, Push Button, and Camera. Traffic Pole When inputting Poles the following data is needed: Pole ID, Pole Type, Pole Material, Base Type, Pole Height, Number of Heads, and Picture. Pole ID Pole ID is auto-incremented but in some cases these numbers will have to be manually inputted. Pole Type For Pole Types you are given a pull down menu that include the following choices: Sign Support, Street Light, Decorative, Signal, Combo, Utility and other. A full of the various pole types are given in glossary of terms. Pole Material For Pole Materials you are given a pull down menu that includes the following choices: Metal, Wood, Plastic, Aluminum, and Poly Tech. Generally pole materials are self explanatory. The only exceptions are Aluminum and Poly Tech. These poles look like metal poles but are not magnetic. You can check to see if you these poles are not metal by using the magnet at the end of the given tape measure. Base Type Base Type is either T-Base, Temporary or does not apply. T-Base or Temporary only applies to Street Light, Signal, and Combo Poles. All other poles does not apply is the appropriate input for Base Type. A description of Base Type is in the glossary of terms. Pole Height The pole height should be measured to nearest foot and inputted in at that amount. Number of Heads For Signal and Combo Poles it is necessary to apply the appropriate number of traffic signals that are on the particular pole. This also includes Decorative poles that have Traffic Signals as well.
Picture Picture ID is determined by the camera and entered into the data collector. Traffic Sign When inputting signs the following data is needed: Sign ID, Pole ID, Sign Category, Sign Name, Sign Dimension, Sign Height, and Pole Type. Sign ID Sign ID is auto-incremented but in some cases these numbers will have to be manually inputted. It is important that the Sign ID matches the end digits of the Barcode affixed to the sign. If it does not, the Sign ID needs to be changed to match the Barcode. Pole ID Pole ID should match the Pole ID of the pole the sign is affixed. Sign Category The sign categories are as follow: Regulatory, Stop/Prohibition, Pedestrian, Warning, School, and Guidance/Directional. Pick the appropriate category from the drop down menu. Sign Name Sign name are inputted as the code given to signs in the Manual on Uniform Traffic Devices (MUTCD). If the name is unknown, then leave the Sign Name blank. Sign Height The sign height should be measured to nearest tenth of foot and inputted in at that amount. If the Signal is affixed to a Signal Arm, the height of the Signal is the height of the Signal Arm. Pole Description Normally Pole Description is N/A except if it is a Sign Support. In the case of Sign Support, you will need to input Pole Description as U-Channel, Round, Square, or Impact Recovery Picture Picture ID is determined by the camera and entered into the data collector. Traffic Signals When inputting Signals the following data is needed: Signal ID, Pole ID, Signal Arm ID, Signal Type, Signal Height, and Number of Section. Signal ID Signal ID is auto-incremented but in some cases these numbers will have to be manually inputted. Pole ID Pole ID should match the Pole ID of the pole the signal is affixed. Signal Arm ID If the Signal is on a Signal Arm, input the appropriate Signal Arm. Signal Height The signal height should be measured to nearest tenth of foot and inputted in at that amount. Number of Sections Enter the number of section that the signal has. Traffic Signal Arms When inputting Signal Arms the following data is needed: Signal Arm ID, Pole ID, Signal Arm Length, Signal Arm Material, Signal Arm Height, and Number of Heads. Signal Arm ID Signal Arm ID is auto-incremented but in some cases these numbers will have to be manually inputted. Pole ID Pole ID should match the Pole ID of the pole the Signal Arm is affixed. Signal Arm Length Input the length the Signal Arm extends from the pole.
Signal Arm Material Input the material of the Signal Arm. Signal Height The Signal Arm height should be measured to nearest tenth of foot and inputted in at that amount. Number of Heads Input the number of Signals affixed to the Signal Arm. Traffic Push Buttons When inputting Push Buttons the following data is needed: Push Button ID, Push Button Height, and Pole ID. Push Button ID Push Button ID is auto-incremented but in some cases these numbers will have to be manually inputted. Push Button Height The Push Button height should be measured to nearest foot and inputted in at that amount. Pole ID Pole ID should match the Pole ID of the pole the Push Button is affixed.

Traffic Cameras When inputting Cameras the following data is needed: Camera ID, Pole ID, Camera Type, and Camera Owner. Camera ID Camera ID is auto-incremented but in some cases these numbers will have to be manually inputted. Pole ID Pole ID should match the Pole ID of the pole the Camera is affixed. Camera Type Choose from CCTV, Red Light and Speed. Camera Owner Choose from DDOT, DC Police and Secret Service. Traffic Cabinets When inputting Cabinets the following data is needed: Cabinet ID, and Cabinet Type. Cabinet ID Cabinet ID is auto-incremented but in some cases these numbers will have to be manually inputted. Cabinet Type Input the Cabinet Type: 336s, or 336ss. The difference between the two is the height. If the height of the Cabinet is taller than an average man's shoulder, then the type is 336ss; otherwise the type is 336s. Verify Barcode match signs. The Trimble Operator has to verify the barcode is at the bottom, left-hand corner and match the Sign ID in the Trimble. If the there is no Barcode on sign, alert the Rod Man. Assist the Rod man when necessary. If you finished your assigned duties, you should help the Rod Man where you can.
Rodman The Rod Man job is to collect the data that the Trimble Operator is inputting in the Data Collector. Measurements Measurements should be measured bottom for all data that is collected from the pole and should be written down on the pole or ground along with the pole ID. Pictures For every pole and sign that is entered into the data collector, there should be a picture. These pictures should be taken bottom to top within the minute of the pole picture being taken. Pole The pole picture should include everything that is on the pole such as base, picture, push button, camera and signs. After each pole picture, the picture time should be written down. Signs The sign picture should be taken of the sign. After the sign picture is taken, a barcode should be placed on the back of the sign in the lower left hand corner. Drawing Pavement Markings The pavement markings should be drawn as exactly seen on the ground on the orthographic sheet. It should be noted whether tape is showing or the color is other than white. Mark the tape lines as tape and lines that other than white as the color they are.(See field sheet) Drawing Poles Poles must be drawn on the data sheet where the pole is located noting the Pole ID. (See field sheet) Video When you take the video, you must video tape the worksheet first. After videotaping the worksheet, you go from corner to corner videotaping the pavement noting what corner you are on and the pavement markings you see. If you see taped lines, you must zoom into the line and mention that it is tape. Checking Numbers Check the numbers with the Trimble operator to make sure the numbers are correct. The numbers that are being checked are Pole ID, Sign ID, Signal ID, Arm ID, Push Button ID, Traffic Cabinet ID, and Camera ID. (See field sheet)
Process_Date: Unknown
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Ryan Spielman
Contact_Organization: Mercado Consultants
Contact_Position: Project Manager
Contact_Voice_Telephone: 301 260 0090
Contact_Facsimile_Telephone: 301 260 0018
Contact_Electronic_Mail_Address: rspielman@mercadoeng.com
Hours_of_Service: 8:00am to 5:00pm
Process_Step:
Process_Description:
Mercado developed a controlled QA/QC process that requires a GIS technician to manually check the accuracy of the data using Arc GIS software. The QA/QC process includes the following checklist:
Location of poles are accurate based on orthophotos and existing planametrics.
Each required attribute is correctly filled.
Each TrafficPole and TrafficSign feature is hyperlinked to a photo.
Each asset on the pole are correctly related to the pole based on the picture taken of the pole.
Source_Used_Citation_Abbreviation: C:\DOCUME~1\RSPIEL~1\LOCALS~1\Temp\xml979.tmp
Process_Date: 20100215
Process_Time: 21474000
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
\\DDOT-10TYGH1\M$\Projects\TOA Asset Inventory\Final Delivery\TOAAssetInventory.mdb
Process_Date: 20101223
Process_Time: 08373100
Cloud_Cover: Unknown

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity point
Point_and_Vector_Object_Count: 28219

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: State Plane Coordinate System 1983
State_Plane_Coordinate_System:
SPCS_Zone_Identifier: 1900
Lambert_Conformal_Conic:
Standard_Parallel: 38.300000
Standard_Parallel: 39.450000
Longitude_of_Central_Meridian: -77.000000
Latitude_of_Projection_Origin: 37.666667
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000000
Ordinate_Resolution: 0.000000
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: Traffic Pole
Entity_Type_Definition:
TrafficPole is the point geometry that represents DDOT traffic poles that support traffic control assets.
Entity_Type_Definition_Source: DDOTGIS
Attribute:
Attribute_Label: POLETYPE
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: ISPOWER
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: PICTURE
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: PoleID
Attribute_Definition: Unique traffic pole id
Attribute_Definition_Source: Mercado Consultants
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Whole number
Enumerated_Domain_Value_Definition:
Unique sequential number generated by Terrasync software on Trimble XT
Enumerated_Domain_Value_Definition_Source: Mercado Consultants
Attribute:
Attribute_Label: BaseType
Attribute_Definition: Pole Base Type
Attribute_Definition_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: TrafficPoleBaseType
Codeset_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute:
Attribute_Label: POLEHEIGHT
Attribute:
Attribute_Label: POLEID
Attribute:
Attribute_Label: IsPower
Attribute_Definition: Represents the availability of back up power for the pole.
Attribute_Definition_Source: Mercado Cosultants
Attribute_Domain_Values:
Unrepresentable_Domain: The existence of backup power varies for each pole
Attribute:
Attribute_Label: ISAPS
Attribute:
Attribute_Label: FacilityID
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: NOOFHEADS
Attribute:
Attribute_Label: FACILITYID
Attribute:
Attribute_Label: COMMENTS
Attribute:
Attribute_Label: PoleType
Attribute_Definition: Pole type
Attribute_Definition_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: PoleType
Codeset_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute:
Attribute_Label: IsAPS
Attribute_Definition: Determines the pole supporting audible push button signal
Attribute_Definition_Source: Mercado Consultants
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: BooleanValue
Codeset_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute:
Attribute_Label: BASETYPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: PoleHeight
Attribute_Definition: Height of pole to the nearest foot
Attribute_Definition_Source: Mercado Consultants
Attribute_Domain_Values:
Unrepresentable_Domain: The height of Pole varies for each pole.
Attribute:
Attribute_Label: NoOfHeads
Attribute_Definition: Number of Signal on Pole
Attribute_Definition_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: NoOfHeads
Codeset_Source:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Attribute:
Attribute_Label: Comments
Attribute_Definition: Field for additional information
Attribute_Definition_Source: Mercado Consultants
Attribute_Domain_Values:
Unrepresentable_Domain: Comments is determined by each pole
Attribute:
Attribute_Label: Picture
Attribute_Definition:
Picture is created based on each pole's PoleID attribute. Field calcutlator equals "PIC_PoleID"+Format([PoleID])+".JPG"
Attribute_Definition_Source: Mercado Consultants
Attribute_Domain_Values:
Unrepresentable_Domain: Picture is created based on each pole's PoleID attribute
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Detailed_Description:
Entity_Type:
Entity_Type_Label: TrafficPoleHasSignals
Entity_Type_Definition: TrafficPole supports a signal arm
Entity_Type_Definition_Source: DDOTGIS
Detailed_Description:
Entity_Type:
Entity_Type_Label: TrafficPoleHasPushButtons
Entity_Type_Definition: TrafficPoles supports signal push buttons
Entity_Type_Definition_Source: DDOTGIS
Detailed_Description:
Entity_Type:
Entity_Type_Label: TOA.TrafficPoleHasSigns
Entity_Type_Definition: TrafficPole supports traffic signs
Entity_Type_Definition_Source: DDOTGIS
Detailed_Description:
Entity_Type:
Entity_Type_Label: TrafficPoleHasSignalArms
Entity_Type_Definition: TrafficPole supports traffic signal arms
Entity_Type_Definition_Source: DDOTGIS

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
D.C. Department of Transportation. Operation Support and Applied Technology (OSAT) - Spatial Systems Division
Contact_Person: Markos K. Yeterawork
Contact_Position: Head, Spatial Systems Division
Contact_Voice_Telephone: (202) 671 2123
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: markos.yeterawork@dc.gov
Hours_of_Service: 8:30 am - 5 pm
Resource_Description: Downloadable Data
Distribution_Liability:
DDOT (OSAT) / OCTO makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred, with respect to the information or data furnished herein. Subject to terms and conditions of the Memorandum of Agreement. Memorandum of Agreement must have authorized signature.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.754
Ordering_Instructions: Contact DDOT/TSA
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown
Time_of_Day: unknown

Metadata_Reference_Information:
Metadata_Date: 20110210
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Markos K. Yeterawork
Contact_Organization:
DC Department of Transportation, Operational Support and Applied Technology (OSAT) - Spatial Data Systems Division
Contact_Position: Sr GIS Analyst, Spatial Data Systems
Contact_Address:
Address_Type:
REQUIRED: The mailing and/or physical address for the organization or individual.
City: REQUIRED: The city of the address.
State_or_Province: REQUIRED: The state or province of the address.
Postal_Code: REQUIRED: The ZIP or other postal code of the address.
Contact_Voice_Telephone: (202) 741-5391
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: markos.yeterawork@dc.gov
Hours_of_Service: 8:30 am - 5 pm
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.9.6 on Thu Feb 10 14:32:39 2011