Weigh-In-Motion Stations (WIMSite)

Data format: SDE Feature Class

File or table name: DCGIS.WIMSite

Coordinate system: State Plane Coordinate System 1983

Theme keywords: transportation, location, Station, Traffic Count, Traffic, Count, sensorCamera

Abstract: Weigh-In-Motion Stations. The dataset contains locations and attributes of weigh-in-motion stations, created as part of the District of Columbia, Department of Transportation (DDOT) Street Spatial Database (SSD). A database provided by the District of Columbia, Department of Transportation identified Weigh-In-Motion stations. All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

FGDC and ESRI Metadata:

Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.

Identification Information:


Citation:
Citation information:
Originators: DC, Department of Transportation. OSAT


Title:
Weigh-In-Motion Stations (WIMSite)
*File or table name: DCGIS.WIMSite


Publication date: 01/07/2005
Publication time: 07:00 am
*Geospatial data presentation form: vector digital data


Publication information:
Publication place: Washington, DC
Publisher: DDOT

Online linkage: http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=WIMSite&downloadTYPE=ESRI
Online linkage: http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=WIMSite&downloadTYPE=KMZ


Larger work citation:
Citation information:
Originators: DC GIS


Title:
DC Geographic Information System


Geospatial data presentation form: vector digital data


Description:
Abstract:
Weigh-In-Motion Stations. The dataset contains locations and attributes of weigh-in-motion stations, created as part of the District of Columbia, Department of Transportation (DDOT) Street Spatial Database (SSD).

A database provided by the District of Columbia, Department of Transportation identified Weigh-In-Motion stations.  

All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.

METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

Purpose:
This data is used for the planning and management of Traffic - Assets, Activities, Incidents,  as well as the maintenance of safety Features of the District of Columbia, Department of Transportation (DDOT).

Supplemental information:
This dataset is the point geometry that represents Weigh-In-Motion Stations

*Language of dataset: en


Time period of content:
Time period information:
Single date/time:
Calendar date: 10/10/2006
Time of day: 07:00 am

Currentness reference:
publication date

Status:
Progress: Complete
Maintenance and update frequency: As needed

Spatial domain:
Bounding coordinates:
*West bounding coordinate: -76.987086
*East bounding coordinate: -76.945534
*North bounding coordinate: 38.918340
*South bounding coordinate: 38.869830

Local bounding coordinates:
*Left bounding coordinate: 401120.716607
*Right bounding coordinate: 404723.371490
*Top bounding coordinate: 138941.298175
*Bottom bounding coordinate: 133557.605338

Data set G-polygon:
Data set G-polygon outer G-ring:
G-Ring point:

Keywords:
Theme:
Theme keywords: transportation, location, Station, Traffic Count, Traffic, Count, sensorCamera
Theme keyword thesaurus: none

Place:
Place keywords: Washington, D.C., District of Columbia, DC, DC GIS, DCGIS

Stratum:
Stratum keywords: terrestrial

Access constraints: Contact DDOT / OCTO GIS. Any data obtained outside of DDOT / OCTO GIS are unauthorized copies.
Use constraints:
Acknowledgment of the DC Geographic Information Systems Program (DC GIS).  The District of Columbia Government 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 address:
Address type: mailing and physical address
Address:
64 New York Ave NE
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: (202) 741-5391
Contact facsimile telephone: (202) 727-5660


Contact electronic mail address: markos.yeterawork@dc.gov
Contact electronic mail address: ali,fatah@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 dataset format: SDE Feature Class
*Native data set environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.2.5.1450


Back to Top
Data Quality Information:


Attribute accuracy:
Attribute accuracy report:
Data believed to be complete and accurate, subject to change.

Logical consistency report:
In process of validation by source and/or responsible agency.

Completeness report:
Data believed to be complete and accurate, subject to change.

Positional accuracy:
Horizontal positional accuracy:
Vertical positional accuracy:
Lineage:
Source information:
Source citation:
Citation information:
Process step:
Process description:
The District was flown over to capture aerial imagery at < 1 meter resolution. These aerial images were orthorectified.

Process date: 1999


Process contact:
Contact information:
Contact organization primary:
Contact organization: Earth Data Corporation

Contact address:

Process step:
Process description:
The aerial photos were vectorized to extract linear featutes such as street, alley and driveway centerlines and produce the planimetric maps of the City

Process date: 1999 - 2000


Process contact:
Contact information:
Contact person primary:
Contact organization: Earth Data Corporation

Process step:
Process description:
To create attributes for the vectors each geometry was linked to corresponding street segment records from the existing Street Inventory System (SIS).

