Land Use - Existing (ExistingLandUse)

Data format: SDE Feature Class

File or table name: DCGIS.ExistingLandUse

Coordinate system: State Plane Coordinate System 1983

Theme keywords: Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment, Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment, Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment, Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment

Abstract: Existing Landuse This Spatial Data contains 2004 Existing Land Use delineations for Washington District of Columbia. The layer was developed to support in the Comprehensive Plan review process currently underway by the DC Office of Planning Long Range Planning Division. The layer boundaries are a combination of 1999 planimetrics, DC Property Square Index boundaries that were manually split along scanned, raster tax lot boundaries.

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


Title:
Land Use - Existing (ExistingLandUse)
*File or table name: DCGIS.ExistingLandUse


Publication date: 20050505
Publication time: 5:55
Edition: 1st Edition
*Geospatial data presentation form: vector digital data


Series information:
Series name: Existing Land Use
Issue identification: DC Square Aggregate

Publication information:
Publication place: DC Office of Planning - Long Range Planning

Publication information:
Publisher: DC GIS

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


Larger work citation:
Citation information:
Title:
DC Office of Planning Geographic Information System


Description:
Abstract:
Existing Landuse

This Spatial Data contains 2004 Existing Land Use delineations for Washington District of Columbia.  The layer was developed to support in the Comprehensive Plan review process currently underway by the DC Office of Planning Long Range Planning Division.  The layer boundaries are a combination of 1999 planimetrics, DC Property Square Index boundaries that were manually split along scanned, raster tax lot boundaries.

Purpose:
This data is used for the planning and management of Washington by local government agencies.

Stereotype areas using DC Office of Tax and Revenue (OTR) owner points and use codes as the first step; supplement with additional data layers and corrections based on manual review as needed.  The end product should be a land inventory and associated maps sufficiently accurate to indicate for planning purposes how lands are currently being used in DC.  This effort is launched in advance of the availability of digitized lot boundaries for DC, and will be revised when they become available.

*Language of dataset: en


Time period of content:
Time period information:
Range of dates/times:
Beginning date: 06/21/2004
Ending date: 03/11/05

Currentness reference:
publication date

Status:
Progress: In work
Maintenance and update frequency: Continually

Spatial domain:
Bounding coordinates:
*West bounding coordinate: -77.119895
*East bounding coordinate: -76.909016
*North bounding coordinate: 38.995965
*South bounding coordinate: 38.791582

Local bounding coordinates:
*Left bounding coordinate: 389613.795500
*Right bounding coordinate: 407881.659500
*Top bounding coordinate: 147558.253000
*Bottom bounding coordinate: 124876.928000

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

Keywords:
Theme:
Theme keywords: Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment, Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment
Theme keyword thesaurus: Land Use

Theme:
Theme keywords: Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment, Land Use, Existing Land Use, Ownership, planningCadastre, Existing, environment
Theme keyword thesaurus: Land Cover

Place:
Place keywords: Washington DC, District of Columbia, DC, DC GIS, DCGIS
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 N 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 - 4:30 pm



Browse graphic:
Browse graphic file description:
View the Existing Land Use maps online
Browse graphic file type: PDF

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


Cross reference:
Citation information:
Originators: DC Office of Planning (DCOP)


Title:
Comprehensive Plan Generlized Land Use Map


Publication date: 02/01/2002
Geospatial data presentation form: vector digital data


Back to Top
Data Quality Information:


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

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

Lineage:
Source information:
Source citation:
Citation information:
Originators: DC Office of Tax and Revenue (OTR), DGIS


Title:
Owner Points Light (OwnerPtLt)


Publication date: 04/10/04
Geospatial data presentation form: vector digital data


Series information:
Series name: Public Extract

Publication information:
Publication place: DC Office of Tax and Revenue (OTR)
Publisher: DC Office of Tax and Revenue (OTR)

Other citation details:
opgisdata.OP.ownerpt_lt


Online linkage: SDE 5151 opgisdata.OP.ownerpt_lt


