Download In State Plane Projection Here The 2024 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2024 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

The Virginia Geographic Information Network (VGIN) has coordinated the development and maintenance of a statewide Parcels data layer in conjunction with local governments across the Commonwealth. The Virginia Parcel dataset is aggregated as part of the VGIN Local Government Data Call update cycle. Localities are encouraged to submit data bi-annually and are included into the parcel dataset with their most recent geography.These tables are to be used in conjunction with theVirginia Parcel Datasetmost recent download to receive additional attribution beyond Map Number and Parcel ID. They are joined to the Parcel geography using the VGIN_QPID attribute on the Parcel feature class and local schema table. Attributes differ from locality to locality and what is provided in the geodatabase is a tabular representation of the geospatial attributes provided from the jurisdiction to VGIN with bi-annual data calls. Locality tables have the last received and processed date appended to the table name.If you have questions about attributes and usability of each schema set, please contact the jurisdiction"s GIS coordinator at theLocal GIS Contacts Page.GDB Version: ArcGIS Pro 3.3Additional Resources:Statewide Parcel Dataset

Geostatistics analyzes and predicts the values associated with spatial or spatial-temporal phenomena. It incorporates the spatial (and in some cases temporal) coordinates of the data within the analyses. It is a practical means of describing spatial patterns and interpolating values for locations where samples were not taken (and measures the uncertainty of those values, which is critical to informed decision making). This archive contains results of geostatistical analysis of COVID-19 case counts for all available US counties. Test results were obtained with ArcGIS Pro (ESRI). Sources are state health departments, which are scraped and aggregated by the Johns Hopkins Coronavirus Resource Center and then pre-processed by MappingSupport.com.

This update of the Zenodo dataset (version 6) consists of three compressed archives containing geostatistical analyses of SARS-CoV-2 testing data. This dataset utilizes many of the geostatistical techniques used in previous versions of this Zenodo archive, but has been significantly expanded to include analyses of up-to-date U.S. COVID-19 case data (from March 24th to September 8^th, 2020):

Archive #1: “1.Geostat. Space-Time analysis of SARS-CoV-2 in the US (Mar24-Sept6).zip” – results of a geostatistical analysis of COVID-19 cases incorporating spatially-weighted hotspots that are conserved over one-week timespans. Results are reported starting from when U.S. COVID-19 case data first became available (March 24^th, 2020) for 25 consecutive 1-week intervals (March 24th through to September 6th, 2020). Hotspots, where found, are reported in each individual state, rather than the entire continental United States.

Archive #2: "2.Geostat. Spatial analysis of SARS-CoV-2 in the US (Mar24-Sept8).zip" – the results from geostatistical spatial analyses only of corrected COVID-19 case data for the continental United States, spanning the period from March 24^th through September 8th, 2020. The geostatistical techniques utilized in this archive includes ‘Hot Spot’ analysis and ‘Cluster and Outlier’ analysis.

Archive #3: "3.Kriging and Densification of SARS-CoV-2 in LA and MA.zip" – this dataset provides preliminary kriging and densification analysis of COVID-19 case data for certain dates within the U.S. states of Louisiana and Massachusetts.

