ArcGIS REST Services Directory Login | Get Token
Home > services > PLUS > PlanningMap (MapServer) > Pending Comprehensive Plan Amendment Help | API Reference
JSON

Layer: Pending Comprehensive Plan Amendment (ID: 14)

Name: Pending Comprehensive Plan Amendment

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

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.

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata