Land Use - Planned 2006 (PlannedLandUse2006)

Data format: SDE Feature Class

File or table name: DCGIS.PlannedLandUse2006

Coordinate system: State Plane Coordinate System 1983

Theme keywords: Comprehensive Plan Land Use, Comprehensive Plan, Land Use, Landuse, future land use, environment

Abstract: Planned Landuse from the 2006 DC Comprehensive Plan This data set was digitized from the Generalized Land Use Map of the District of Columbia Comprehensive Plan (January 2002), and shows which areas of the city are planned for various uses. These uses include residential and commercial uses at various densities, public land, institutional, federal, and industrial uses. Although planned uses and current uses may be similar, this is not a data set describing current land use. This is a generalized product, and cannot be used to identity specific uses for all specific locations in the District of Columbia.

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 Office of Planning


Title:
Land Use - Planned 2006 (PlannedLandUse2006)
*File or table name: DCGIS.PlannedLandUse2006


Publication date: 20061220
*Geospatial data presentation form: vector digital data


Publication information:
Publisher: DC GIS

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


Larger work citation:
Citation information:
Originators: DC Office of Planning


Title:
District of Columbia Generalized Land Use Map


Publication date: January 2002
Geospatial data presentation form: map


Description:
Abstract:
Planned Landuse from the 2006 DC Comprehensive Plan

This data set was digitized from the Generalized Land Use Map of the District of Columbia Comprehensive Plan (January 2002), and shows which areas of the city are planned for various uses.  These uses include residential and commercial uses at various densities, public land, institutional, federal, and industrial uses.  Although planned uses and current uses may be similar, this is not a data set describing current land use.  This is a generalized product, and cannot be used to identity specific uses for all specific locations in the District of Columbia.

Purpose:
This data set replaces the Generalized Land Use Map included in previous editions of the DC Comprehensive Plan.  It  is intended to guide zoning and development in the District.  It is a visual depiction of District policy about appropriate land uses for various parts of the District.  It is not intended to document existing conditions.

Supplemental information:
This information was approved by the Council of the District of Columbia on printed maps at a scale of 1:18000 (one inch = 1500 feet.)   Details that were not visible as printed were not reviewed by Council, and have no meaning whatsoever.

*Language of dataset: en


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

Currentness reference:
publication date

Status:
Progress: Complete
Maintenance and update frequency: Irregular

Spatial domain:
Bounding coordinates:
*West bounding coordinate: -77.119455
*East bounding coordinate: -76.909016
*North bounding coordinate: 38.995970
*South bounding coordinate: 38.803055

Local bounding coordinates:
*Left bounding coordinate: 389651.942500
*Right bounding coordinate: 407881.659500
*Top bounding coordinate: 147558.865000
*Bottom bounding coordinate: 126150.421000

Keywords:
Theme:
Theme keywords: Comprehensive Plan Land Use, Comprehensive Plan, Land Use, Landuse, future land use, environment
Theme keyword thesaurus: None

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

Access constraints: none
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 organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St, NE  Suite 4000
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


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



Data set credit:
DC Office of Planning (DCOP)

Security information:
Security classification: Unclassified

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


Back to Top
Data Quality Information:


Attribute accuracy:
Attribute accuracy report:
This is the source dataset for the current Planned Land Use Map produced by the Office of Planning.  The information in this dataset is the source for land use information shown on that map, so the two should match.

Completeness report:
This dataset was originally traced from the January 2002 District of Columbia Generalized Land Use map, and then was edited extensively to reflect the Comprehensive Plan adopted by the Council of the District of Columbia in December, 2006.  It is intended to reflect all of the changes made by staff and Council during the Comprehensive Plan approval process.

Note that the level of spatial detail varies across the District.  In all cases, only details visible at a printed scale of 1:18000 (one inch = 1500 feet) are meaningful.

Originally developed in ArcGis Version 8.1, this dataset has undergone several revisions and iterations.  The primary enhancements consist of:

1)  Topology rules were added in the ArcGis (8.3) editing environment to ensure that Land Uase polygons shared common boundaries withou overlaps and without gaps
2)  Attribute information was reviewed against the January 2002 edition of the DC Generalized Land Use Map in both hardcopy and scanned image format and verified to be correct
3)  Updated the contents of the LUCODE field to reflect updates to the ALLCODES field (same as ALLCODES except where multiple entries, then enter value MIXED)
4)  This dataset has been clipped to the DC Boundaries
5) Using ArcGIS 9.1, numerous edits have been included in this data set to reflect the current policy of the Council of the District of Columbia.