These archives consist of map files (as both static images and as animations) and data files (including text files which contain the underlying data of said map files [where applicable]) which were generated when performing the following Geostatistical analyses: Hot Spot analysis (Getis-Ord Gi*) [‘Archive #1’: consecutive weeklong Space-Time Hot Spot analysis; ‘Archive #2’: daily Hot Spot Analysis], Cluster and Outlier analysis (Anselin Local Moran's I) [‘Archive #2’], Spatial Autocorrelation (Global Moran's I) [‘Archive #2’], and point-to-point comparisons with Kriging and Densification analysis [‘Archive #3’].

The Word document provided ("Description-of-Archive.Updated-Geostatistical-Analysis-of-SARS-CoV-2 (version 6).docx") details the contents of each file and folder within these three archives and gives general interpretations of these results.

Laatste update: 23 september 2024

The Wind Integration National Dataset (WIND) Toolkit, developed by the National Renewable Energy Laboratory (NREL), provides modeled wind speeds at multiple elevations. Instantaneous wind measurements were analyzed from more than 126,000 sites in the continental United States for the years 2007–2013. The model results were mapped on a 2-km grid. A subset of the contiguous United States data for 2012 is shown here. Offshore data is shown to 50 nautical miles.Time Extent: Annual 2012Units: m/sCell Size: 2 kmSource Type: StretchedPixel Type: 32 Bit FloatData Projection: GCS WGS84Mosaic Projection:  WGS 1984 Web MercatorExtent: Contiguous United StatesSource: NREL Wind Integration National Dataset v1.1WIND is an update and expansion of the Eastern Wind Integration Data Set and Western Wind Integration Data Set. It supports the next generation of wind integration studies.Accessing Elevation InformationEach of the 9 elevation slices can be accessed, visualized, and analyzed. In ArcGIS Pro, go to the Multidimensional Ribbon and use the Elevation pull-down menu. In ArcGIS Online, it is best to use Web Map Viewer Classic where the elevation slider will automatically appear on the righthand side. The elevation slider will be available in the new Map Viewer in an upcoming release. What can you do with this layer?This layer may be added to maps to visualize and quickly interrogate each pixel value. The pop-up provides the pixel’s wind speed value.This analytical imagery tile layer can be used in analysis. For example, the layer may be added to ArcGIS Pro and proposed wind turbine locations can be used to Sample the layer at multiple elevation to determine the optimal hub height. Source data can be accessed on Amazon Web ServicesUsers of the WIND Toolkit should use the following citations:Draxl, C., B.M. Hodge, A. Clifton, and J. McCaa. 2015. Overview and Meteorological Validation of the Wind Integration National Dataset Toolkit (Technical Report, NREL/TP-5000-61740). Golden, CO: National Renewable Energy Laboratory.Draxl, C., B.M. Hodge, A. Clifton, and J. McCaa. 2015. "The Wind Integration National Dataset (WIND) Toolkit." Applied Energy 151: 355366.King, J., A. Clifton, and B.M. Hodge. 2014. Validation of Power Output for the WIND Toolkit (Technical Report, NREL/TP-5D00-61714). Golden, CO: National Renewable Energy Laboratory.

Author: Titus, Maxwell (mtitus@esri.com)Last Updated: 3/4/2025Intended Environment: ArcGIS ProPurpose: This Notebook was designed to automate updates for Hosted Feature Services hosted in ArcGIS Online (or ArcGIS Portal) from ArcGIS Pro and a spatial join of two live datasets.Description: This Notebook was designed to automate updates for Hosted Feature Services hosted in ArcGIS Online (or ArcGIS Portal) from ArcGIS Pro. An associated ArcGIS Dashboard would then reflect these updates. Specifically, this Notebook would:First, pull two datasets - National Weather Updates and Public Schools - from the Living Atlas and add them to an ArcGIS Pro map.Then, the Notebook would perform a spatial join on two layers to give Public Schools features information on whether they fell within an ongoing weather event or alert. Next, the Notebook would truncate the Hosted Feature Service in ArcGIS Online - that is, delete all the data - and then append the new data to the Hosted Feature ServiceAssociated Resources: This Notebook was used as part of the demo for FedGIS 2025. Below are the associated resources:Living Atlas Layer: NWS National Weather Events and AlertsLiving Atlas Layer: U.S. Public SchoolsArcGIS Demo Dashboard: Demo Impacted Schools Weather DashboardUpdatable Hosted Feature Service: HIFLD Public Schools with Event DataNotebook Requirements: This Notebook has the following requirements:This notebook requires ArcPy and is meant for use in ArcGIS Pro. However, it could be adjusted to work with Notebooks in ArcGIS Online or ArcGIS Portal with the advanced runtime.If running from ArcGIS Pro, connect ArcGIS Pro to the ArcGIS Online or ArcGIS Portal environment.Lastly, the user should have editable access to the hosted feature service to update.

Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations. Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals. Data from thegSSURGO databasewas used to create this layer. To download ready-to-use project packages of useful soil data derived from the SSURGO dataset, please visit the USA SSURGO Downloader app. Dataset Summary Phenomenon Mapped:Soils of the United States and associated territoriesGeographic Extent:The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaCoordinate System:Web Mercator Auxiliary SphereVisible Scale:1:144,000 to 1:1,000Source:USDA Natural Resources Conservation Service Update Frequency:AnnualPublication Date:December 2024 What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS Online Add this layer to a map in the map viewer. The layer is limited to scales of approximately 1:144,000 or larger but avector tile layercreated from the same data can be used at smaller scales to produce awebmapthat displays across the full scale range. The layer or a map containing it can be used in an application.Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections and apply filters. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Change the layer’s style and filter the data. For example, you could set a filter forFarmland Class= "All areas are prime farmland" to create a map of only prime farmland.Add labels and set their propertiesCustomize the pop-upArcGIS Pro Add this layer to a 2d or 3d map. The same scale limit as Online applies in ProUse as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of theLiving Atlas of the Worldthat provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Data DictionaryAttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them. Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units. Area SymbolSpatial VersionMap Unit Symbol Map Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field. Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability Rating Legend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field. Project Scale Survey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields. Survey Area VersionTabular Version Map Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field. Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - Presence Rating for Manure and Food Processing Waste - Weighted Average Component Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected. Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent Key Component Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r). Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence -

