Other traffic signs (OtherTrfPt)

Data format: SDE Feature Class

File or table name: DCGIS.OtherTrfPt

Coordinate system: State Plane Coordinate System

Theme keywords: structure, Planimetrics, Geographic Information System, transportation, signalSign

Abstract: Other traffic signs. Contract NCPC 93-02. This document describes the planimetric map production for the 350 tiles located in Washington DC and the surrounding states of MD and VA.

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: National Capital Planning Commission, Department of Public Works, Office of the Chief Technology Officer


Title:
Other traffic signs (OtherTrfPt)
*File or table name: DCGIS.OtherTrfPt


Publication date: 20020610
Edition: 1st edition
*Geospatial data presentation form: vector digital data


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

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


Description:
Abstract:
Other traffic signs. Contract NCPC 93-02.  This document describes the planimetric map production for the 350 tiles located in Washington DC and the surrounding states of MD and VA.

Purpose:
This data set was created to act as a basis for public and private institutions to improve their policy and decision making; promote economic development; and enhance the quality of life for residents and businesses.

*Language of dataset: en


Time period of content:
Time period information:
Single date/time:
Calendar date: 1999

Currentness reference:
ground condition

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

Spatial domain:
Bounding coordinates:
*West bounding coordinate: -77.116763
*East bounding coordinate: -76.910538
*North bounding coordinate: 38.994409
*South bounding coordinate: 38.804834

Local bounding coordinates:
*Left bounding coordinate: 389884.920500
*Right bounding coordinate: 407749.980500
*Top bounding coordinate: 147385.530000
*Bottom bounding coordinate: 126347.690000

Keywords:
Theme:
Theme keywords: structure, Planimetrics, Geographic Information System, transportation, signalSign
Theme keyword thesaurus: None

Place:
Place keywords: Washington, DC, District of Columbia
Place keyword thesaurus: None

Access constraints: Contact OCTO GIS. Any data obtained outside of 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 organization primary:
Contact person: GIS Data Coordinator
Contact organization: DC Office of the Chief Technology Officer (OCTO)

Contact address:
Address type: mailing and physical address
Address:
441 4th St NW, Suite 930 South
City: Washington
State or province: DC
Postal code: 20001
Country: USA

Contact facsimile telephone: (202) 727-5660


Contact electronic mail address: dcgis@dc.gov


Hours of service: 8:30 am - 5:00 pm



*Native dataset format: SDE Feature Class
*Native data set environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350


Back to Top
Data Quality Information:


Attribute accuracy:
Attribute accuracy report:
Validated by source and/or responsible agency. Attribute accuracy is tested by manual comparison of the digital orthos/aerial photography with the hard copy plots.  In addition, several computer quality control programs are run on the accompanying digital data.

Logical consistency report:
Validated by source and/or responsible agency.



Edit/Quality Control Process in ARC/INFO

The final topological structure is created and verified using ARC/INFO's Map Librarian functionality.  In general, use of a map library ensures overall compliance with defined database structures and conventions, and, for this specific project, guarantees adherence to the database structure and conventions.  In addition, in-house-developed ARC/INFO routines are employed for translation of vector data from a CAD to GIS environment.  These routines maintain coding of all CAD data, construct both topologically clean and topologically structured data sets, and combine or separate data into the correct user-defined output data sets.  For this project, for example, all CAD data are translated to ARC/INFO coverages while eliminating topological errors such as overshoots and undershoots.  EDMD GIS division verifies that all vector data produced for the project meets the Graphic Data Standards, as outlined in the modification of Task 4.  



A combination of automated procedures and interactive processes are used. The following is a listing of AML Default Routines:

QC_PROC.aml
This routine will run all of the following AMLs.  The &run qc_proc.aml <library> <tile> <layer> 

<library> - The name of the map library (i.e. NCPC) 

<tile> - the tile within the map library upon which the AMLs are to run

<layer> - the layer defined for the map library (i.e. roads)



General Data Set Verification

QC_DATAPROJ.aml
This routine checks correctness of all projection parameters.  It verifies map projection, projection zone, datum and projection units.

QC_DATAEXT.aml
This routine checks if all data in the selected data set are within the corresponding map sheet boundaries.

QC_CORN.aml
This routine checks if corner coordinates of the selected data set coincide with corner coordinates of the corresponding map sheet.