Positional accuracy:
Horizontal positional accuracy:
Horizontal positional accuracy report:
This is a policy statement, not a survey instrument.  It is intended to reflect the policies adopted in the District Elements of the Comprehensive Plan for the District of Columbia at the published scale of 1:1500.  Complete, detailed and accurate electronic property boundary information was not available when this data set was compiled, so some boundaries may not be shown in precisely the intended locations.

Lineage:
Source information:
Source citation:
Citation information:
Originators: DC Office of Planning


Title:
District of Columbia Generalized Land Use Map


Publication date: January 2002
Geospatial data presentation form: map


Source scale denominator: 14400
Type of source media: paper
Source citation abbreviation:
District of Columbia Generalized Land Use Map
Source contribution:
This previous land use policy document was produced at a scale that reveals more detail, but on a less accurate cartographic base than the current product.

Source time period of content:
Time period information:
Single date/time:
Calendar date: January 2002

Source currentness reference:
publication date

Source information:
Source scale denominator: 18000
Type of source media: paper
Source citation abbreviation:
District of Columbia Council -- Comprehensive Plan approved December 2006
Source contribution:
The 2006 Comprehensive Plan revison process resulted in numerous changes to policy regarding land use in DC.  Numerous drafts were prepared and reviewe by Office of Planning staff , by Council staff, and ultimately by the Council itself.

Process step:
Process description:
Printed land use map (District of Columbia Generalized Land Use Map - January 2002) was scanned, and subsequently digitized.  The digitized version was submitted to planners for approval.  Changes and problems were identified, and edits were performed in ArcMap at a scale of approximately 1:5000.  

Land use polygons were snapped to various layers- street centerlines, zoning boundaries, building outlines, respectively.  Data were then edited further for consistency with the newest edition of the printed land use map, dated January 2002.  In selected locations, boundaries that were extremely generalized on the source map were rendered in more detail in this data set.

Process date: 07/17/2006


Process contact:
Contact information:
Contact organization primary:
Contact organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St, NE  # 4000
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


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



Process step:
Process description:
Added new field [LUCODE] to to simplify view of Land Use codes in both ArcGis and ArcView environments.  Previously, mixed land use types utilized numerous shaded bands to display the various Land Use types.

Multiple mixed Land Use code shadings, while easily identified in a tabular environment, are not always discernable between shades of a specific color on a map.  The new field [LUCODE] keeps all existing land use codes, but multiple codes in the [ALLCODES] field are replaced with the value "MIXED".

Process date: 04/25/2003


Process contact:
Contact information:
Contact organization primary:
Contact organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St, NE  # 4000
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


Process step:
Process description:
Performed final validation between existing Landuse dataset and hardcopy source Landuse (January 2002) map.
1)  Topology Rules were added in the ArcGis editing environment to ensure that Land Uase polygons shared common boundaries withou overlaps and without gaps
2)  Attribute information was reviewed against the January 2002 edition of the DC Generalized Land Use Map in both hardcopy and scanned image format and verified to be correct
3)  Updated the contents of the LUCODE field to reflect updates to the ALLCODES field (same as ALLCODES except where multiple entries, then enter value MIXED)
4)  Developed a shade styleset to ensure consistent colors between original Landuse map when printed on DCOP color plotters.  Developed corresponding layerfiles.

Process date: 02/27/2004


Process contact:
Contact information:
Contact organization primary:
Contact organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St, NE  # 4000
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


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



Process step:
Process description:
Reattributed polygon at intersection of Georgia Ave. and Missouri Ave., NW from High Density Residential to Medium Density Residential.

Process date: 09/13/2004


Process contact:
Contact information:
Contact organization primary:
Contact organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St., NW  # 4000
City: Washington
State or province: DC
Postal code: 20002

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


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



Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
Server=opdb; Service=5152; Database=opgisdata; User=opgisuser; Version=sde.DEFAULT


Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
Server=opdb; Service=sde:sqlserver:opdb\opdb9; Database=opgisdata; User=op; Version=sde.DEFAULT


Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
Server=opdb; Service=sde:sqlserver:opdb\opdb9; Database=opgisdata; User=op; Version=sde.DEFAULT


Process step:
Process description:
Metadata imported.

Source used citation abbreviation:
C:\DOCUME~1\AAnna\LOCALS~1\Temp\xml48.tmp


Process step:
Process description:
Dataset copied.

Source used citation abbreviation:
Server=opdb; Service=sde:sqlserver:opdb\opdb9; Database=OPGISDev; User=op; 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: None
Back to Top
Spatial Data Organization Information:


*Direct spatial reference method: Vector


Point and vector object information:
SDTS terms description:
*Name: DCGIS.PlannedLandUse2006
*SDTS point and vector object type: G-polygon
*Point and vector object count: 1613