Process date: 2000


Process contact:
Contact information:
Contact organization primary:
Contact organization: Dewberry and Davies

Process step:
Process description:
The planimetric data derived from the aerial photos and the attribute data extracted from the Street Inventory System (SIS) were subjected to quality checks and field verification.

Process date: 2000


Process contact:
Contact information:
Contact organization primary:
Contact organization: Dewberry and Davies / Michael Baker Corp

Process step:
Process description:
This process step was carried out to correct the direction of flow on street segments. This was done programmatically by the Senior GIS Analyst

Process date: 2001


Process contact:
Contact information:
Contact person primary:
Contact person: Makos Yeterawork
Contact organization: District of Columbia, Department of Transportation
Contact position: Senior GIS Analyst


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\Documents and Settings\Tosan\Desktop\MetadataII\AlleySegment.xml


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\Documents and Settings\Tosan\Desktop\MetadataII\ServiceSegment.xml


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\GeoImaging_TestMetadata\MetadataII\StreetSegment.xml


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\DOCUME~1\myeteraw\LOCALS~1\Temp\xml10D7.tmp


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
\\Gismaps\gis\Metadata\ReferenceFeatures\StreetSegment.xml


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\Documents and Settings\myeteraw\Desktop\pcs.xml


Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
Server=dcgiscentral.in.dc.gov; Service=5151; User=dcgis_user; Version=SDE.DEFAULT


Back to Top
Spatial Data Organization Information:


*Direct spatial reference method: Vector


Point and vector object information:
SDTS terms description:
*Name: DCGIS.WIMSite
*SDTS point and vector object type: Entity point
*Point and vector object count: 0

ESRI terms description:
*Name: DCGIS.WIMSite
*ESRI feature type: Simple
*ESRI feature geometry: Point
*ESRI topology: FALSE
*ESRI feature count: 0
*Spatial index: TRUE
*Linear referencing: FALSE


Back to Top
Spatial Reference Information:


Horizontal coordinate system definition:
Coordinate system name:
*Projected coordinate system name: NAD_1983_StatePlane_Maryland_FIPS_1900
*Geographic coordinate system name: GCS_North_American_1983

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.001000
*Ordinate resolution: 0.001000
*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

Back to Top
Entity and Attribute Information:


Detailed description:
*Name: DCGIS.WIMSite


Entity type:
*Entity type label: DCGIS.WIMSite
*Entity type type: Feature Class
*Entity type count: 0
Entity type definition:
Weigh-In-Motion Station is the point geometry that represents Weigh-in-motion locations
Entity type definition source:
District of Columbia, Department of Transportation

Attribute:
Attribute label: SHAPE
Attribute definition:
Feature geometry.
Attribute definition source:
ESRI

Attribute domain values:
Unrepresentable domain:
Coordinates defining the features.


Attribute:
Attribute label: Shape
Attribute definition:
Feature geometry
Attribute definition source:
ESRI

Attribute domain values:
Unrepresentable domain:
Coordinates defining the features.


Attribute:
Attribute label: OBJECTID
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: SITE
*Attribute alias: SITE
Attribute definition:
Site Description
Attribute definition source:
DDOT/TSA

*Attribute type: String
*Attribute width: 50
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: WIM_ID
*Attribute alias: WIM_ID
Attribute definition:
Weigh in motion ID
Attribute definition source:
DDOT/TSA

*Attribute type: Integer
*Attribute width: 4
*Attribute precision: 10
*Attribute scale: 0


Back to Top
Distribution Information:


Distributor:
Contact information:
Contact organization primary:
Contact person: Markos K. Yeterawork
Contact organization: D.C. Department of Transportation. Operation Support and Applied Technology (OSAT) - Spatial Systems Division
Contact position: Head, Spatial Systems Division


Contact address:
Address type: mailing and physical address
Address:
2000 14th Street NW, 5th Floor
City: Washington
State or province: DC
Postal code: 20009
Country: USA

Contact voice telephone: (202) 671 2123
Contact facsimile telephone: (202) 727-5660


Contact electronic mail address: ali.fatah@dc.gov


Hours of service: 8:30 am - 5 pm



Resource description: Offline Data


Distribution liability:
Acknowledgment of the DC Geographic Information Systems Program (DC GIS).  The District of Columbia Government 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.

Standard order process:
Digital form:
Digital transfer information:
Transfer size: 0.082

Digital transfer option:
Online option:
Computer contact information:
Network address:

Ordering instructions:
Contact DDOT/TSA