Both this geodatabase and its associated web map display the shoreline miles and water acres within the 88 ocean, coastal, and Great Lakes National Park units. The following feature classes are included: "WRD Shoreline Miles Update 2024": Existing shoreline products from federal, state, and NPS sources were visually assessed for each park unit and compared to reference imagery within ESRI ArcGIS Pro to determine the best available data. The resulting shoreline delineation for each park unit was reviewed by NPS park, regional, national, and/or Inventory and Monitoring Network staff, and manual adjustments were made as needed to accurately reflect the shoreline. "WRD Water Acres Update 2024": For park units located in marine settings, “water acres” refers to ocean, estuarine, and tidally influenced waters. For park units in the Great Lakes region, “water acres” refers to freshwater. For all park units, freshwater bodies such as lakes, ponds, and rivers that exist inland of the marine or Great Lake shoreline are excluded. "WRD Park Boundaries 2022": Data current as of December 2022, provided by NPS Land Resources Division (LRD) and accessible via NPS DataStore (with a few exceptions as noted within the attribute table).

A Geospatial Data Resource Site (GDRS) is a structured collection of GIS apps and data used as the data structure that supports the Minnesota Geospatial Commons (MGC) and MNDNR Quick Layers (for ArcGIS Pro and ArcMap). The GDRS Manager application allows anyone to create their own local GDRS, either to be shared on an organization's network drive or to use offline. There is no installation for the GDRSManager. Simply download the application and double-click the executable file to run it. Current version: 1.0.0.44

Use https://resources.gisdata.mn.gov/pub/gdrs as the source GDRS to access the full public data from the MGC. Copy everything or select which datasets you want to copy to a local GDRS destination. If you have disk space or download speed limiations, sorting the resources by size and unselecting the largest resources is a quick way to reduce the size of a the GDRS but still have access to most of the resources.

Once you have a GDRS set up, run the application again whenever you want to update existing datasets or add additional datasets. You can even keep your data current by scheduling automatic updates to run gdrsmanager.exe through a bat file. For your reference, a template bat file gdrsmanager_console.bat is included in the application download. Just make sure to update the bat file to include the path to your copy of GDRS Manager, and schedule the bat file to run as desired.

The application download includes a comprehensive help document, which you can also access separately here:
gdrsmanager_quicklayers_Pro_help.pdf
gdrsmanager_quicklayers_help.pdf (ArcMap)

This layer features special areas of interest (AOIs) that have been contributed to Esri Community Maps using the new Community Maps Editor app. The data that is accepted by Esri will be included in selected Esri basemaps, including our suite of Esri Vector Basemaps, and made available through this layer to export and use offline. Export DataThe contributed data is also available for contributors and other users to export (or extract) and re-use for their own purposes. Users can export the full layer from the ArcGIS Online item details page by clicking the Export Data button and selecting one of the supported formats (e.g. shapefile, or file geodatabase (FGDB)). User can extract selected layers for an area of interest by opening in Map Viewer, clicking the Analysis button, viewing the Manage Data tools, and using the Extract Data tool. To display this data with proper symbology and metadata in ArcGIS Pro, you can download and use this layer file.Data UsageThe data contributed through the Community Maps Editor app is primarily intended for use in the Esri Basemaps. Esri staff will periodically (e.g. weekly) review the contents of the contributed data and either accept or reject the data for use in the basemaps. Accepted features will be added to the Esri basemaps in a subsequent update and will remain in the app for the contributor or others to edit over time. Rejected features will be removed from the app.Esri Community Maps Contributors and other ArcGIS Online users can download accepted features from this layer for their internal use or map publishing, subject to the terms of use below.

The 2023 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2023 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