ESRI terms description:
*Name: DCGIS.PlannedLandUse2006
*ESRI feature type: Simple
*ESRI feature geometry: Polygon
*ESRI topology: FALSE
*ESRI feature count: 1613
*Spatial index: TRUE
*Linear referencing: FALSE


*XY rank: 1
*Z rank: 1
*Topology weight: 5.000000
*Events on validation: FALSE
Participates in topology rules:
*Rule identifier: 31
Participates in topology rules:
*Rule identifier: 32


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.PlannedLandUse2006


Entity type:
*Entity type label: DCGIS.PlannedLandUse2006
*Entity type type: Feature Class
*Entity type count: 1613
Entity type definition:
Planned Landuse
Entity type definition source:
DC Office of Planning

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: LUCODE
Attribute definition:
Land use code (simplified)
Attribute definition source:
ESRI

Attribute domain values:
Enumerated domain:
Enumerated domain value: CHD
Enumerated domain value definition:
Commercial High Density

Enumerated domain:
Enumerated domain value: CLD
Enumerated domain value definition:
Commercial Low Density

Enumerated domain:
Enumerated domain value: CMED
Enumerated domain value definition:
Commercial Medium Density

Enumerated domain:
Enumerated domain value: CMOD
Enumerated domain value definition:
Commercial Moderate Density

Enumerated domain:
Enumerated domain value: FED
Enumerated domain value definition:
Federal

Enumerated domain:
Enumerated domain value: INST
Enumerated domain value definition:
Institutional

Enumerated domain:
Enumerated domain value: LPUB
Enumerated domain value definition:
Local Public Use

Enumerated domain:
Enumerated domain value: MIXED
Enumerated domain value definition:
mixed uses

Enumerated domain:
Enumerated domain value: PROS
Enumerated domain value definition:
Parks, Recreation, and Open Space

Enumerated domain:
Enumerated domain value: PROTECH
Enumerated domain value definition:
Professional, Techical

Enumerated domain:
Enumerated domain value: RHD
Enumerated domain value definition:
Residential, High Density

Enumerated domain:
Enumerated domain value: RLD
Enumerated domain value definition:
Residential Low Density

Enumerated domain:
Enumerated domain value: RMED
Enumerated domain value definition:
Residential Medium Density

Enumerated domain:
Enumerated domain value: RMOD
Enumerated domain value definition:
Residential Moderate Density

Enumerated domain:
Enumerated domain value: WATER
Enumerated domain value definition:
water

Attribute:
Attribute label: ALLCODES
Attribute definition:
Land Use Code(s)
Attribute definition source:
DC Generalized Land Use Map

Attribute domain values:
Enumerated domain:
Enumerated domain value: RLD
Enumerated domain value definition:
Residential Low Density

Enumerated domain:
Enumerated domain value: RMOD
Enumerated domain value definition:
Residential Moderate Density

Enumerated domain:
Enumerated domain value: RMED
Enumerated domain value definition:
Residential Medium Density

Enumerated domain:
Enumerated domain value: RHD
Enumerated domain value definition:
Residential High Density

Enumerated domain:
Enumerated domain value: CLD
Enumerated domain value definition:
Commercial Low Density

Enumerated domain:
Enumerated domain value: CMOD
Enumerated domain value definition:
Commercial Moderate Density

Enumerated domain:
Enumerated domain value: CMED
Enumerated domain value definition:
Commercial Medium Density

Enumerated domain:
Enumerated domain value: CMHD
Enumerated domain value definition:
Commercial Medium-High Density

Enumerated domain:
Enumerated domain value: CHD
Enumerated domain value definition:
Commercial High Density

Enumerated domain:
Enumerated domain value: FED
Enumerated domain value definition:
Federal

Enumerated domain:
Enumerated domain value: LPUB
Enumerated domain value definition:
Local Public Facilities

Enumerated domain:
Enumerated domain value: INST
Enumerated domain value definition:
Institutional

Enumerated domain:
Enumerated domain value: PROS
Enumerated domain value definition:
Parks, Recreation, and Open Space

Enumerated domain:
Enumerated domain value: PROTECH
Enumerated domain value definition:
Production and Technical Employment

Enumerated domain:
Enumerated domain value: WATER
Enumerated domain value definition:
Water Areas

Attribute:
Attribute label: RLD
Attribute definition:
Residential Low Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Attribute:
Attribute label: RMED
Attribute definition:
residential medium density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Attribute:
Attribute label: RHD
Attribute definition:
Residential High Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: CLD
Attribute definition:
Commercial Low Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: CMOD
Attribute definition:
Commercial Moderate Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: CMED
Attribute definition:
Commercial Medium Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: CMHD
Attribute definition:
Commercial Medium High Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: CHD
Attribute definition:
Commercial High Density

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: FED
Attribute definition:
Federal

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: LPUB
Attribute definition:
Local Public

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: INST
Attribute definition:
Institutional
Attribute definition source:
DC Generalized Land Use Map

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: PROS
Attribute definition:
Parks, Recreation and Open Space
Attribute definition source:
DC Generalized Land Use Map

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: PROTECH
Attribute definition:
Professional, Technical
Attribute definition source:
DC Generalized Land Use Map

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: RMOD
Attribute definition:
Residential Moderate

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: QC_STATUS