Type of source media: vector digital data
Source citation abbreviation:
Owner Points Light

Source time period of content:
Source currentness reference:
publication date

Source information:
Source citation:
Citation information:
Originators: DC Office of Tax and Revenue, DCGIS


Title:
Property Square Index (PropSqrPly)


Publication date: 03/29/2004
Geospatial data presentation form: vector digital data


Other citation details:
Property Squares Index from Owner Point vectorization project. The Property Square Index was created by outlining georegistered tax scans onto orthorectified aerial photography of DC.


Online linkage: PropSqrPly


Type of source media: vector digital data
Source citation abbreviation:
Property Square Index

Source information:
Source citation:
Citation information:
Originators: DC Office of Tax and Revenue, DCGIS


Title:
Tax Map Scans


Publication date: 06/21/2001
Geospatial data presentation form: raster digital data


Type of source media: raster digital data
Source citation abbreviation:
Tax Map Scans

Source information:
Source citation:
Citation information:
Originators: National Capitol Planning Commission (NCPC)


Title:
Road Bondaries (RoadPly)


Publication date: 03/31/2001
Geospatial data presentation form: vector digital data


Type of source media: vector digital data
Source citation abbreviation:
Road Bondaries

Source information:
Source citation:
Citation information:
Originators: National Parks Service


Title:
NPS-Managed Parks (NpsParks_dc10_03)


Publication date: 01/09/2004


Other citation details:
National Parks from NPS


Type of source media: vector digital data
Source citation abbreviation:
(NpsParks_dc10_03)

Source information:
Source citation:
Citation information:
Originators: DC Parks and Recreation, DCGIS


Title:
DC-Managed Parks (RecPly)


Publication date: 03/01/2004
Geospatial data presentation form: vector digital data


Type of source media: vector digital data
Source citation abbreviation:
RecPly

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


Title:
Hope IV Removed Properties (Vacant)


Geospatial data presentation form: vector digital data


Other citation details:
Geocoded from Hope IV spreadsheet of removed properties that at that time were vacant properties.


Online linkage: S:\GisData\Pending\J-Codd\ExistingLandUse\9.0\ExistingLandUseGIS90.mdb\OwnerPtLight622


Type of source media: vector digital properties
Source citation abbreviation:
OwnerPtLight622 (Hope IV Removed Properties)

Process step:
Process description:
Phase 1 of the Existing Land Use develoment process is layer creation.  1999 Planimetric Water features and Roads features (roads, intersection, medians, traffic circles, alleys) and DC OTR property square boundaries were unioned to create a base layer that contained attributes from each of the input source layers. The resulting geodatabase covered all of DC land including water features.  Some, but not all of the Planimetrics outside of the DC property squares retained the geography of the original planimetrics layer.  In the union process, the planimetric alley polygons cut into and/or split the DC property squares.  This decision was made to assist in the process of further splitting the DC property squares by tax lots that were not conforming Existing Land Use categories.  Whole or partial DC property squares were automatically assigned Existing Land Use catgories based on the Office of Tax and Revenue (OTR) Public Extract ownership database. 

GIS specialists at the DC Office of Planning conducted further manual splitting of the tax lots within the DC Property squares.  Tax lots or aggregates of contiguous tax lots automatically received an Existing Land Use category when a pre-approved percentage of land were assigned a homogenious Existing Land Use category.

Prepare spatial analysis tools

?	Build ArcGIS scripts to support one-time categorization of lands and interactive re-categorization of lands as needed.
?	Test and revise as needed

Prepare tables characterizing land use by OTR Use Codes

?	Generate a set of categories to be distinguished via use code data
?	Identify the maximum allowable proportions of other uses within an area we will designate as homogeneous (i.e., how much LMDR is ok within LDR.)
?	For "Government", also try to distinguish "Federal" by examining owner name

Process OTR data

