Description: This layer represents the geographic boundaries of supervisor districts within Fairfax County.Contact: Fairfax County Office of ElectionsData Accessibility: Publicly available Update frequency: As needed Creation date: 6/1/2011 Layer name: REGMGR.SUPERVISOR_DISTRICTSDataset name: REGMGR.ELECTORAL
Copyright Text: Fairfax County GIS and Mapping Services for creating and reviewing the data, and various Fairfax County Agencies, including the Office of County Attorney and the Office of the Electoral Board and General Registrar
Description: Areas of approved zoning for Fairfax County, Town of Herndon, and Town of Vienna. This layer contains the zoning code, the zoning category, the jurisdiction, a proffer flag, and a public land flag.Contact: Fairfax County GIS Division Data Accessibility: Publicly available Update frequency: DailyCreation date: 1/1/2001 Layer name: GISMGR.ZONINGDataset name: GISMGR.ZONING
Copyright Text: The data set was created by Analytical Surveys Incorporated (ASI) and Landata under contract to Fairfax County. Quality control checks were performed by Engineering Systems Incorporated and Dewberry and Davis. Staff from the GIS branch were also used for quality control checking. Since 2001 Fairfax County staff have been solely responsible for maintaining this data.
JURISDICTION
(
type: esriFieldTypeString, alias: Jurisdiction, length: 20
,
Coded Values:
[FAIRFAX COUNTY: FAIRFAX COUNTY]
,
[TOWN OF VIENNA: TOWN OF VIENNA]
,
[TOWN OF HERNDON: TOWN OF HERNDON]
)
Description: The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the STATEPLANE projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.
Description: Floodplain delineations were first added to the County tax maps in the 1970's for creeks and streams with watersheds of 1 square mile or greater. In 1977 all the studies on these large streams had been completed and a "Floodplain Overlay District" was created. Within several years this floodplain overlay district was depicted on the zoning maps. Again, these delineations were only for those creeks with drainage areas of over 1 square mile. A note in a 1981 memo to the Mapping Division about these delineations said, "...the County delineation of a Flood Plain Overlay District line on the tax map is treated here as a flag or general indicator of approximate location of this District's line. Normal development provides 2 field run topography professionally certified on which the floodplain elevations can be more accurately determined..." In 1985 the Zoning Ordinance was amended, an entire section on floodplains was added to Chapter 2 and the definition of what constituted a floodplain was significantly revised. Where as the Floodplain Overlay District had principally contained only those overbank areas inundated by the 100-yr storm along streams with drainage areas of 1 square mile or greater (i.e. 640 acres), the new definition included the overbank areas inundated by the 100-year storm along creeks with drainage areas of 70 acres and greater. But this change in the definition of floodplain created a problem for those who had become dependant on the tax maps to show them whether or not there was floodplain on a given property. These newly-defined floodplains were not yet studied or mapped and would only be mapped one property at a time, as each parcel containing these smaller floodplains submitted plans for development. When such parcels were developed, floodplain studies were required, and floodplain easements (later titled "floodplain and storm drainage easements") were recorded around these smaller floodplains. And as those easements were recorded, they were added to the tax maps. For all the floodplains which have been studied since 1985, the limits of the floodplain and storm drainage easements have been added to the tax maps, when such easements were required by the County Code or the Zoning Ordinance. But if a parcel has not yet been developed or if it was developed prior to 1985, there is usually no easement around the floodplain. There are also numerous cases where, for some reason, floodplain easements were recorded along small creeks with drainage areas well below 70 acres. These recorded "floodplain" easements were then added to the tax maps. THE RESULT: The tax maps cannot be used to definitively determine whether floodplain exists on a given parcel .There are approximately 900 miles of streams which meet the 70 acre drainage area requirement for floodplains, but to date (6/2003) almost 400 of these 900 miles remain unstudied. And if a stream has never been studied, no easement would have been recorded and thus the fact that it was a floodplain would not be reflected in the tax maps. Only after a determination of the drainage area is made can one know whether the overbank areas along a given creek meet the Zoning Ordinance definition of floodplain. Further if the drainage area is over 70 acres, only a floodplain study can determine the limits of the floodplain that is, how much of the overbank areas are inundated by the peak flow of the 100-yr storm. The layer for floodplains with drainage areas of over 1 square mile is good, but above that, it's inconsistent, especially in those areas which are minor floodplains (i.e. less than 360 acres of drainage area) and which were developed prior to 1985. The entire 850 or so miles of floodplain have not been mapped as unbroken corridors. And the "floodplain" here in Fairfax County, we're using the zoning ordinance definition which is the 100-yr water surface limits along streams with drainage areas of over 70 acres. This definition came into the zoning ordinance in 1985, so from that time, developers have had to study and map even these smaller floodplains on their developments and put them in easements. These easements have been captured on our tax maps since 1985, development by development, as the record plats were recorded. FEMA doesn't recognize as Special Flood Hazard Areas, many stream valleys that we would call floodplain. The layer currently on the data loader for floodplains is missing many segments of stream that are defined as floodplain per the zoning ordinance. Yet because of our zoning ordinance definition, this layer extends up in many areas far beyond where FEMA has mapped its 100-yr floodplains.Contact: Fairfax County GIS DivisionData Accessibility: Publicly availableUpdate frequency: DailyCreation date: 1/1/2000Layer name: GISMGR.FLOOD_PLAIN_RECORDEDDataset Name: GISMGR.ENCUMBRANCES
Copyright Text: The data set was created by Analytical Surveys Incorporated (ASI) and Landata under contract to Fairfax County. Quality control checks were performed by Engineering Systems Incorporated and Dewberry and Davis. Staff from the GIS branch were also used for quality control checking. Since 2001 Fairfax County staff have been solely responsible for maintaining this data.
Description: Estimated flood plain areas. Streams draining a watershed with a drainage area of greater than 70 acres but less than 360 acres (i.e. "minor floodplains") were buffered 100 feet on each side.A high-resolution Digital Elevation Model (DEM) of the county, created from over 1.1 million spot elevations, was used to create synthetic stream networks at 70ac a threshold. This synthetic stream network was then used to create a floodplain stream centerline for streams draining a watershed with a drainage area of greater than 70 acres but less than 360 acres (i.e. "minor floodplains"). The synthetic stream network was then used as the stream centerline to which the buffer was applied. Therefore, the gridded stream network was used to both locate the centerline against which the buffer was applied, and to determine the drainage area at any given point along a stream.
Description: This dataset is a combination of Floodplain Studies, Stormwater Planning Staff Investigations, and LDS staff request represented by distinct polygons. These areas are used to flag records in PLUS for further review by LDS staff. This dataset is intended for internal use. Contact: Land Development ServicesData Accessibility: Internal Use OnlyUpdate Frequency: As NeededLast Revision Date: 4/16/2024Creation Date: 4/16/2024Layer Name: LDSAMGR.LDS_PROPERTY_FLAGS
Copyright Text: Fairfax County, Virginia; Land Development Services
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
FLAG_ID
(
type: esriFieldTypeInteger, alias: Flag ID:
)
FLAG_TYPE
(
type: esriFieldTypeString, alias: Flag type:, length: 100
,
Coded Values:
[Area of Concern: Area of Concern]
,
[LDS Point of Interest: LDS Point of Interest]
,
[Floodplain Study: Floodplain Study]
, ...1 more...
)
FLAG_DESCRIPTION
(
type: esriFieldTypeString, alias: Flag description:, length: 2000
)
SOURCE
(
type: esriFieldTypeString, alias: Source:, length: 100
,
Coded Values:
[Board of Supervisors: Board of Supervisors]
,
[Stormwater Planning Division: Stormwater Planning Division]
,
[Land Development Services: Land Development Services]
)
POLYGON_AREA
(
type: esriFieldTypeDouble, alias: Polygon area (ac):
)
Name: Resource Protection Areas (Chesapeake Bay Preservation Area)
Display Field: TYPE
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: This set of data provides a delineation of Chesapeake Bay Preservation Areas (Resource Protection Areas and Resource Management Areas) as set forth in Section 118-1-7 of Chapter 118, Chesapeake Bay Preservation Ordinance, of the Code of the County of Fairfax, Virginia adopted by the Board of Supervisors on July 7, 2003 (effective November 18, 2003). The CBPA maps were adopted by the Board of Supervisors on November 17, 2003. Revisons to the 2003 RPAs were made based on a quality assurance field and map review. The revisions were adopted by the Board of Supervisors on July 11, 2005 (effective July 12, 2005). Where RPA and RMA boundaries on the adopted map differ from boundaries as determined from the text of the Ordinance, the text shall govern.
Description: Historic Overlay Districts (HODs) are bounded areas created by the BOS. Inside an HOD certain regulations on development apply which serve to protect historic resources inside that area. HODs are administered by the History Commission and the Planning Division of the Department of Planning and Development.Contact: Daniel WhiteData Accessibility: Publicly available to Fairfax County Employees and represented to citizens and the public through a number of GIS applications.Update Frequency: As neededCreation Date: N/AFeature Set Name: DPZMGR.HISTORIC_AREASFeature Layer Name: DPZMGR.HISTORIC_OVERLAY_DISTRICTS
Copyright Text: Fairfax County Department of Planning & Development
Description: This layer was constructed by combining several intermediate layers which were developed in April 2010 from a database constructed several years earlier by DPZ staff. On this layer almost all features are shown as planimetric shapes. A few features are shown as 220-foot diameter circles placed as closely as possible over the center of the feature. In the table, a show_as_point column identifies these features with a "yes." There are also 5 linear-style features expressed as polygons. These are roads shown as 125-foot wide buffers following the centerline of the inventoried feature. All features appear only once in the layer except for Great Falls Park Historic District Park, which is split into two polygons, one for the portion in Upper Potomac Planning District and one for the portion in McLean Planning District.Contact: Daniel WhiteData Accessibility: Publicly available to Fairfax County Employees and represented to citizens and the public through a number of GIS applications.Update Frequency: As neededCreation Date: April 2010Feature Set Name: DPZMGR.HISTORIC_AREASFeature Layer Name: DPZMGR.INVENTORY_OF_HISTORIC_SITES
Copyright Text: The geographic data layers produced by the Government of Fairfax County, Virginia (“Fairfax County”), and any associated maps and applications, are provided as a public resource. While every reasonable effort is made to ensure the accuracy and completeness of the data, Fairfax County makes no warranties, expressed or implied, concerning the accuracy, completeness or suitability of its data, and it should not be construed or used as a legal description.
Pursuant to Section 54.1-402 of the Code of Virginia, any determination of topography or contours, or any depiction of physical improvements, property lines or boundaries is for general information only and shall not be used for the design, modification, or construction of improvements to real property or for flood plain determination.
Copyright by Fairfax County. Except as provided herein, all rights are reserved. Authorization to reproduce material for internal or personal use by any user of this information is granted by Fairfax County, the copyright owner.
This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult with Fairfax County and information sources to ascertain the usability of the information including but not limited to Parcels, Chesapeake Bay Preservation Areas, Flood Plains etc...
Description: The boundaries of the zoning overlay districts in Fairfax County. The districts show in this layer are for the purpose of providing for special regulations in given designated areas of the County to accomplish stated purposes that are set forth for each district. For further information go to the zoning ordinance associated with the overlay districts: https://www.fairfaxcounty.gov/planning-development/sites/planning-development/files/Assets/documents/Zoning/Zoning%20Ordinance/art07.pdfContact: Fairfax County GIS Division Data Accessibility: Publicly available Update frequency: As needed Creation date: 1/1/2001 Layer name: GISMGR.OVERLAY_DISTRICTSDataset name: GISMGR.ZONING
Copyright Text: The data set was created by Analytical Surveys Incorporated (ASI) and Landata under contract to Fairfax County. Quality control checks were performed by Engineering Systems Incorporated and Dewberry and Davis. Staff from the GIS branch were also used for quality control checking. Since 2001 Fairfax County staff have been solely responsible for maintaining this data.
Description: This data layer is a polyline feature class which is typically captured using the Fairfax County Road Centerline layer. Each roadway record has a MSMD Program value assigned to it (Service Drive, FCRMIP, Chapter 2) which determines the maintenance designation. Any associated plans and land record documents are referenced in the layer and accessible within the county network.This data layer replaces two previous layers (STW_SERVICE_DRIVES, STW_FCRMIP_ROADS) which were merged into a single road inventory layer. This was completed as part of a county roadway inventory and assessment project completed with the help of Rinker Design Associates under the direction of the MSMD.Contact: DPWES GIS Services - DPWES-GISSolutions@fairfaxcounty.govData Accessibility: PublicUpdate frequency: As neededCreation date: 8/1/2017Layer name: STWMGR.STW_ROADSDataset name: STWMGR.STW_TRANSPORTATION
Description: The SDID Inspection Areas feature class is maintained by LDS, SDID and is updated corresponding to any changes in the inspection areas. SDID Inspection Areas are divided up into three distinct polygons based off Supervisor Districts. Contact: Land Development Services, Brett MartinData Accessibility: PublicUpdate frequency: MonthlyCreation date: 04/19/2019Feature Class: LDSAMGR.SDID_INSPECTION_AREAS
Copyright Text: Fairfax County, Land Development Services
Description: Contact: Fairfax County Department of Planning and Development IT and Graphics SectionData Accessibility: Internal Use OnlyUpdate Frequency: As NeededCreation Date: 7/23/2020Layer Name: DPDMGR.COMMUNITY_REVIT_INTEREST_AREAS
Copyright Text: Fairfax County Department of Planning and Development Community Revitalization Section
Description: The feature class contains discrete polygons representing the boundaries of Fairfax Water Authority and the Town of Vienna’s Water Service Areas. provided by the Fairfax Water Authority and Town of Vienna in August 2020.Contact: Land Development ServicesData Accessibility: Publicly AvailableUpdate Frequency: As NeededLast Revision Date: 8/21/2020Creation Date: 8/21/2020Layer Name: LDSA.WATER_SERVICE_AREA
Copyright Text: Fairfax County, Virginia; Land Development Services; Town of Vienna; Fairfax Water Authority
Description: The boundary lines for soils. The soil boundaries are for general planning purposes. Soils lines are not definitive. Soils gradually phase into one another. Characteristics of neighboring soils types will be found within a soil's borders. The code for the soil type is attributed to the area. This data must be included on all plans submitted for permits (site plans, grading plans, etc.) and must be used as the basis for whatever engineering tests are required before a construction permit can be issued.Contact: Northern Virginia Soil & Water Conservation DistrictData Accessibility: Publicly available Update frequency: As needed Creation date: 11/17/2015Layer name: NVSWDCMGR.SOIL_LINES
Copyright Text: Northern Virginia Soil & Water Conservation District
Description: This layer contains the soil boundaries based on the 1990 soil survey. There are large areas of Fairfax County that were not included in the 1990 soil survey and therefore do not have soil map unit values. The soil map unit descriptions are available at https://www.fairfaxcounty.gov/landdevelopment/soil-map-unit-descriptions.Contact: Northern Virginia Soil & Water Conservation DistrictData Accessibility: Publicly available Update frequency: NeverCreation date: 1/1/2001 Layer name: NVSWCDMGR.SOILSDataset name: NVWSCDMGR.SOILS
Copyright Text: Northern Virginia Soil & Water Conservation District
Description: Contact: Fairfax County Department of Planning and DevelopmentData Accessibility: Internal Use Only and disseminated to the public through web GIS applicationsUpdate frequency: As needed; This layer is updated by DPD as the BOS authorizes and adopts amendments.Creation date: 12/13/2013Layer name: DPZMGR.PLAN_AMENDMENT_DATABASEDataset name: DPZMGR.COMP_PLAN_AMENDMENTSField Definitions:Type:This refers to the type of amendment – Area Plans Review (APR), Out-of-turn Plan amendment (OTPA), special study (ST), work program item (W), Site-Specific Plan Amendment (SSPA)Spvr_Dist:Supervisor districts included in the amendment. Note that over time, district boundaries have changed…amendments are classified based upon the district they were located in at the time of authorizationAdopt_Num:Adopted text number (if adopted)Authorized:Date when the BOS authorized a proposed amendment to the Comprehensive Plan. This means the BOS directed county staff to begin the study and analysis of a proposed amendment, it does not mean the amendment was incorporated into the Plan.Adopted:Date when a proposed amendment to the Plan was adopted by the BOS and formally incorporated into the Comprehensive Plan text and map.Purpose:General characterization of the amendment topic. Most are Land use/Int (land use or intensity change proposed) but the amendments cover a wide variety of topics. Many studies cover multiple policy areas, but are categorized as Land use/Int if a primary purpose of the amendment was to change land use recommendations. This is distinguished from Land Use Related, which recognizes amendments where recommendations or conditions were proposed to be changed, but did not involve a change in land use or density/intensity.Acres_Log:The “official” acreage noted in the staff report at the time of the amendment. Not all amendments have had an official acreage associated with them.Cycle:Refers to the APR or SSPA cycle for an item, or in the case of current work program items, the year in which the item was added to the work program.Item_Num:The number assigned to each Plan amendment. If this says “pending” it is an item currently on the work program that is not yet underway.Notes:For APR or SSPA items, this is where the nominator is listed. For OTPAs and studies, the Supervisor who made the motion to authorize the amendment is listed. There may be additional miscellaneous information in this field, such as related amendments, as is warranted.Name:The name of the amendment or study. This is generally only found for ST, OTPA, SSPA, and W items.Outcome:The outcome of the item. This is generally straightforward, except in instances where items have been deferred or rescinded. Any item with a second item in parentheses means a second action was taken after the first. The second action is in parentheses. Temp_num:This is an internal number used to document work program items that have not yet commenced. The only real purpose of this number is for recordkeeping, so you likely won’t be concerned with it.Acres_gis:Acres as calculated in GIS. Since all mapping projections have some inherent distortion, this is not an exact acreage. This figure is the area of the item’s polygon, which may include some right-of-way. This has been calculated so that for items without a value in Acres_Log, you can still get a general idea of the amendment size.Mapped:Many of the amendments in this database cover quite a large area. Some cover the whole county. They have all been given a shape so that we can account for them in this file, but you may find that the presence of these larger amendments obscures some of the smaller, site-specific amendments you may be researching. Amendments labeled as “yes” tend to be smaller and account for land use and intensity/density changes, while those labeled as “no” are larger in size and tend to be related to policy topics or editorial updates. This field allows you to query out the geographically larger amendments so that they don’t, for lack of a better phrase, get in your way. Of course, you can symbolize this layer however you want, which will allow you show the locations or types of amendments most relevant to you.FFMAP:YES=current item which appears on DPZ interactive Web maps. NO=current item whose character (typically Countywide, Editorial, or Policy) is such that it cannot be mapped on DPZ interactive Web maps, or recent item which was shown on the DPZ interactive Web maps, but is no longer current and has been removed. <Null>=not shown on DPZ interactive Web maps because item predates Web map and item is resolved. ?=will be mapped and shown on DPZ interactive Web maps as soon as location can be determined.
Copyright Text: Marshall Keeney; Fairfax County Department of Planning & Development; Originally compiled by DPD Planning Division.
Description: This layer contains the definitive boundaries of Fairfax County's: Urban Center, Suburban Centers, Community Business Centers, Transit Station Areas, Industrial Areas, and Large Institutional Land Areas as defined in the Concept for Future Development map that appears in the Comprehensive Plan Area Plan texts. THIS LAYER HAS BEEN UPDATED TO MARCH 6, 2018, to include boundary changes in Plan Amendment 2017-07, which added Lincolnia CBC.RELATED LAYERS - Two other types of place: Suburban Neighborhoods and Low Density Residential Areas are depicted on a separate SDE layer, DPZMGR:RESIDENTIAL_AREAS_CONCEPTUAL See also the layer: DPZMGR.SUPPPLEMENTARY_PLANNING_AREAS for additional bounded planning-related areas.Contact: Fairfax County Department of Planning & DevelopmentData Accessibility: Publicly available to Fairfax County Employees and represented to citizens and the public through several GIS applications.Update Frequency: PERIODICCreation Date: UNKOWNFeature Layer Name: DPZMGR.DEVELOPMENT_CENTERSFeature Set Name: DPZMGR.PLANNING
Copyright Text: Department of Planning and Development
Description: This dataset is a selection of known erosion and flooding problems throughout the County. The data is intended primarily to assist site plan preparers with establishing the existence of known erosion and flooding problems. Increased volumes of sheet flow that will cause or contribute to erosion, sedimentation, or flooding of down gradient properties or resources shall be diverted to a stormwater management facility or a stormwater conveyance system that conveys the runoff without causing down-gradient erosion, sedimentation, or flooding per Stormwater Management Ordinance 124-4-4.E. Minimum Standard (MS) 19 of the Virginia Erosion and Sediment Control Regulations (9VAC25-840-40.19) requires stormwater discharge from permitted projects be diverted to an adequate conveyance or detention facility.This data documents known inadequacies in the stormwater conveyance system. Plan preparers should and County staff will use this information when evaluating compliance with requirements to discharge storm water to an adequate system or detention facility.The erosion and flooding problems identified in the layer were determined using the following county datasets: -Stream Physical Assessment 1.0 Erosion -Stream Physical Assessment 1.0 Reach Habitat-Stream Physical Assessment 1.0 Head Cuts -Stream Physical Assessment 2.0 -Open Channel Inspections Contact: Land Development ServicesData Accessibility: Publicly AvailableUpdate Frequency: As NeededLast Revision Date: 9/212021Creation Date: 9/21/2021Layer Name: LDSAMGR.INADEQUATE_OUTFALLS
Copyright Text: Fairfax County, Virginia; Land Development Services
Description: Zoning Applications in Fairfax County. These applications are coordinated through the Zoning Evaluation Division with-in the department of Planning & Development.Contact: Fairfax County Department of Planning & DevelopmentData Accessibility: Publicly available to Fairfax County Employees and represented to citizens and the public through a number of GIS applications.Update Frequency: WeeklyCreation Date: 2009Feature Layer Name: DPZMGR.APPLICATIONS_ZEDFeature Set Name: DPZMGR.ZONING_APPLICATIONS
Copyright Text: Daniel White
Fairfax County Department of Planning & Development
Description: This layer contains polygons defining the boundaries of several named “areas” which are described in the Comprehensive Plan text. RELATED LAYERS - Two other types of place: Suburban Neighborhoods and Low Density Residential Areas are depicted on a separate SDE layer, DPZMGR:RESIDENTIAL_AREAS_CONCEPTUAL See also the layer: DPZMGR.DEVELOPMENT_CENTERSfor additional bounded planning-related areas.Contact: Fairfax County Department of Planning & DevelopmentData Accessibility: Publicly available to Fairfax County Employees and represented to citizens and the public through several GIS applications.Update Frequency: RARELYCreation Date: 2000Feature Layer Name: DPZMGR.SUPPLEMENTARY_PLANNING_AREASFeature Set Name: DPZMGR.PLANNING
Copyright Text: Maintained by the Department of Planning & Development
Description: This data set contains a variety of easements that are captured from recorded subdivision plats and easement plats. Once a document has been recorded then the GIS office receives that document and creates any features that are shown on the recorded document. This layer contains the easement type by category and the name of the easement as stated on the plat. For newer easements there is also the deed book and deed page. This is used to perform research on the original document in the Courts system.This layer does not contain all easements. There are many easements before the GIS office started capturing all easements that did not get into the layer because they were not on the original mylars where this data was captured from. Also, in 2016 the GIS Division stopped capturing stormwater easements into this layer as there is different layer that contains the stormwater related easements.Contact: Fairfax County GIS DivisionData Accessibility: Publicly availableUpdate frequency: DailyLast Revision date: 1/1/2000Creation date: 1/1/2000Feature Dataset Name: GISMGR.ENCUMBRANCESLayer name: GISMGR.EASEMENTS
Copyright Text: Fairfax County, Virginia; Fairfax County Department of Information Technology GIS Division; The data set was created by Analytical Surveys Incorporated (ASI) and Landata under contract to Fairfax County. Quality control checks were performed by Engineering Systems Incorporated and Dewberry and Davis. Staff from the GIS branch were also used for quality control checking. Since 2001 Fairfax County staff have been solely responsible for maintaining this data.
Description: The Fairfax County Stormwater Easement feature dataset includes two GIS feature classes, STW_EASEMENT_POLYGONS & STW_EASEMENT_COGOLINES. These feature classes were generated from extensive plat research to derive metes & bounds to then create all easements determined to be related to stormwater management. All easements are contained within the Fairfax County boundary. The project began in the Spring of 2005 and remains in production.
Copyright Text: Fairfax County, Virginia; DPWES GIS Services
Description: Zoning Applications in Fairfax County. These applications are coordinated through the Zoning Evaluation Division with-in the department of Planning & Development.Contact: Fairfax County Department of Planning & DevelopmentData Accessibility: Publicly available to Fairfax County Employees and represented to citizens and the public through a number of GIS applications.Update Frequency: WeeklyCreation Date: 2009Feature Layer Name: DPZMGR.APPLICATIONS_ZEDFeature Set Name: DPZMGR.ZONING_APPLICATIONS
Copyright Text: Daniel White
Fairfax County Department of Planning & Development