Coordinate system Update:Notably, this dataset will be provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection, instead of WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857) which is the coordinate system of the 2023 dataset and will remain in Connecticut State Plane moving forward.Ownership Suppression and Data Access:The updated dataset now includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name will be replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with suppressed ownership data, users should be aware that there was no "Suppression" field in the submission to verify specific details. This measure was implemented this year to help verify compliance with Suppression.New Data Fields:The new dataset introduces the "Land Acres" field, which will display the total acreage for each parcel. This additional field allows for more detailed analysis and better supports planning, zoning, and property valuation tasks. An important new addition is the FIPS code field, which provides the Federal Information Processing Standards (FIPS) code for each parcel’s corresponding block. This allows users to easily identify which block the parcel is in.Updated Service URL:The new parcel service URL includes all the updates mentioned above, such as the improved coordinate system, new data fields, and additional geospatial information. Users are strongly encouraged to transition to the new service as soon as possible to ensure that their workflows remain uninterrupted. The URL for this service will remain persistent moving forward. Once you have transitioned to the new service, the URL will remain constant, ensuring long term stability.For a limited time, the old service will continue to be available, but it will eventually be retired. Users should plan to switch to the new service well before this cutoff to avoid any disruptions in data access.The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2024 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually. These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on 10/31/2024 from data collected in 2023-2024. Data was processed using Python scripts and ArcGIS Pro, ensuring standardization and integration of the data.<p style='margin-top:0px; margin-bottom:1.5rem; font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helv

This layer contains route identifier shields that can be added on top of other layers within a map. The shields in this layer will dynamically draw based on the location and zoom scale of the map.Route identifier shields include:State RouteUS RouteInterstateFA RouteThis layer does not have an automatic refresh but will be updated manually as needed. Current data snap shot: 11/2022Notes:Service Type - ArcGis Pro on 08Location - 08 in the Complex\UDOT_Shields folder. Document name Shields.aprxPublished to 08 (Central) in the UDOT Folder. Service Name is Shields

Coordinate system Update:

Notably, this dataset will be provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection, instead of WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857) which is the coordinate system of the 2023 dataset and will remain in Connecticut State Plane moving forward.

Ownership Suppression and Data Access:
The updated dataset now includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name will be replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with suppressed ownership data, users should be aware that there was no "Suppression" field in the submission to verify specific details. This measure was implemented this year to help verify compliance with Suppression.

New Data Fields:
The new dataset introduces the "Land Acres" field, which will display the total acreage for each parcel. This additional field allows for more detailed analysis and better supports planning, zoning, and property valuation tasks. An important new addition is the FIPS code field, which provides the Federal Information Processing Standards (FIPS) code for each parcel’s corresponding block. This allows users to easily identify which block the parcel is in.

Updated Service URL:
The new parcel service URL includes all the updates mentioned above, such as the improved coordinate system, new data fields, and additional geospatial information. Users are strongly encouraged to transition to the new service as soon as possible to ensure that their workflows remain uninterrupted. The URL for this service will remain persistent moving forward. Once you have transitioned to the new service, the URL will remain constant, ensuring long term stability.

For a limited time, the old service will continue to be available, but it will eventually be retired. Users should plan to switch to the new service well before this cutoff to avoid any disruptions in data access.

The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2024 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually.

These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on 10/31/2024 from data collected in 2023-2024. Data was processed using Python scripts and ArcGIS Pro, ensuring standardization and integration of the data.

CAMA Notes:

The CAMA underwent several steps to standardize and consolidate the information. Python scripts were used to concatenate fields and create a unique identifier for each entry. The resulting dataset contains 1,353,595 entries and information on property assessments and other relevant attributes.

• CAMA was provided by the towns.

Spatial Data Notes:

Data processing involved merging the parcels from different municipalities using ArcGIS Pro and Python. The resulting dataset contains 1,290,196 parcels.

• No alteration has been made to the spatial geometry of the data.

• Fields that are associated with CAMA data were provided by towns.

• The data fields that have information from the CAMA were sourced from the towns’ CAMA data.

• If no field for the parcels was provided for linking back to the CAMA by the town a new field within the original data was selected if it had a match rate above 50%, that joined back to the CAMA.

• Linking fields were renamed to "Link".

• All linking fields had a census town code added to the beginning of the value to create a unique identifier per town.

• Any field that was not town name, Location, Editor, Edit Date, or a field associated back to the CAMA, was not used in the creation of this Dataset.

• Only the fields related to town name, location, editor, edit date, and link fields associated with the towns’ CAMA were included in the creation of this dataset. Any other field provided in the original data was deleted or not used.

• Field names for town (Muni, Municipality) were renamed to "Town Name".

The attributes included in the data:

• Town Name

• Owner

• Co-Owner

• Link

• Editor

• Edit Date

• Collection year – year the parcels were submitted

• Location

• Mailing Address

• Mailing City

• Mailing State

• Assessed Total

• Assessed Land

• Assessed Building

• Pre-Year Assessed Total

• Appraised Land

• Appraised Building

• Appraised Outbuilding

• Condition

• <span

Urban Tree Canopy Assessment. This was created using the Urban Tree Canopy Syracuse 2010 (All Layers) file HERE.The data for this map was created using LIDAR and other spatial analysis tools to identify and measure tree canopy in the landscape. This was a collaboration between the US Forest Service Northern Research Station (USFS), the University of Vermont Spatial Laboratory, and SUNY ESF. Because the full map is too large to be viewed in ArcGIS Online, this has been reduced to a vector tile layer to allow it to be viewed online. To download and view the shapefiles and all of the layers, you can download the data HERE and view this in either ArcGIS Pro or QGIS.Data DictionaryDescription source  USDA Forest ServiceList of values  Value 1 Description Tree CanopyValue 2 Description Grass/ShrubValue 3 Description Bare SoilValue 4 Description WaterValue 5 Description BuildingsValue 6 Description Roads/RailroadsValue 7 Description Other PavedField Class Alias Class Data type String Width 20Geometric objects  Feature class name landcover_2010_syracusecity Object type  complex Object count 7ArcGIS Feature Class Properties Feature class name landcover_2010_syracusecity Feature type  Simple Geometry type Polygon Has topology FALSE Feature count 7 Spatial index TRUE Linear referencing  FALSEDistributionAvailable format  Name ShapefileTransfer options  Transfer size 163.805Description Downloadable DataFieldsDetails for object landcover_2010_syracusecityType Feature Class Row count  7 Definition  UTCField FIDAlias FID Data type OID Width  4 Precision 0 Scale 0Field descriptionInternal feature number.Description source ESRIDescription of valueSequential unique whole numbers that are automatically generated.Field ShapeAlias Shape Data type Geometry Width 0 Precision 0 Scale 0Field description Feature geometry.Description source  ESRIDescription of values Coordinates defining the features.Field CodeAlias Code Data type Number Width 4Overview Description  Metadata DetailsMetadata language  English Metadata character set utf8 - 8 bit UCS Transfer FormatScope of the data described by the metadata  dataset Scope name  datasetLast update 2011-06-02ArcGIS metadata properties Metadata format ArcGIS 1.0 Metadata style North American Profile of ISO19115 2003Created in ArcGIS for the item 2011-06-02 16:48:35 Last modified in ArcGIS for the item 2011-06-02 16:44:43Automatic updates Have been performed Yes Last update 2011-06-02 16:44:43Item location history  Item copied or moved 2011-06-02 16:48:35 From T:\TestSites\NY\Syracuse\Temp\landcover_2010_syracusecity To \T7500\F$\Export\LandCover_2010_SyracuseCity\landcover_2010_syracusecity

Coordinate system Update:Notably, this dataset will be provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection, instead of WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857) which is the coordinate system of the 2023 dataset and will remain in Connecticut State Plane moving forward.Ownership Suppression and Data Access:The updated dataset now includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name will be replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with suppressed ownership data, users should be aware that there was no "Suppression" field in the submission to verify specific details. This measure was implemented this year to help verify compliance with Suppression.New Data Fields:The new dataset introduces the "Land Acres" field, which will display the total acreage for each parcel. This additional field allows for more detailed analysis and better supports planning, zoning, and property valuation tasks. An important new addition is the FIPS code field, which provides the Federal Information Processing Standards (FIPS) code for each parcel’s corresponding block. This allows users to easily identify which block the parcel is in.Updated Service URL:The new parcel service URL includes all the updates mentioned above, such as the improved coordinate system, new data fields, and additional geospatial information. Users are strongly encouraged to transition to the new service as soon as possible to ensure that their workflows remain uninterrupted. The URL for this service will remain persistent moving forward. Once you have transitioned to the new service, the URL will remain constant, ensuring long term stability.For a limited time, the old service will continue to be available, but it will eventually be retired. Users should plan to switch to the new service well before this cutoff to avoid any disruptions in data access.The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2024 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually. These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on 10/31/2024 from data collected in 2023-2024. Data was processed using Python scripts and ArcGIS Pro, ensuring standardization and integration of the data.CAMA Notes:The CAMA underwent several steps to standardize and consolidate the information. Python scripts were used to concatenate fields and create a unique identifier for each entry. The resulting dataset contains 1,353,595 entries and information on property assessments and other relevant attributes.CAMA was provided by the towns.Spatial Data Notes:Data processing involved merging the parcels from different municipalities using ArcGIS Pro and Python. The resulting dataset contains 1,290,196 parcels.No alteration has been made to the spatial geometry of the data.Fields that are associated with CAMA data were provided by towns.The data fields that have information from the CAMA were sourced from the towns’ CAMA data.If no field for the parcels was provided for linking back to the CAMA by the town a new field within the original data was selected if it had a match rate above 50%, that joined back to the CAMA.Linking fields were renamed to "Link".All linking fields had a census town code added to the beginning of the value to create a unique identifier per town.Any field that was not town name, Location, Editor, Edit Date, or a field associated back to the CAMA, was not used in the creation of this Dataset.Only the fields related to town name, location, editor, edit date, and link fields associated with the towns’ CAMA were included in the creation of this dataset. Any other field provided in the original data was deleted or not used.Field names for town (Muni, Municipality) were renamed to "Town Name".The attributes included in the data: Town Name OwnerCo-OwnerLinkEditorEdit DateCollection year – year the parcels were submittedLocationMailing AddressMailing CityMailing StateAssessed TotalAssessed LandAssessed BuildingPre-Year Assessed Total Appraised LandAppraised BuildingAppraised OutbuildingConditionModelValuationZoneState UseState Use DescriptionLand Acre Living AreaEffective AreaTotal roomsNumber of bedroomsNumber of BathsNumber of Half-BathsSale PriceSale DateQualifiedOccupancyPrior Sale PricePrior Sale DatePrior Book and PagePlanning RegionFIPS Code *Please note that not all parcels have a link to a CAMA entry.*If any discrepancies are discovered within the data, whether pertaining to geographical inaccuracies or attribute inaccuracy, please directly contact the respective municipalities to request any necessary amendmentsAdditional information about the specifics of data availability and compliance will be coming soon.If you need a WFS service for use in specific applications : Please Click Here