QC_DATATOL.aml
This routine checks mapping tolerances.  Mapping tolerances implicitly define accuracy and precision of vector data.



Attribute Verification

QC_FEATNODE.aml, QC_FEATPNTS.aml, QC_FEATLINE.aml, QC_FEATPOLY.aml
These routines check the field definitions of the selected data set and data type.

QC_ATTRPNTS.aml, QC_ATTRLINE.aml, QC_ATTRPOLY.aml
These routines check the attribute codes of all features in the selected data set against the range of possible attribute codes defined in the database.



Topological Consistency Verification

QC_DATAEDGE.aml
This routine checks for spatial mismatches of linear features among adjacent map sheets.  It displays any mismatch.

QC_ATTREDGE.aml
This routine checks for attribute mismatches of polygon features among adjacent map sheets.

QC_DANGINT.aml
This routine displays intersections of features within a data set such as contour data.  Intersections of contour features indicate errors as contours are by definition non-intersecting isometric.  This routine also displays any terminal node that is not connected to any other feature.  



The following is a description of the steps undertaken to inspect and verify the quality of the planimetric data.

Step 1	EDMD prepares an ARC/INFO map library using the database design as developed by Dewberry & Davis dated June 30, 1997.  Using an ARC/INFO map library, any inconsistencies in the database are immediately apparent when loading or modifying the digital planimetric data.

Step 2	Compiled data are translated to the appropriate ARC/INFO coverages and inserted into the map library.  The translation procedures ensure that all codes are within the range of possible domain values.  Illogical coding or configuration of features such as roads within buildings is immediately flagged.

Step 3	Using the Map Librarian functionality, routines (i.e., Arc Macro Language - AML) can be automatically applied to the entire database using the Map Librarian VISIT command.  Similarly, other layers are validated with the appropriate routines.

Step 4	In an interactive session, using ARC/EDIT, each map library tile, including all the associated layers, is verified by an editor.  Verification consists of checking spatial and attribute data.  In this session, topological inconsistencies are highlighted, for example, dangling arcs, missing label points, etc.  Identification of missing features or features with incorrect shape can also easily be identified through use of the 1995 orthophotos that reside in the image catalog.

Step 5	Final quality control is performed in an ArcView session, again using the map library.  Any missing features will be identified during this step. 

Generally, steps 1, 4, and 5 involve interactive quality control steps, while steps 2 and 3 are based on automated quality assurance.  Step 5, as a final quality control step, includes verification of vector data to hardcopy maps.

Completeness report:
Validated by source and/or responsible agency. The photogrammetric mapping is guaranteed to meet National Map Accuracy standards for digital mapping at a scale of 1 inch to 83.33 feet, which calls for 90% of well defined points to fall within 33.3 inches of true position horizontally. This does not apply to hidden features, which were inferred.

Positional accuracy:
Horizontal positional accuracy:
Horizontal positional accuracy report:
Validated by source and/or responsible agency. The horizontal accuracy is guaranteed to meet National Map Accuracy standards which calls for 90% of well defined points to fall within .85 meters of true position. This accuracy was verified by the completion of a fully analytical aerotriangulation adustment which resulted in an RMSE of 1 part in 10,000 which is recognized as necessary to achieve the accuracy requirement.

Vertical positional accuracy:
Vertical positional accuracy report:
Validated by source and/or responsible agency. The vertical accuracy of the topographic information is guaranteed to meet National Map Accuracy standards which calls for 90% of well defined points to fall within one half (.50 meters)  of true position. This accuracy was verified by the completion of a fully analytical aerotriangulation adustment which resulted in an RMSE of 1 part in 9,000 which is recognized as necessary to achieve the accuracy requirement.

Lineage:
Process step:
Process description:
EDMD transferred control points, pass and tie points from
the 1995 analytical aerotriangulation solution.  Control was
transferred from 1995 working diapositives to diapositives
of the new photography.  Control points were transferred
optically using a Wild PUG 4-point transfer device
equipped with a 60-micron drill.

Process date: Unknown


Source produced citation abbreviation:
EDMD1


Process contact:
Contact information:
Contact organization primary:
Contact person: Chris Barnard
Contact organization: EarthData International
Contact position: Project Manager


Contact address:
Address type: mailing and physical address
Address:
45 W. Watkins Mill Road Suite G
City: Gaithersburg
State or province: MD
Postal code: 20878
Country: USA