Available time period:
Time period information:
Single date/time:
Calendar date: unknown
Time of day: unknown

Back to Top
Metadata Reference Information:


*Metadata date: 20080502
Metadata review date: 10/10/2006


*Language of metadata: en


Metadata contact:
Contact information:
Contact organization primary:
Contact person: Markos Yeterawork
Contact organization: DDOT
Contact position: Sr. GIS Analyst


Contact address:
Address type: mailing and physical address
Address:
64 New York Ave, NE
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: (202) 741-5391


Contact electronic mail address: markos.yeterawork@dc.gov


Hours of service: 9:00 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

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

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

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

Back to Top
Geoprocessing History:


Process:
*Process name: Append_2
*Date: 20080123
*Time: 100205
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\Append
*Command issued: Append Export_Output "Database Connections\SSDPROD@gisdata as sde_ddot_editor.sde\SDE_DDOT_EDITOR.WIMSite" NO_TEST "SITE SITE true true false 50 Text 0 0 ,First,#,F:\MiscData\SISUpdate\LinearlyRefencedAssets.mdb\Export_Output,SITE,-1,-1;WIM_ID WIM_ID true true false 4 Long 0 10 ,First,#,F:\MiscData\SISUpdate\LinearlyRefencedAssets.mdb\Export_Output,WIM_ID,-1,-1" "Database Connections\SSDPROD@gisdata as sde_ddot_editor.sde\SDE_DDOT_EDITOR.WIMSite"


Process:
*Date: 20080428
*Time: 161113
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyFeatures
*Command issued: CopyFeatures "Database Connections\DDOT SSD PROD.sde\SDE_DDOT_EDITOR.WIMSite" V:\DataLoadApril\DDOT.mdb\Transportation\SDE_DDOT_EDITOR_WIMSite # 0 0 0


Process:
*Date: 20080502
*Time: 204246
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyFeatures
*Command issued: CopyFeatures E:\DataLoadApril\DDOT.mdb\Transportation\WIMSite "Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.WIMSite" DCGISDBP_S 1000 0 0


Process:
*Process name: AddGlobalIDs_5
*Date: 20090307
*Time: 015045
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\AddGlobalIDs
*Command issued: AddGlobalIDs 'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.AMPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.ASRPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.CellularAggCallSignPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.CellularPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.FMPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.LmBCastPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.LmCommPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.LmPrivatePt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.MdsItfsPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.MicrowavePt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.PagingPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.TVContourPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.TVDigitalPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.TVNtscPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.AcisaIntersection';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.AlleyMaintenance';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BicycleLane';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BrgPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BrgPoly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BRT';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BudgetLine';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BudgetPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CommuterBusLoc';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CompletedLine';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CompletedPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CurrentLine';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CurrentPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.DDOT_CBD';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Flexcar';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.HAR';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.ParkingMeter';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.PCStation';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.PDMS';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.POS_Supercans';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.PrimarySignedRoute';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.RapidBus';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.RPPBlocks';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SchoolCrossingGuard';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SecondarySignedRoute';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SignedBikeRoute';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SpecialtyLighting';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SpeedDetector';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetCar';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetCenterlineLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetLight';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetSegmentLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.TrafficCabinet';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.TrafficControlOfficer';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Trail';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Trails_NPS';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.TranspStudyArea';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.WIMSite';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Zipcar' 'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.AMPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.ASRPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.CellularAggCallSignPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.CellularPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.FMPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.LmBCastPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.LmCommPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.LmPrivatePt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.MdsItfsPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.MicrowavePt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.PagingPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.TVContourPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.TVDigitalPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Towers\DCGIS.TVNtscPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.AcisaIntersection';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.AlleyMaintenance';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BicycleLane';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BrgPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BrgPoly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BRT';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BudgetLine';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.BudgetPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CommuterBusLoc';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CompletedLine';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CompletedPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CurrentLine';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.CurrentPoint';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.DDOT_CBD';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Flexcar';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.HAR';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.ParkingMeter';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.PCStation';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.PDMS';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.POS_Supercans';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.PrimarySignedRoute';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.RapidBus';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.RPPBlocks';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SchoolCrossingGuard';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SecondarySignedRoute';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SignedBikeRoute';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SpecialtyLighting';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.SpeedDetector';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetCar';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetCenterlineLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetLight';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.StreetSegmentLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.TrafficCabinet';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.TrafficControlOfficer';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Trail';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Trails_NPS';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.TranspStudyArea';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.WIMSite';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Transportation\DCGIS.Zipcar'


Back to Top