Abstract Built up area polygons represent where buildings are clustered together, such as urban areas. Layer can be used for activities such as monitoring urban grown, or responding to natural disasters. Product has been designed for AUSTopo - Australian Digital Topographic Map Series 250k. Built up area polygons designed for the AUSTopo - Australian Digital Topographic Map Series 250k. Feature class attributes include polygon area (in m2) and feature type (Builtup Area). This dataset provides valuable insights into the built environment of towns and cities, and serves as a crucial resource for urban planners, researchers, policymakers, and developers. Currency Date modified: 31 August 2023 Modification frequency: None Data extent Spatial extent North: -10.15° South: -43.44° East: 153.64° West: 113.42° Temporal extent From 1 January 2013 to 1 January 2018 Source information Catalog entry: Built Up Areas Dataset This dataset is generated from a publicly-available dataset: Bing Building Footprints, using the 'Delineate Built Up Area' tool in ArcGIS Pro. More information on the original source dataset can be found here. Lineage statement Dataset was generated by using the Bing Building Footprints of Australia (October 2020) dataset as an input. Built Up Area layer was created using the Delineate Built Up Areas tool in ArcGIS Pro in April 2023. This layer was produced as part of the update of AUSTopo - Australian Digital Topographic Map Series 250k. This dataset extracted on or before 4 SEPTEMBER 2023. This dataset has been projected from GDA2020 to Web Mercator as part of the Digital Atlas of Austalia project. Minor changes to symbology have been performed only as neccessary to meet the requirements of this project. Data dictionary All layers

Attribute name Description

Object ID Unique identifier for the area polygon

Area (sq. m) Measured area of the built-up region

Feature Type All features in this set are "Builtup Area"

SHAPE_Length Internal - length of the polygon perimeter

SHAPE_Area Internal - area of the generated polygon

Contact Geoscience Australia, clientservices@ga.gov.au

Urban Tree Canopy Assessment. Created using LIDAR and other spatial analysis tools to identify and measure tree canopy in the landscape. This was a collaboration between the US Forest Service Northern Research Station (USFS), the University of Vermont Spatial Laboratory, and SUNY ESF. Includes all layers, but is too large to be viewed in ArcGIS Online. To view all of the layers, you can download the data and view this in either ArcGIS Pro or QGIS.Data DictionaryDescription source  USDA Forest ServiceList of values  Value 1 Description Tree CanopyValue 2 Description Grass/ShrubValue 3 Description Bare SoilValue 4 Description WaterValue 5 Description BuildingsValue 6 Description Roads/RailroadsValue 7 Description Other PavedField Class Alias Class Data type String Width 20Geometric objects  Feature class name landcover_2010_syracusecity Object type  complex Object count 7ArcGIS Feature Class Properties Feature class name landcover_2010_syracusecity Feature type  Simple Geometry type Polygon Has topology FALSE Feature count 7 Spatial index TRUE Linear referencing  FALSEDistributionAvailable format  Name ShapefileTransfer options  Transfer size 163.805Description Downloadable DataFieldsDetails for object landcover_2010_syracusecityType Feature Class Row count  7 Definition  UTCField FIDAlias FID Data type OID Width  4 Precision 0 Scale 0Field descriptionInternal feature number.Description source ESRIDescription of valueSequential unique whole numbers that are automatically generated.Field ShapeAlias Shape Data type Geometry Width 0 Precision 0 Scale 0Field description Feature geometry.Description source  ESRIDescription of values Coordinates defining the features.Field CodeAlias Code Data type Number Width 4Overview Description  Metadata DetailsMetadata language  English Metadata character set utf8 - 8 bit UCS Transfer FormatScope of the data described by the metadata  dataset Scope name  datasetLast update 2011-06-02ArcGIS metadata properties Metadata format ArcGIS 1.0 Metadata style North American Profile of ISO19115 2003Created in ArcGIS for the item 2011-06-02 16:48:35 Last modified in ArcGIS for the item 2011-06-02 16:44:43Automatic updates Have been performed Yes Last update 2011-06-02 16:44:43Item location history  Item copied or moved 2011-06-02 16:48:35 From T:\TestSites\NY\Syracuse\Temp\landcover_2010_syracusecity To \T7500\F$\Export\LandCover_2010_SyracuseCity\landcover_2010_syracusecity

