Name: POPPROJECTION_POINTS
Display Field: DEVELOPMENT_NAME
Type: Feature Layer
Geometry Type: esriGeometryPoint
Description: These geospatial models were built using property parcel data from county property appraisers. These data include the property parcel boundaries and attributes that indicate the property use, the number of residential units, the year the residences were built, and the lot size. To this we added data from other sources that enabled us to project maximum development potential (or "build-out") at the parcel level, including:-Population, average household size and average occupancy from the 1990, 2000, 2010 and 2020 decennial censuses-Future land use classification and unit densities from local government future land use maps-Surface water and wetlands-Land uses where future development is restricted-Planned development boundaries and approved residential units-Political, natural or other boundaries needed for summarizing the results (cities, utility boundaries, etc.)Using this "Build-out Submodel", we also estimated 2024 population. We applied average household size and occupancy metrics from the 2020 Census to the parcel-level residential unit estimates provided by the county property appraisers. We then added population in group quarters (e.g., nursing homes, college dormitories, prisons, etc.) and made minor adjustments to control the current population to 2024 BEBR county population estimates.To project future growth, we began by calculating historic growth trends. These were based on tract-level data from the 1990, 2000, 2010, and 2020 censuses. These data were used to produce 11tract-level projections using five different demographic extrapolation methods over multiple base periods. The length of the base was adjusted to roughly match the length of the projection horizon, so for a 20-year horizon, 20 years of historical data were used to establish the growth trends. The number of trend calculations varied based on the length of the base period used, and the highest and lowest calculations were discarded to moderate the effects of extreme projections. The remaining projections were then averaged.In addition to historic growth trends, spatial features can influence future growth. For that reason, we determined the historical relationship between residential development over the past 20 years and its proximity to the following features:-Roads and interchanges prioritized by level of use (with each road type modeled separately)-Existing residential development-Existing commercial development (based on parcels with specific commercial land use codes deemed attractors to residential growth)-Coastal and inland waters-Planned developmentsThe results of multiple logistic regressions were combined into a single "Growth Drivers Submodel" extending beyond the area to be projected to eliminate edge effects. The values were reclassified from 1 to100, with 100 indicating the highest likelihood for development.Projections were made in 5-year increments to the year 2050 (2025, 2030, 2035, 2040, 2045, and 2050). For each tract, the projections derived from the growth trends were distributed to parcels with the highest driver values first and limited to the maximum development potential from the Build-out Submodel. This cap was based on the land available for residential development, the recent historical densities for which each land use in each jurisdiction have developed, and development plans. Once this was done for all tracts in a county, the total of this preliminary county growth was compared against the published BEBR forecasted growth beyond 2024 for that time period. While the projected growth was typically close to the published county growth forecast, the growth was adjusted to match the county growth exactly. For downward adjustments, the growth was typically reduced for all tracts in proportion to their growth over the period. For upward adjustments, we use the Growth Drivers Submodel to identify groups of parcels with the highest relative probability for development. These upward adjustments were more common as we moved further away from the current year, as more areas that are currently growing reached their maximum capacity. Finally, the parcel-level estimates and projections were summarized by water service areas to support water supply planning and permitting for SWFWMD.
Copyright Text: BEBR, GISA Inc., SWFWMD
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 500000
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:
XMin: 287531.5184457451
YMin: 836089.6362602413
XMax: 997080.7430452444
YMax: 1912278.4513979927
Spatial Reference: 2882
(2882)
Drawing Info:
Renderer:
Simple Renderer:
Symbol: Style: esriSMSCircle
Color: [153, 64, 116, 255]
Size: 4.0
Angle: 0.0
XOffset: 0
YOffset: 0
Outline:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
-
OBJECTID
(
type: esriFieldTypeOID, alias: OBJECTID
)
-
Shape
(
type: esriFieldTypeGeometry, alias: Shape
)
-
PARCEL_NUM
(
type: esriFieldTypeString, alias: PARCEL_NUM, length: 50
)
-
BO_ID
(
type: esriFieldTypeInteger, alias: BO_ID
)
-
GEOID20
(
type: esriFieldTypeString, alias: GEOID20, length: 15
)
-
COUNTY
(
type: esriFieldTypeString, alias: COUNTY, length: 30
)
-
DISTRICT
(
type: esriFieldTypeString, alias: DISTRICT, length: 8
)
-
SVCAREAID
(
type: esriFieldTypeDouble, alias: SVCAREAID
)
-
DRY_ACRES
(
type: esriFieldTypeDouble, alias: DRY_ACRES
)
-
DEVELOPMENT_NAME
(
type: esriFieldTypeString, alias: DEVELOPMENT_NAME, length: 80
)
-
LU_CURRENT
(
type: esriFieldTypeString, alias: LU_CURRENT, length: 30
)
-
DRIVER
(
type: esriFieldTypeDouble, alias: DRIVER
)
-
FLU_BO
(
type: esriFieldTypeString, alias: FLU_BO, length: 110
)
-
POP_BO_P
(
type: esriFieldTypeDouble, alias: POP_BO_P
)
-
POP24
(
type: esriFieldTypeDouble, alias: POP24
)
-
POP25
(
type: esriFieldTypeDouble, alias: POP25
)
-
POP30
(
type: esriFieldTypeDouble, alias: POP30
)
-
POP35
(
type: esriFieldTypeDouble, alias: POP35
)
-
POP40
(
type: esriFieldTypeDouble, alias: POP40
)
-
POP45
(
type: esriFieldTypeDouble, alias: POP45
)
-
POP50
(
type: esriFieldTypeDouble, alias: POP50
)
-
POP24_P
(
type: esriFieldTypeDouble, alias: POP24_P
)
-
POP25_P
(
type: esriFieldTypeDouble, alias: POP25_P
)
-
POP30_P
(
type: esriFieldTypeDouble, alias: POP30_P
)
-
POP35_P
(
type: esriFieldTypeDouble, alias: POP35_P
)
-
POP40_P
(
type: esriFieldTypeDouble, alias: POP40_P
)
-
POP45_P
(
type: esriFieldTypeDouble, alias: POP45_P
)
-
POP50_P
(
type: esriFieldTypeDouble, alias: POP50_P
)
-
PERMSEAS24
(
type: esriFieldTypeDouble, alias: PERMSEAS24
)
-
PERMSEAS25
(
type: esriFieldTypeDouble, alias: PERMSEAS25
)
-
PERMSEAS30
(
type: esriFieldTypeDouble, alias: PERMSEAS30
)
-
PERMSEAS35
(
type: esriFieldTypeDouble, alias: PERMSEAS35
)
-
PERMSEAS40
(
type: esriFieldTypeDouble, alias: PERMSEAS40
)
-
PERMSEAS45
(
type: esriFieldTypeDouble, alias: PERMSEAS45
)
-
PERMSEAS50
(
type: esriFieldTypeDouble, alias: PERMSEAS50
)
-
POP24_T
(
type: esriFieldTypeDouble, alias: POP24_T
)
-
POP25_T
(
type: esriFieldTypeDouble, alias: POP25_T
)
-
POP30_T
(
type: esriFieldTypeDouble, alias: POP30_T
)
-
POP35_T
(
type: esriFieldTypeDouble, alias: POP35_T
)
-
POP40_T
(
type: esriFieldTypeDouble, alias: POP40_T
)
-
POP45_T
(
type: esriFieldTypeDouble, alias: POP45_T
)
-
POP50_T
(
type: esriFieldTypeDouble, alias: POP50_T
)
-
POP24_NC
(
type: esriFieldTypeDouble, alias: POP24_NC
)
-
POP25_NC
(
type: esriFieldTypeDouble, alias: POP25_NC
)
-
POP30_NC
(
type: esriFieldTypeDouble, alias: POP30_NC
)
-
POP35_NC
(
type: esriFieldTypeDouble, alias: POP35_NC
)
-
POP40_NC
(
type: esriFieldTypeDouble, alias: POP40_NC
)
-
POP45_NC
(
type: esriFieldTypeDouble, alias: POP45_NC
)
-
POP50_NC
(
type: esriFieldTypeDouble, alias: POP50_NC
)
-
ORIG_FID
(
type: esriFieldTypeInteger, alias: ORIG_FID
)
Supported Operations:
Query
Query Attachments
Query Analytic
Generate Renderer
Return Updates
Iteminfo
Thumbnail
Metadata