Contact facsimile telephone: 301.963.2064


Contact electronic mail address: cbarnard@earthdata.com


Hours of service: Regular office hours



Process step:
Process description:
EDMD acquired new aerial photography of the District of
Columbia in the spring of 1999 prior to the emergence of
deciduous foliage.  Aerial photography was exposed at an
altitude of 7,200' AMT using a Wild RC-20 or RC-30
camera system that is equipped with forward motion
compensation and a 12" (300mm) focal length lens cone
600'.  The
flight design developed in 1995 was duplicated.  The
design calls for an approximate total of 1,000 frames in 24
North-South oriented flight lines.  Forward overlap between
frames within each flight line was 80%.  Sidelap between
adjacent flight lines was 48%.  Aerial photography
was captured in natural color using Kodak Aerocolor
negative film type 2445.  Aerial photography was not
exposed using airborne GPS due to the existence of an
existing control network created in 1995.

Process date: Unknown


Source produced citation abbreviation:
EDMD2


Process contact:
Contact information:
Contact organization primary:
Contact person: Chris Barnard
Contact organization: EarthData International
Contact position: Project Manager


Contact address:
Address type: mailing and physical address
Address:
45 W. Watkins Mill Road Suite G
City: Gaithersburg
State or province: MD
Postal code: 20878
Country: USA

Contact facsimile telephone: 301.963.2064


Contact electronic mail address: cbarnard@earthdata.com


Hours of service: Regular office hours



Process step:
Process description:
EDMD produced 2 full sets of contact prints.  The prints
were separated into a total of 4 sets of prints, 2 sets of
even frames and 2 sets of odd frames.  Three of these sets
were delivered to NCPC for distribution to the District.  One
set was held by EDMD for reference purposes.  The
project manager determined if an odd or even set was
withheld for work purposes.
The planimetric mapping was developed using a set of
stable base color film diapositives that are created from the
1999 photography.
EDMD produced a flight line index of the completed
photography.  The positions of the photographs as
recorded by the ASCOT navigation/control system was
plotted over an existing raster or vector map of the District
of Columbia.  EDMD delivered 3 plots of the completed
index to NCPC.

Process date: Unknown


Source used citation abbreviation:
EDMD2
Source produced citation abbreviation:
EDMD3


Process contact:
Contact information:
Contact organization primary:
Contact person: Chris Barnard
Contact organization: EarthData International
Contact position: Project Manager


Contact address:
Address type: mailing and physical address
Address:
45 W. Watkins Mill Road Suite G
City: Gaithersburg
State or province: MD
Postal code: 20878
Country: USA

Contact facsimile telephone: 301.963.2064


Contact electronic mail address: cbarnard@earthdata.com


Hours of service: Regular office hours