?	Begin with square (block) boundaries
?	Split them into "square segments" to the extent practicable using alley centerline data
?	Process square segments in bulk, identifying a designated land use classification if the predominant use covers the entire segment or if the other uses are sufficiently limited and consistent with the predominant use.
?	Revisit all square segments that are not automatically classified using a semi-automated process:
o	Begin with test areas in each ward of the city; revise the process if necessary before proceeding further
o	The software will highlight all non-classified square segments
o	Zoom to each in turn and show owner point data color-coded by use and the tax lot boundaries
o	Operators will split segments as needed to separate distinct uses; the software will automatically re-evaluate each newly-split segment and classify it (removing the highlighting) if it now meets the rules for automatic classification.

Additional Bulk Processing Steps:

?	Separate Government areas into Federal/District/undetermined 
o	? via owner point ownership info
o	? via other sources
?	Separate Commercial areas, identifying neighborhood commercial areas distinctly (using boundaries provided by LRP staff)
?	Separate areas that are:
o	Alleys
o	Sidewalks
o	Road surfaces
o	Parking lots ?
?	Tag other areas (outside of squares) known to be parkland (NPS)
?	Tag other areas (outside of squares) believed to be managed by Parks and Rec
?	Tag areas known to be military
?	Tag areas known to be Federal
?	Tag areas known to be water (Potomac/Anacostia/other)

Initial Manual Review

?	Print large-format maps for in-house review by OP planners (possibly with orthos as faint overlays)
o	Any corrections must be vouched for by a specific planner, whose name will be recorded as the source of that information

Pictometry Review

?	Focus on suspect areas, and use oblique aerial photos to resolve as needed

Windshield Review

?	For areas of particular concern - and a random sample of areas we think are ok -- review in the field
?	We won't know how extensive this is until we see the interim products

IMPLIED DATA HIERARCHY

?	Street polygons
?	Sidewalk polygons
?	Alley polygons
?	Parking lots *** not in squares *** 
?	
?	Separately QC'D military base boundaries
?	
?	Squares/owner points
o	Owner name = United States xxx or District of xxx supercedes use code
o	Use codes thereafter
?	(separate designation) Parking lots *** in squares only ***
?	(separate designation - CHECK ) Parks and rec parks *** in squares ***
?	National park boundaries (from NPS)
?	Separately prepared and QC'd boundaries for Mall, Zoo, other fed lands as needed
?	Parks and rec parks *** outside of squares ***

Process date: 03/03/2005


Process contact:
Contact information:
Contact organization primary:
Contact person: John Codd
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
Country: USA

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


Process step:
Process description:
Phase 2 of the Existing Land Use development is the review process.  The Long Range Planning Division drew up strict review guidelines.  Neighborhood Planning staff, Development Review staff and Historic Preservation staff each reviewed 36x48 hardcopy, Ward maps of the Existing Land Use layer.  Reviewers marked polygons that were assigned incorrect Existing Land Use categories with correct attributes.  GIS specialist staff updated the geodatabase to reflect the marked changes.

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

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:
Metadata imported.

Source used citation abbreviation:
C:\Documents and Settings\WisemanA\My Documents\ExistingLandUse.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


Back to Top
Spatial Data Organization Information:


*Direct spatial reference method: Vector


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

ESRI terms description:
*Name: DCGIS.ExistingLandUse
*ESRI feature type: Simple
*ESRI feature geometry: Polygon
*ESRI topology: FALSE
*ESRI feature count: 55249
*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.ExistingLandUse


Entity type:
*Entity type label: DCGIS.ExistingLandUse
*Entity type type: Feature Class
*Entity type count: 55249
Entity type definition:
Existing Landuse
Entity type definition source:
DC Office of Planning (DCOP)

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: OP_LAYER
Attribute definition:
Source Planimetrics

Beginning date of attribute values: 1999
Ending date of attribute values: 1999


Attribute:
Attribute label: CNT_OP_LAYER
Attribute definition:
Original polygon count.

Beginning date of attribute values: 08/2004


Attribute:
Attribute label: MIN_DXF_LAYER


Attribute:
Attribute label: AREAKM
Attribute definition:
Area of The District of Columbia in square kilometers

