Orlando Planning Land Use

Orlando Planning Land Use

The html maps are provided as supplementary information for the publication titled Parcel Scale Assessment of Rooftop Solar Technical Potential (NREL/PR-7A40-80780). The maps contain information on rooftop solar technical potential at the block scale for the city of Orlando in Florida. The rooftop solar technical potential information is based on data from two different datasets. The first dataset is LiDAR data for the city of Orlando obtained from the Orlando Utilities Commission (OUC) (Koebrich et al. 2021). The second dataset is a national parcel dataset (HIFLD 2020) which contains descriptive data and geometries for parcels in the U.S. Parcel scale data from both these datasets have been processed and aggregated to block scale to produce these html maps. The first html map (block scale developable roof area for Orlando) contains the developable roof area for solar. The second html map (block scale rooftop solar technical potential for Orlando) contains the rooftop solar technical potential in units of kilowatts as well as additional information on the most common building use type and the most common building occupancy type for the block. These html maps are provided to demonstrate the proof-of-concept analysis conducted for Orlando.

Orlando Planning Boards: Zoning Determination, BZA, MPB, BPTD, SETD

Orlando Planning Land Use

Orlando Downtown Entertainment Area

Orlando Planning Land Use

The Surficial Aquifer System (SAS) depth to water table surface grid was created by subtracting the water table surface grid from the DEM.

This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries. Please reference the metadata for contact information.

District Boundaries adopted by City Council 6/20/2022, Doc# 2206201202 Effective for Term beginning 10/01/2022