Process step:
Process description:
Planimetric Data Capture and Edit
The following is a step-by-step description of the steps
involved in the collection of planimetric features from the
aerial photography.
Step 1	Planimetric data is captured within each flightline
proceeding in an North-South or South-North progression.
The diapositives and contact prints for each of the priority
production areas are assigned to photogrammetric
technician for data collection.  All planimetric data is
collected using Wild BC-2 first order analytical
stereoplotting systems.
Step 2	The photogrammetric supervisor establishes the
data collection conventions to be used for data capture.
All planimetric data is initially collected in the Microstation
environment.  The photogrammetric supervisor establishes
data collection conventions and establishes the
data-layering schema, global origin and working units to be
used for data collection.  These preferences are
programmed into Microstation to ensure continuity.
Step 3	Planimetric data is collected and saved to the
designated network subdirectory.  As data is collected, the
technician reviews the planimetric information on the
stereoplotter monitor to ensure that collection is complete
and that the required features are depicted and assigned
to the correct layer in the CAD design file.
EDMD has developed an in-house CAD application to
prepare the planimetric features for conversion to polygons
once the data has been migrated into ARC/INFO.  The
technician collects planimetric features in a clockwise
direction, which create centroids at the completion of each
line.  Each of these centroids delineates the outer
boundary of a polygon.  In areas where a line creates a
boundary for multiple features (edge of pavement, edge of
parking lot, edge of parking lot-edge of building), the line
segment is duplicated and assigned to all layers of the file
that contain the effected features.
Step 4	The photogrammetric technician completes
information for inclusion in the metadata.
Step 5	As stereo models are completed on the analytical
stereoplotter, the cartographic editor copies a number of
files pertaining to a block of map coverage and merges the
data sets into map-sheet-oriented format.  The merged data
is inspected for compliance with the database design.
Criteria for inspection include correct layer assignment, line
color, and line style.
The CAD application has incorporated quality control
functions, which add temporary symbols to indicate the
necessary duplication of line segments to complete
polygon closure in all affected features.  The editor makes
any corrections or additions interactively.  If necessary,
lines are snapped to ensure closure.
Step 5A	The cartographic editor translates the
ARC/INFO coverages of the existing planimetric data that
was produced as part of Task 2 and the State Department
modification into a CAD readable format.  The line work
between the new mapping and existing mapping is
tied together to ensure compliance with the contract
requirements for topology.
Step 6	As coverage areas are completed; the editor
informs the ARC/INFO supervisor that data is ready for
conversion and final quality control.  The completed vector
files are copied to a designated network subdirectory.
In order to avoid the possibility that incomplete or unedited
data sets are mistakenly imported during production, a
separate network subdirectory is used for the data at each
stage in the production process.  The network subdirectory
structure is standardized for every project.
Step 7	Edited data sets are translated into ARC/INFO
and polygon topology is created.  The process used to
create the final ARC/INFO coverages is described in the
Attribute Accuracy Report Section.
Step 8	The cartographic technician records any
pertinent dates or other information for completion of
metadata.
Plots
EDMD developed an ARC/INFO AML to generate hard
copy plots of the 1995 digital orthophotos as part of Task
3.  This routine will be modified to accommodate plotting of
the planimetric and/or topographic data.  The format will
retain the graphic design that was developed in 1999.
Design elements of the format and surround as well as the
planimetric/topographic mapping will be fully compliant with
the requirements stated in the contract modification.
Upon completion of the initial editing and conversion of the
data to ARC/INFO, EDMD will prepare a set of bond paper
plots.  Polygon features will be color coded for cartographic
clarity and will enable NCPC quality inspectors to verify that
no polygons overlap or are miscoded.  A copy of the digital
data that corresponds to the plots will be included to allow
inspectors to review digital data content.
NCPC will inspect the plots and mark any errors, omissions
or mistakes on the plots.  The edited plots are returned to
EDMD for correction.  Once the data has been corrected,
EDMD will produce a total of 3 sets of inkjet mylar plots
containing the planimetric data only in the approved format
surround.

Process date: Unknown


Source used citation abbreviation:
EDMD1
Source used citation abbreviation:
EDMD2
Source used citation abbreviation:
EDMD3


Process contact:
Contact information:
Contact organization primary:
Contact person: Chris Barnard
Contact organization: EarthData International
Contact position: Project Manager


Contact address:
Address type: mailing and physical address
Address:
45 W. Watkins Mill Road Suite G
City: Gaithersburg
State or province: MD
Postal code: 20878
Country: USA

Contact facsimile telephone: 301.963.2064


Contact electronic mail address: cbarnard@earthdata.com


Hours of service: Regular office hours



Process step:
Process description:
SIS Automation
EDMD will submit a copy of the edited planimetric data to
Dewberry & Davis for the automation of the street inventory
system.  It is anticipated that there will be a delay of 4
weeks between the completion of planimetric mapping and
completion of the corresponding SIS database.  The
following is a description of the process that will be used to
Step 1	EDMD, D&D, NCPC and designated
representatives of DC DPW will meet to accomplish the
--Presentation of the listing of government furnished material that are needed by D&D
--Set up conventions for creation of intersection nodes
--Set up conventions for attribution
--Set up conventions for reporting of omissions, errors or other QC issues in the SIS data to DC DPW and NCPC
These conventions will be tested and validated during the
pilot project.
Step 2 	For each contiguous block of centerlines, D&D
will extend curb lines through street intersections and
generate intersection nodes consistent with DPW
guidance established in step 1.
Step 3	Where two or more nodes are present that
comprise a single intersection (e.g., two multi-street
centerlines that intersect with four nodes), D&D will cluster
those nodes and identify an intersection centroid for linking
SIS files of street names, address ranges, etc.
Step 4	D&D will overlay the SIS files and conflate them
to match the centerlines, nodes, and multi-node centroids.
Because of anticipated SIS shortcomings, such as
identified in D&D's Washington GIS, Pilot Project Final
Report, dated June 30, 1997, this conflation will normally
be performed manually.
Step 5	D&D will overlay the georeferenced SIS files
over 1995 digital orthophotos and copies of the 1999
planimetric mapping provided by EDI to ensure that the
new SIS files satisfy positional accuracy requirements.
Step 6	D&D will deliver one set of ARC/INFO export
files (.e00) on CD-ROM to NCPC and will conduct a
demonstration, on DPW equipment (PC ArcView), that the
current INFO attributes work with the revised street
centerline file coverage.
Step 7	D&D will conduct on-site field verification surveys
(1)
direction (2) street name, (3) address ranges for each street
segment between cross-streets, (4) number of
lanes, (5) directionality of lane, and (6) lane usage.
Step 8	Addition of streets not digitized by EDMD.
Step 9	Correction of address ranges where streets are
bisected by added streets.
Step 10	Correction of other SIS data errors observable
from "windshield surveys."
Step 11	Provision of discrepancy lists, to NCPC, where
SIS street names differ from those posted on street signs.
D&D will not change the SIS files to match street signs that
are verified in the field.