Attribute:
Attribute label: MAPEDITNAME
Attribute definition:
Map Edit Name

Attribute:
Attribute label: MAPEDITNAME2
Attribute definition:
Second Map Edit Name

Attribute:
Attribute label: MAPEDITNAME3
Attribute definition:
Third Map Edit Name

Attribute:
Attribute label: EDITEDBY
Attribute definition:
Operator name

Attribute:
Attribute label: WATER
Attribute definition:
Water

Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

Attribute:
Attribute label: EDITDATE
Attribute definition:
Edit date

Attribute:
Attribute label: Shape


Attribute domain values:
Enumerated domain:
Enumerated domain value: 0
Enumerated domain value definition:
no

Enumerated domain:
Enumerated domain value: 1
Enumerated domain value definition:
yes

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.AREA
*Attribute alias: SHAPE.AREA


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


Attribute:
*Attribute label: SHAPE.LEN
*Attribute alias: SHAPE.LEN


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


Overview description:
Entity and attribute overview:
Two fields [LUCODE] and [ALLCODES] show Land Use code associated with records.  [LUCODE] is a summarization of [ALLCODES] in which multiple Land Use codes have been reattributed as "MIXED".

Multiple Land Use Code Flag fields (Field Names of Land Use Codes) have also been defined.  Field values are either 0 (FALSE)  or 1 (TRUE) and denote the Land Use of the identified record.

Back to Top
Distribution Information:


Distributor:
Contact information:
Contact organization primary:
Contact organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St, NE  # 4000
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


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

Available time period:
Time period information:
Single date/time:
Calendar date: 2004-0227

Back to Top
Metadata Reference Information:


*Metadata date: 20071214


*Language of metadata: en


Metadata contact:
Contact information:
Contact organization primary:
Contact person: REQUIRED: The person responsible for the metadata information.
Contact organization: DC Office of Planning

Contact address:
Address type: mailing and physical address
Address:
801 North Capitol St, NE  # 4000
City: Washington
State or province: DC
Postal code: 20002
Country: USA

Contact voice telephone: 202-442-7600
Contact facsimile telephone: 202-442-7637


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 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:
*Date: 20070322
*Time: 213128
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyFeatures
*Command issued: CopyFeatures E:\DataLoad031507\OPGIS2007_2.mdb\CompPlan\PlannedLandUse2006 "Database Connections\dcgiscentral Data Loader.sde\DCGIS.Planning\DCGIS.PlannedLandUse2006" DCGISDBP_S 10000 0 0


Process:
*Process name: AddGlobalIDs_2
*Date: 20090307
*Time: 003810
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\AddGlobalIDs
*Command issued: AddGlobalIDs 'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.BaistIndex';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.CFAReviewPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.CompPlanPlanningAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.DistrictRevitalization';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.DntnDevCompPlan';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.EconDevelZones';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.EnergyStar';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.ExistingLandUse';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistDisPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistoricDistrictsAndAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistoricStructurePoints';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistoricStructures';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistStLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistStPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HomeAgain';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HubZones';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandmarkBldgPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandmarkPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandUse';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandUseEmpty';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LargeSites';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LEED';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LEnfantPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.NbhdComposition';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.NewCommCandidates';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.OtherHistoricAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.PersistentProblemAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.PlannedLandUse2006';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.Reservations';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.RestoreDC';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.ShawHist';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.ShipsteadLuce';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.SNIPs' 'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.BaistIndex';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.CFAReviewPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.CompPlanPlanningAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.DistrictRevitalization';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.DntnDevCompPlan';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.EconDevelZones';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.EnergyStar';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.ExistingLandUse';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistDisPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistoricDistrictsAndAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistoricStructurePoints';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistoricStructures';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistStLn';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HistStPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HomeAgain';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.HubZones';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandmarkBldgPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandmarkPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandUse';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LandUseEmpty';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LargeSites';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LEED';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.LEnfantPly';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.NbhdComposition';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.NewCommCandidates';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.OtherHistoricAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.PersistentProblemAreas';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.PlannedLandUse2006';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.Reservations';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.RestoreDC';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.ShawHist';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.ShipsteadLuce';'Database Connections\vector_data_dcgiscentral.sde\DCGIS.Planning\DCGIS.SNIPs'


Back to Top