Attribute:
Attribute label: AREAMILES
Attribute definition:
Area of The District of Columbia in square miles

Attribute:
Attribute label: WAT
Attribute definition:
Original Planimetric Water Feature

Attribute:
Attribute label: WAT_ID
Attribute definition:
Original Planimetric Water Feature Object ID

Attribute:
Attribute label: WAT_CODE
Attribute definition:
Original Planimetric Water Feature Code

Attribute:
Attribute label: WAT_NAME


Attribute:
Attribute label: DXF_LAYER
Attribute definition:
Original Planimetric Water Feature DXF_Layer Attribute

Attribute:
Attribute label: SQRSUF
Attribute definition:
DC Property Square number and suffix where one occurs
Attribute definition source:
Real Property Tax Assessors (RPTA) public extract database

Ending date of attribute values: 2005


Attribute:
Attribute label: WARD_ID
Attribute definition:
Original Polygons assigned a ward number (1-8).

Attribute:
Attribute label: GIS_ID
Attribute definition:
DC Property Square number

Attribute:
Attribute label: SQR_NUM
Attribute definition:
DC Property Square number

Attribute:
Attribute label: LU_CODE
Attribute definition:
Current Existing Land Use attribute

Attribute:
Attribute label: QCFLAG
Attribute definition:
Flag field for Phase 2 Review and Editing process

Attribute:
Attribute label: OLD_LU_CD
Attribute definition:
Last LU_CODE before change

Attribute:
Attribute label: ISVACANT
Attribute definition:
Tracks vacant polygon (lot or lots)

Attribute domain values:
Enumerated domain:
Enumerated domain value: y
Enumerated domain value definition:
The polygon (lot or lots) is vacant

Enumerated domain:
Enumerated domain value: Null
Enumerated domain value definition:
The polygon (lot/lots) is not vacant

Enumerated domain:
Enumerated domain value: blank
Enumerated domain value definition:
The polygon (lot/lots) is not vacant

Attribute:
Attribute label: HASBLDG
Attribute definition:
Tracks vacant polygon (lot or lots) structure status

Attribute domain values:
Enumerated domain:
Enumerated domain value: y
Enumerated domain value definition:
a building or sturucure is present

Enumerated domain:
Enumerated domain value: n
Enumerated domain value definition:
a building or structure is not present

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

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


Attribute:
Attribute label: VACTYPE
Attribute definition:
Vacant polygon (lot or lots) type

Attribute domain values:
Enumerated domain:
Enumerated domain value: V
Enumerated domain value definition:
Vacant Land

Enumerated domain:
Enumerated domain value: VB
Enumerated domain value definition:
Vacant Building or structure

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:
Dataset overview:
Existing Landuse

This Spatial Data contains 2004 Existing Land Use delineations for Washington District of Columbia.  The layer was developed to support in the Comprehensive Plan review process currently underway by the DC Office of Planning Long Range Planning Division.  The layer boundaries are a combination of 1999 planimetrics, DC Property Square Index boundaries that were manually split along scanned, raster tax lot boundaries.

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 N Capitol St, NW  # 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:30 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:
Format name: ARCGIS
File decompression technique: no compression applied

Digital transfer option:
Online option:
Computer contact information:
Network address:
Network resource name: http://www.draft.dcgis.com/data_catalogue.asp

Access instructions:
Local area network


Back to Top
Metadata Reference Information:


*Metadata date: 20071214


*Language of metadata: en


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

Contact address:
Address type: mailing and physical address
Address:
801 N 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 - 4:30 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:
*Date: 20051003
*Time: 181421
*Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyFeatures
*Command issued: CopyFeatures E:\DCGISDATA_WORKSPACE\OP\OPS9_ExistingLanduse.mdb\ExistingLanduse\ExistingLanduse "Database Connections\intradbSU.sde\SDE.Planning\SDE.ExistingLanduse" # 0 0 0


Process:
*Process name: AddGlobalIDs_2
*Date: 20090307
*Time: 003754
*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