The Federal Emergency Management Agency (FEMA) produces Flood Insurance Rate maps and identifies Special Flood Hazard Areas as part of the National Flood Insurance Program's floodplain management. Special Flood Hazard Areas have regulations that include the mandatory purchase of flood insurance for holders of federally regulated mortgages. In addition, this layer can help planners and firms avoid areas of flood risk and also avoid additional cost to carry insurance for certain planned activities. Dataset SummaryPhenomenon Mapped: Flood Hazard AreasGeographic Extent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands and American Samoa.Projection: Web Mercator Auxiliary SphereData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Northern Mariana Islands, and American Samoa)Cell Sizes: 10 meters (default), 30 meters, and 90 metersUnits: NoneSource Type: ThematicPixel Type: Unsigned integerSource: Federal Emergency Management Agency (FEMA)Update Frequency: AnnualPublication Date: May 7, 2025 This layer is derived from the May 7, 2025 version Flood Insurance Rate Map feature class S_FLD_HAZ_AR. The vector data were then flagged with an index of 94 classes, representing a unique combination of values displayed by three renderers. (In three resolutions the three renderers make nine processing templates.) Repair Geometry was run on the set of features, then the features were rasterized using the 94 class index at a resolutions of 10, 30, and 90 meters, using the Polygon to Raster tool and the "MAXIMUM_COMBINED_AREA" option. Not every part of the United States is covered by flood rate maps. This layer compiles all the flood insurance maps available at the time of publication. To make analysis easier, areas that were NOT mapped by FEMA for flood insurance rates no longer are served as NODATA but are filled in with a value of 250, representing any unmapped areas which appear in the US Census boundary of the USA states and territories. The attribute table corresponding to value 250 will indicate that the area was not mapped.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application. Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "flood hazard areas" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "flood hazard areas" in the search box, browse to the layer then click OK. In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro. The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one. Processing TemplatesCartographic Renderer - The default. These are meaningful classes grouped by FEMA which group its own Flood Zone Type and Subtype fields. This renderer uses FEMA's own cartographic interpretations of its flood zone and zone subtype fields to help you identify and assess risk. Flood Zone Type Renderer - Specifically renders FEMA FLD_ZONE (flood zone) attribute, which distinguishes the original, broadest categories of flood zones. This renderer displays high level categories of flood zones, and is less nuanced than the Cartographic Renderer. For example, a fld_zone value of X can either have moderate or low risk depending on location. This renderer will simply render fld_zone X as its own color without identifying "500 year" flood zones within that category.Flood Insurance Requirement Renderer - Shows Special Flood Hazard Area (SFHA) true-false status. This may be helpful if you want to show just the places where flood insurance is required. A value of True means flood insurance is mandatory in a majority of the area covered by each 10m pixel. Each of these three renderers have templates at three different raster resolutions depending on your analysis needs. To include the layer in web maps to serve maps and queries, the 10 meter renderers are the preferred option. These are served with overviews and render at all resolutions. However, when doing analysis of larger areas, we now offer two coarser resolutions of 30 and 90 meters in processing templates for added convenience and time savings.Data DictionaryMaking a copy of your area of interest using copyraster in arcgis pro will copy the layer's attribute table to your network alongside the local output raster. The raster attribute table in the copied raster will contain the flood zone, zone subtype, and special flood hazard area true/false flag which corresponds to each value in the layer for your area of interest. For your convienence, we also included a table in CSV format in the box below as a data dictionary you can use as an index to every value in the layer. Value,FLD_ZONE,ZONE_SUBTY,SFHA_TF 2,A,, 3,A,,F 4,A,,T 5,A,,T 6,A,,T 7,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 8,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 9,A,ADMINISTRATIVE FLOODWAY,T 10,A,COASTAL FLOODPLAIN,T 11,A,FLOWAGE EASEMENT AREA,T 12,A99,,T 13,A99,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 14,AE,,F 15,AE,,T 16,AE,,T 17,AE,,T 18,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 19,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 20,AE,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",T 21,AE,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",T 22,AE,ADMINISTRATIVE FLOODWAY,T 23,AE,AREA OF SPECIAL CONSIDERATION,T 24,AE,COASTAL FLOODPLAIN,T 25,AE,COLORADO RIVER FLOODWAY,T 26,AE,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 27,AE,COMMUNITY ENCROACHMENT,T 28,AE,COMMUNITY ENCROACHMENT AREA,T 29,AE,DENSITY FRINGE AREA,T 30,AE,FLOODWAY,T 31,AE,FLOODWAY CONTAINED IN CHANNEL,T 32,AE,FLOODWAY CONTAINED IN STRUCTURE,T 33,AE,FLOWAGE EASEMENT AREA,T 34,AE,RIVERINE FLOODWAY IN COMBINED RIVERINE AND COASTAL ZONE,T 35,AE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 36,AE,STATE ENCROACHMENT AREA,T 37,AH,,T 38,AH,,T 39,AH,FLOODWAY,T 40,AO,,T 41,AO,COASTAL FLOODPLAIN,T 42,AO,FLOODWAY,T 43,AREA NOT INCLUDED,,F 44,AREA NOT INCLUDED,,T 45,AREA NOT INCLUDED,,U 46,D,,F 47,D,,T 48,D,AREA WITH FLOOD RISK DUE TO LEVEE,F 49,OPEN WATER,,F 50,OPEN WATER,,T 51,OPEN WATER,,U 52,V,,T 53,V,COASTAL FLOODPLAIN,T 54,VE,,T 55,VE,,T 56,VE,COASTAL FLOODPLAIN,T 57,VE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 58,X,,F 59,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,F 60,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,T 61,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,U 62,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,F 63,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,F 64,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COASTAL ZONE,F 65,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COMBINED RIVERINE AND COASTAL ZONE,F 66,X,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",F 67,X,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",F 68,X,1 PCT DEPTH LESS THAN 1 FOOT,F 69,X,1 PCT DRAINAGE AREA LESS THAN 1 SQUARE MILE,F 70,X,1 PCT FUTURE CONDITIONS,F 71,X,1 PCT FUTURE CONDITIONS CONTAINED IN STRUCTURE,F 72,X,"1 PCT FUTURE CONDITIONS, COMMUNITY ENCROACHMENT",F 73,X,"1 PCT FUTURE CONDITIONS, FLOODWAY",F 74,X,"1 PCT FUTURE IN STRUCTURE, COMMUNITY ENCROACHMENT",F 75,X,"1 PCT FUTURE IN STRUCTURE, FLOODWAY",F 76,X,AREA OF MINIMAL FLOOD HAZARD, 77,X,AREA OF MINIMAL FLOOD HAZARD,F 78,X,AREA OF MINIMAL FLOOD HAZARD,T 79,X,AREA OF MINIMAL FLOOD HAZARD,U 80,X,AREA OF SPECIAL CONSIDERATION,F 81,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,F 82,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 83,X,FLOWAGE EASEMENT AREA,F 84,X,1 PCT FUTURE CONDITIONS,T 85,AH,COASTAL FLOODPLAIN,T 86,AE,,U 87,AE,FLOODWAY,F 88,X,AREA WITH REDUCED FLOOD HAZARD DUE TO ACCREDITED LEVEE SYSTEM,F 89,X,530,F 90,VE,100,T 91,AE,100,T 92,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO LEVEE SYSTEM,T 93,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO NON-ACCREDITED LEVEE SYSTEM,T 94,A,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 250,AREA NOT INCLUDED,Not Mapped by FEMA, Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Laatste update: 07 december 2023In ArcGIS Desktop en ArcGIS Pro is het mogelijk om bestaande database views direct toe te voegen aan een kaart. De database view wordt toegevoegd als een ‘query layer’. Een ‘query layer’ is read-only en kan dus wel worden bekeken en als input dienen voor geoprocessing tools, maar er kunnen geen edits op worden uitgevoerd.Een view toevoegen aan de kaart kan op 3 manieren.