FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION VERSION 2006 TITLE: DEVELOPMENTS OF REGIONAL IMPACT - 2006 QUARTER 2 Geodataset Name: DRI_DCA_2006Q2 Geodataset Type: Shapefile Geodataset Feature: POLYGON Feature Count: 1105 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): DCA and GeoPlan Center SCALE OF ORIGINAL SOURCE MAPS: VARIOUS DATE OF AUTOMATION OF SOURCE: 20060612 GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: DRI_DCA_2006Q2.DBF
ITEM NAME | WIDTH | TYPE |
FID
|
4 | OID |
Shape
|
0 | Geometry |
ADA_NO
|
10 | String |
PROJ_NAM
|
70 | String |
APP_DATE
|
8 | Date |
TRANS_COM
|
5 | String |
DEVELOPER
|
50 | String |
REGION
|
7 | String |
LOCAL_GOV
|
25 | String |
DO_STATUS
|
30 | String |
TYPE1
|
15 | String |
SIZE1
|
10 | Number |
CLASS1
|
10 | String |
TYPE2
|
15 | String |
SIZE2
|
10 | Number |
CLASS2
|
10 | String |
SOURCE
|
20 | String |
DESCRIPT
|
70 | String |
FGDLAQDATE
|
8 | Date |
AUTOID
|
6 | Number |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
FID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
ADA_NO |
DCA DRI Identification Number. |
|
PROJ_NAM |
DRI Name. |
|
APP_DATE |
DRI Application Date. |
|
TRANS_COM |
DRI Transportation Commitment. |
|
DEVELOPER |
DRI Developer Name. |
|
REGION |
The DCA Region the DRI falls within. |
|
LOCAL_GOV |
The Local Government boundary that the DRI falls within. |
|
DO_STATUS |
The Status of the Development Order of the DRI. The Development Order is the binding order which authorizes and formally approves the DRI. It is executed between the applicant and the local government. The DO spells out most, if not all, of the binding conditions that will be imposed upon the DRI and usually includes any separate agreements made to resolve specific regional issues. At a minimum, conditions of approval would include mitigation requirements, monitoring procedures, DO compliance, commencement and termination dates, requirements for the annual report, and a legal description of the property.
|
|
TYPE1 |
The primary land use type of the DRI.
|
|
SIZE1 |
The size of the primary land use type. |
|
CLASS1 |
The Class type of the primary DRI.
|
|
TYPE2 |
The secondary land use type of the DRI.
|
|
SIZE2 |
The size of the secondary land use type. |
|
CLASS2 |
The Class type of the secondary DRI.
|
|
SOURCE |
The DRI's data source for the spatial information. |
|
DESCRIPT |
Based on PROJ_NAME. |
|
FGDLAQDATE |
The date FGDL acquired the data from the source. |
|
AUTOID |
GeoPlan Center Internal Feature Number. |
|
|
A DRI is defined by Section 380.06(1), FS, as any development which, because of its character, magnitude or location, would have a substantial effect on the health, safety or welfare of citizens in more than one county. The state has established thresholds to determine when a development must undergo the DRI review process. These determinations are made by the Florida Department of Community Affairs (DCA) using Chapter 28-24, FAC. The Regional Planning Council (RPC) plays a primary role in the DRI process, coordinating the multi-agency review activities at the regional level and reviewing the application for consistency with adopted state and regional plans. The RPC will hold a public hearing for the adoption of a regional position on the application, which is then forwarded to the local government of jurisdiction for its consideration. The RPC is an advisory body to the local government and so does not approve or deny applications. The local planning agency (LPA) plays a lead role in the identification of local issues or concerns relative to the project and will take the recommended conditions of approval from the RPC and combine them with locally oriented conditions of approval in the construction of an overall development order. The local government's governing body will also conduct a public hearing on the project, at which time it will consider the reports of the RPC and LPA. It is the entity which ultimately approves or denies the authorization for the project to develop, through the issuance of a binding Development Order (DO). The datasets used to compile this shapefile were obtained by FGDL via phone and email requests to County Property Appraisers, Planning Departments, GIS departments, and Regional Planning Councils. Certain datasets were also downloaded from county websites when available. --------------------------------------------------------------------------- Because of a lack of existing spatial information for DRIs located in the Panhandle and the Treasure Coast regions, the GeoPlan Center, using 2004 parcel data, created DRI polygon boundaries from a variety of source information (Maps, Parcel Owner Information, Parcel Site Legal Description Information, etc). The following regional planning councils have the polygon information and it is currently under review, however, they have not as of yet signed off on the spatial information provided in this shapefile. - Treasure Coast Regional Planning Council - West Florida Regional Planning Council - Apalachee Regional Planning Council Polygons that have been digitized in house can be located through the [SOURCE] field where the source is equal to GeoPlan Center. |
|
|
|
|
|
|
|
A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:250000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html |
Developments of Regional Impact and Florida Quality Developments: http://www.dca.state.fl.us/fdcp/dcp/DRIFQD/index.cfm DEVELOPMENTS OF REGIONAL IMPACT DRI Status: View a list of the status of DRIs, Excel or PDF format. http://www.dca.state.fl.us/fdcp/dcp/Procedures/index.cfm Chapter 28-24 Florida Administrative Code Developments Presumed to be of Regional Impact. http://www.dca.state.fl.us/fdcp/dcp/publications/statutesruleslegis/28-24.wpd.pdf ------------------------------------------------------ Florida Regional Planning Councils Apalachee: http://thearpc.com/ Central Florida: http://www.cfrpc.org/ East Central Florida: http://www.ecfrpc.org/Main/Main.asp North Central Florida: http://ncfrpc.org/ Northeast Florida: http://www.nefrpc.org/ South Florida: http://www.sfrpc.com/ Southwest Florida: http://www.swfrpc.org/ Tampa Bay: http://www.tbrpc.org/ Treasure Coast: http://www.tcrpc.org/ West Florida: http://www.wfrpc.dst.fl.us/ Withlacoochee: http://www.wrpc.cc/ |
UF GeoPlan Center compiled this dataset from various sources. Attribute information for DRI's came from Florida DCA. Polygon boundaries for individual DRI's came from a variety of sources, including Regional Planning Councils, and County Governments. For DRI's without existing polygon boundaries, the GeoPlan Center digitized polygons using parcel boundaries, owner information, parcel legal descriptions, and DRI boundary descriptions. Polygon boundaries were downloaded or received via email from various sources. The boundaries were first reprojected to FGDL Albers. Then individual DRI datasets were merged into one dataset. GeoPlan downloaded a spreadsheet (adastatlist.xls) of DRI attribute information from the FDCA website: http://www.dca.state.fl.us/fdcp/dcp/Procedures/index.cfm. The spreadsheet was converted to a DBF table. DRI polygons were spatially identified using information from the DCA table and added the corresponding DCA ADA number was added to each polygon. Performed a table join between the statewide polygon DRI layer and the DCA table, based on the DRI's ADA number (ADA_NO field). -DESCRIPT item was added based on the item PROJ_NAME. -Added SOURCE field and calculated it to represent the source of each of the polygons. -Added FGDLAQDATE and calculated it to the date the information was received. -Added AUTOID. -Moved DESCRIPT item to the end of table. Process Date: 20060612 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
Department of Community Affairs - Division of Community Planning DCA 2555 Shumard Oak Boulevard Tallahassee, Florida 32399-2100 (850) 487-4545 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html