Process date: Unknown


Source used citation abbreviation:
EDMD3
Source produced citation abbreviation:
DD1


Process contact:
Contact information:
Contact organization primary:
Contact person: Chris Barnard
Contact organization: EarthData International
Contact position: Project Manager


Contact address:
Address type: mailing and physical address
Address:
45 W. Watkins Mill Road Suite G
City: Gaithersburg
State or province: MD
Postal code: 20878
Country: USA

Contact facsimile telephone: (301) 963-2064


Contact electronic mail address: cbarnard@earthdata.com


Hours of service: Regular office hours



Process step:
Process description:
Extracted from Librarian using Simple option into coverage, then imported to geodatabase. Removed all voids and empty polygons from shape. The NCPC ArcInfo Librarian dataset is made up of 350 tiles.  Over 29 data layers were extracted from the Librarian using the following procedures (see planimetric process.xls).

1) In order to withdraw seamless data out of Librarian an extraction polygon must be created.  The extraction polygon must encompass the span of all the tiles.  Extracting the index layer of the librarian and dissolving the boundaries of the 350 polygons into 1 polygon accomplished this task.

The procedures for creating the extraction polygon are as follows:
?	Extract the index layer using Arcview and converting the theme into a shapefile.
?	Create a field within the feature table for which the individual polygon can dissolve from by assigning a value of 1 in it for all records.
?	Using the geo-processor extension option, the shapefiles' records were dissolved into 1 poly by dissolving the records with the common field.
?	The polygon theme was then transformed into a polygon coverage through ArcToolbox.
?	Once the extraction polygon was prepped, data layer extraction was completely done in the ArcInfo environment.

Setting the ArcInfo Environment.
1)	Launch the ArcInfo Command Prompt window.
2)	Set the working directory ( arc:  w d:\workspace\extraction)
3)	Set the precision for the environment and to all processes done in the ArcInfo Session.  ( arc:  Precision double double  )
4)	Enter the librarian module  (arc:  Librarian)
5)	Set the library volume (Librarian:  library ncpc)
6)	Set the extraction polygon coverage (Librarian: setcover index)
7)	Set the layer to be extracted  (Librarian : setlayer air)
8)	Enter the command line to extract.  (Librarian:  extract OPTION # clip)

The extract command has a few options that can be set when extracting different types of layers such as polygons, lines, and points.
Extract DISSOLVE is used for polygon layers only because it will extract the layer and merge the polygons where they are split by index tiles, thus removing additional polys.  The ArcInfo commands involved with this option are Clip Dissolve and Build.

For Line and Point layers, the SIMPLE option was used to extract.  The topology is left unbuilt when the information is extracted.  Reason being that if the tile lines segment lines and create pseudo nodes.  The user-id from the ArcInfo table were used to unsplit the lines and remove the pseudo node.  Once that is done, the coverage can rebuild the topology.

Data Improvements
The line data coverages had tiles with some additional pseudo nodes.  The pseudo nodes were probably created as a result of different digitizing techniques (neither right nor wrong).  Using the Unsplit command we were able to clean these areas up by unsplitting only lines that had the same dxf-layer value and that shared a node.

Data cleanup
The polygon coverages extracted contained void (coded 9999) areas.  In Arcedit, these ambiguous features were removed with the following technique.
Arc:  ae  (enter arcedit module)

Arcedit: ec coverage  (enter the editing coverage)

Arcedit:  ef poly (enter the feature to be edited)

Arcedit: select for dxf-layer = 'VOID'  (querying for features in the attribute table under dxf-layer that contains attribute labeled VOID)

Arcedit:  delete (delete the features found)

Arcedit: Save  (save the changes)

The line coverages had the neatlines using the same method where the dxf-layer had values = 'NEATLINE'

Creating Shapefiles
All data sets were converted into shapefiles and clipped to the DC Boundary for import into the geodatabase.

From the Arc: prompt window, the command ARCSHAPE was used to create the shape coverages.  This required the user to specify which coverage to convert, the feature class, and naming convention of the output shapefile.

Process contact:
Contact information:
Contact organization primary:
Contact person: Chris Barnard
Contact organization: EarthData International
Contact position: Project Manager


Contact address:
Address type: mailing and physical address
Address:
45 W. Watkins Mill Road Suite G
City: Gaithersburg
State or province: MD
Postal code: 20878
Country: USA

Contact facsimile telephone: (301) 963-2064


Contact electronic mail address: cbarnard@earthdata.com


Hours of service: Regular office hours



Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
\\CITIZEN\CitizenAtlas\Miscellaneous\GeoDB112002\DCGISdata.mdb


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\OCTOGIS\MetadataData\OtherTrfPt.xml


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
E:\DCGISDATA_FINAL\PlanimetricsNFD\OtherTrfPt.shp.xml


Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
Server=intradb.dcgis.in.dc.gov; Service=5151; User=sde; Version=SDE.DEFAULT


Process step:
Process description:
Dataset copied.

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


Cloud cover: 0
Back to Top
Spatial Data Organization Information:


*Direct spatial reference method: Vector


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

ESRI terms description:
*Name: DCGIS.OtherTrfPt
*ESRI feature type: Simple
*ESRI feature geometry: Point
*ESRI topology: FALSE
*ESRI feature count: 8913
*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
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 datum name: North American Vertical Datum of 1988
*Altitude resolution: 1.000000
Altitude distance units: Meters
*Altitude encoding method: Explicit elevation coordinate included with horizontal coordinates

Depth system definition:
Depth datum name: Mean sea level
Depth resolution: .01
Depth distance units: Meters
Depth encoding method: Implicit coordinate

Back to Top
Entity and Attribute Information:


Detailed description:
*Name: DCGIS.OtherTrfPt


Entity type:
*Entity type label: DCGIS.OtherTrfPt
*Entity type type: Feature Class
*Entity type count: 8913

Attribute:
*Attribute label: DESC_
*Attribute alias: DESC_
Attribute definition:
Description

*Attribute type: String
*Attribute width: 30


Attribute:
*Attribute label: Shape
*Attribute alias: Shape
*Attribute definition:
Feature geometry.
*Attribute definition source:
ESRI

*Attribute type: Geometry
*Attribute width: 0
*Attribute precision: 0
*Attribute scale: 0


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


Attribute:
*Attribute label: OBJECTID_1
*Attribute alias: OBJECTID_1
Attribute definition:
Unique ID

*Attribute type: Number
*Attribute width: 9


Attribute:
*Attribute label: TRF
*Attribute alias: TRF
Attribute definition:
Coverage artifact

*Attribute type: Float
*Attribute width: 19
*Attribute number of decimals: 11


Attribute:
*Attribute label: TRF_ID
*Attribute alias: TRF_ID
Attribute definition:
Coverage artifact

*Attribute type: Float
*Attribute width: 19
*Attribute number of decimals: 11


Attribute:
*Attribute label: TRF_CODE
*Attribute alias: TRF_CODE
Attribute definition:
Feature code

*Attribute type: Float
*Attribute width: 19
*Attribute number of decimals: 11


Attribute:
*Attribute label: OBJECTID
*Attribute alias: OBJECTID
*Attribute definition:
Internal feature number.
*Attribute definition source:
ESRI

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


Attribute domain values:
*Unrepresentable domain:
Sequential unique whole numbers that are automatically generated.


Attribute:
*Attribute label: DXF_LAYER
*Attribute alias: DXF_LAYER
Attribute definition:
Street name

*Attribute type: String
*Attribute width: 16


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

*Attribute type: Geometry
*Attribute width: 4
*Attribute precision: 0
*Attribute scale: 0


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


Overview description:
Entity and attribute overview:
Street Centerline
Alley Centerline
Curbs
Road Polygon
Median Island
Traffic Island
Alley Polygon
Drive, Paved
Parking Lot, Paved
Parking Lot, Unpaved
Intersection (outside crosswalk)
Other Traffic Control Sign
Overhead Traffic Sign
Runway
Taxiway, Apron
Airport Perimeter
Helipad
Railroad Centerline
Metro Station, Below Ground
Metro Station Entrance (escalator goes down)
Bus Shelter
Wheelchair Ramp
Concrete Barrier (parking bumpers)
Guard Rail
Sidewalk (public)
Bridge
Tunnel Entrance
Building
Memorial
Major Fence Line
Wall
Stairs, Major Building
Misc. Line Features
Roofbreak
Statue
Planter
Tank
Bench
Bollard
Misc. Point Feature
Cemetery
Park, Zoo, Garden
Golf, Sport Field
Misc. Polygon  (area u/c, pile, shoulder, conc. slab)
Tree/Street ROW
Wooded Area, Unclassified
Lake
Pond
River
Canal
Swimming Pool (not on top of bldgs)
Stream
Dock or Pier
Jetty
Seawall
Utility Pole
Street Pole
Traffic Signal Pole
Power Trans tower
Substation
FHUNK, Hydrant, unknown
Unidentified Manhole
Headwall
Catchbasin, Standard
Grate Inlet
Grate
Obscured Areas

Entity and attribute detail citation:
Arc/Info database structure for NCPC

Back to Top
Distribution Information:


Distributor:
Contact information:
Contact organization primary:
Contact person: GIS Data Coordinator
Contact organization: DC Office of the Chief Technology Officer (OCTO)

Contact address:
Address type: mailing and physical address
Address:
441 4th St NW, Suite 930 South
City: Washington
State or province: DC
Postal code: 20001
Country: USA

Contact facsimile telephone: (202) 727-5660


Contact electronic mail address: dcgis@dc.gov


Hours of service: 8:30 am - 5:00 pm



Resource description: Downloadable 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: 1.402
*Dataset size: 1.398

Ordering instructions:
Most DC GIS datasets can be downloaded from "http://dcgis.dc.gov" on the data center page.  Orders can also be made by contacting OCTO GIS at "dcgis@dc.gov", especially for datasets not available for download.


Back to Top
Metadata Reference Information:


*Metadata date: 20080509
Metadata review date: 01/07/04


*Language of metadata: en


Metadata contact:
Contact information:
Contact organization primary:
Contact person: GIS Data Coordinator
Contact organization: DC Office of the Chief Technology Officer (OCTO)

Contact address:
Address type: mailing and physical address
Address:
441 4th St NW, Suite 930 South
City: Washington
State or province: DC
Postal code: 20001
Country: USA

Contact facsimile telephone: (202) 727-5660


Contact electronic mail address: dcgis@dc.gov


Hours of service: 8:30 am - 5:00 pm



*Metadata standard name: FGDC Content Standards for Digital Geospatial Metadata
*Metadata standard version: FGDC-STD-001-1998
*Metadata time convention: local time


Metadata access constraints: None
Metadata use constraints:
None


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: AddGlobalIDs_1
*Date: 20090307
*Time: 003039
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\AddGlobalIDs
*Command issued: AddGlobalIDs 'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.CulturePly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.EsubStnPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.HydroCenterLineLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.HydroLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.MiscPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.MiscPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.MiscTrnLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.OtherTrfPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.RoofElevPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.SewerPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.SewerPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.StructLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.StructPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.Tile1200Ply';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.SwmPoolPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.TopoPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.UnderConstPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.UtilPolePt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.WaterPly' 'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.CulturePly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.EsubStnPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.HydroCenterLineLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.HydroLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.MiscPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.MiscPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.MiscTrnLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.OtherTrfPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.RoofElevPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.SewerPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.SewerPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.StructLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.StructPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.Tile1200Ply';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.SwmPoolPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.TopoPt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.UnderConstPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.UtilPolePt';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planimetrics\DCGIS.WaterPly'


Back to Top