This vector tile layer provides a detailed basemap for the region symbolized with a classic Esri topographic map style. This vector tile layer is similar in content and style to the COT Topographic Base Map, which is delivered as raster fused map cache tile layer. This vector tile layer provides unique capabilities for customization and high-resolution display.This layer includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries, designed for use with shaded relief for added context. The map is built using the same data sources used for the COT Topographic Base Map raster basemap and other City and Esri basemaps. Use this MapThis map is designed to be used as a basemap layer or reference layer in a web map. You can add this layer to a web map and save as your own map. If you would like to use this map as a basemap layer in a web map, you may use the vector basemap Topographic web map.Customize this MapBecause this map is delivered as a vector tile layer, users can customize the map to change its content and symbology, including fonts. Users are able to turn on and off layers, change symbols for layers, switch to alternate local language (in some areas), and refine the treatment of disputed boundaries. See the Vector Basemap group for other vector tile layers. For details on how to customize this map, please refer to these articles on the ArcGIS Online Blog and view the Esri Vector Basemaps Reference Document.
This data contains City of Tucson mapped flood hazard areas. Circa 2007 - Shapefile created by consultant JE Fuller who was hired by the City to map non-FEMA flood hazards. It is a composite of the city's old Flood Hazard Zones and the new Flood Hazard Zones. Began by TDOT in the 70's and 80's, added to by Frank (some from JE Fuller study) to display areas that could flood but are too small to be looked at by FEMA.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the City of Tucson's Open Data portal and not for regular use in ArcGIS Online, ArcGIS Enterprise or other web applications.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
This project integrated all the available source bathymetry data currently used within the latest gbr100 grid and generated a much higher-resolution gbr30 bathymetry grid (~30 m pixel spacing) over the GBR shelf area. The gbr30 grid is recommended for use as a spatial dataset to feed into the Local and Regional Decision Support Tool (DST) being developed by CSIRO for Integrated Pest Management. Other uses of the grid may extend beyond COTS control efforts to include hydrodynamic modelling, natural hazard assessment, to plan and build offshore infrastructure, and to benefit tourism and fishing.
The gbr30 grid was then used to generate spatial datasets and descriptive statistics of 22 selected 'super spreader' and tourism reefs, to better understand the extent of deep-water habitat at these sites. An assessment was conducted on whether submerged banks or deeper reefs may provide deep-water coral habitat for COTS, and the implications for the design of the control program.
Methods:
The project used the following bathymetry datasets to develop the gbr30 grid:
MBES source data The Australian Hydrographic Office (AHO)-supplied the majority of multibeam echo sounder (MBES) data on the GBR shelf. Geoscience Australia (GA) provided other MBES data, acquired mostly offshore by Australia’s Marine National Facility vessels and also foreign research vessels transiting through the area. Extensive editing on the source data were conducted using QPS Fledermaus and Caris HIPS&SIPS software, and by applying sound velocity and mean sea level (MSL) tide corrections where necessary.
SBES source data The AHO have conducted extensive singlebeam echo sounder (SBES) surveys across the GBR shelf for safety of navigation purposes. Other SBES data were from Maritime Safety Queensland (MSQ), various Queensland Port Authorities and from older National Mapping Division surveys. Data editing were conducted on 3D point clouds generated with Fledermaus software, and lowest astronomical tide (LAT) to MSL tide corrections applied using the Australian Vertical Datum Transformation Tool (AusCoastVDT).
ENC source data Electronic Navigational Chart (ENC) spot depths were generated from S-57 files provided by the AHO and broadly cover the entire GBR shelf and the upper slope. These spot depths were extracted from S-57 files using an ESRI file geodatabase and the xyz data imported to Fledermaus software for examining as 3D point clouds. The accepted bathymetry data were then exported from Fledermaus and LAT-MSL adjustment conducted with AusCoastVDT prior to interpolation of the depth model.
ALB source data Airborne lidar bathymetry (ALB) data were from extensive, AHO-supplied Laser Airborne Depth Sounder (LADS) surveys conducted over the GBR since 1993. Other ALB data were from the Sunshine Coast for the CRC for Spatial Information, and from the Torres Strait using the Fugro SHOALS-1000T system. ALB depths are typically limited to ~40 m. Bathymetry data were imported to Fledermaus software for editing and then LAT-MSL adjustment conducted with AusCoastVDT.
ITEM source data The ITEM DEM data were derived from the Intertidal Extents Model (ITEM v1.0), a nationalscale gridded dataset characterising the spatial extents of the exposed intertidal zone, based upon a full 28 year time series of Landsat observations. ITEM DEM data have 25 m point spacing and have a MSL vertical datum. This version of the gbr30 grid only has ITEM DEM data southwards from latitude 23° South. Future versions of the grid will include ITEM DEM along the remaining intertidal zone.
SDB source data Satellite derived bathymetry (SDB) data utilise optical imagery and rely on physics- or empirical-based techniques to extract depth data. The Queensland Government-supplied SDB data were created by Earth Observation and Environmental Services (EOMAP) using physicsbased Landsat8 for the Gladstone area. EOMAP supplied SDB data using physics-based Landsat8 for offshore Coral Sea reefs. Other SDB data used empirical-based Landsat7/8 data to supplement those reefs on the GBR lacking ALB data. SDB data are limited to ~20 m depth.
Coastline source data Coastline source data are used to ‘pin’ the bathymetry grid at the coast in order to prevent ‘bleeding’ of land into the water during the grid development phase. Coastline data were only used where the higher priority ITEM DEM data were absent, e.g. the coast northwards of latitude 23° South. The Queensland Government-supplied coastline data were rasterised and converted to 25 m point spacing files, then AusCoastVDT used to apply a mean high water springs elevation value to the data.
SRTM Source data The 1 arcsec (~27 m) Shuttle Radar Topographic Mission (SRTM) digital surface model (DSM) data were used as land elevation data for the gbr30 model. The DSM data best represents the topography of the mainland and islands, but also includes vegetation features. The 27 m data were resampled to 30 m to match the interpolated bathymetry grid pixel size. During the grid development phase, the SRTM-DSM data were merged onto the interpolated bathymetry grid to complete the gbr30 grid.
Grid development
The final grid development phase was conducted using Generic Mapping Tools (GMT) software (Wessel & Smith, 1991), following the methodology used in Becker et al. (2009). The xyz source data were first decimated using GMT blockmedian into individual xyz data files representing single node points at 15 m-resolution. The decimated data files were then concatenated into one large xyz file. Next, GMT blockmedian was conducted on the single large file to decimate the combined data to 30 m-resolution in order to produce one valid depth point for each pixel location to be used in the interpolated bathymetry grid at that same 30 mresolution. The 30 m xyz data were then compared with co-located depths from an underlying base grid, in this case the 250 m-resolution AusBathyTopo grid (Whiteway, 2009). The purpose of using a base grid was to flag any new data that may be greatly in error and thus be rejected, and also to provide underlying bathymetry data for pixels that lack coverage by the new source data. The 'repair and replace' method repairs the AusBathyTopo grid, replacing pixels with newer, higher-resolution data.
A grid was made with GMT surface using the difference values between the co-located new data and the underlying base data. GMT surface was used to resample the AusBathyTopo grid to 30 m-resolution. The difference grid and the resampled base grid were then added together with GMT grdmath. This resulting netCDF file was converted into an Environmental Systems Research Institute (ESRI) grid. The SRTM-DSM data were then merged with the interpolated bathymetry grid and clipped to produce the final gbr30 bathymetry grid.
Format:
This dataset consists of spreadsheets and various geospatial files for each of the 22 'super spreader' reefs, and a shapefile identifying the reefs.
Data Location:
This dataset is filed in the eAtlas enduring data repository at: data\NESP3\AU_NESP-TWQ-3.1.1_CSIRO_COTS-control-strategies\
This is a work in progress dataset.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
District polygons for COT Field Services
The parcel layer and attributes distributed by the State COT
Acest fișier conține limitele vectoriale digitale pentru plăcile integrate de îngrijire, în Anglia, la iulie 2022.
Updated with Park Names - 2/27/2025
Acest fișier conține limitele vectoriale digitale pentru țările din Marea Britanie, la decembrie 2016. Limitele disponibile sunt:
Ultra generalizat (500 m) – tăiat la linia de coastă (semn mediu de apă înaltă).
Conține atât Ordnance Survey cât și ONS Intellectual Property Rights.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Contains polygons of homeowners associations (HOAs) within City of Tucson jurisdiction. A homeowners association in this layer is defined as a non-profit organization that enforces restrictions for a subdivision, planned community, or condominium complex. Office parks and apartment complexes were not included in the layer.The attributes are similar to subdivisions layer with a few exceptions. There are five new fields. HOA_NAME is the registered name of the association according to the Arizona Corporation Commission (ACC). HOA_STATUS indicates whether the HOA is active at the time of last update according to the ACC website. CCR_SEQ_NUM is the sequence number from the Pima County Recorder's website for the HOA bylaws. ACC_EID is the entity ID number assigned to the association by the ACC. ST_DED indicates whether the streets within the neighborhood are maintained by the HOA, County, or Public (COT).The layer was built from the Pima County layer: Street dedication by Subdivision Plat with Homeowners Association details.PurposeDisplays the Homeowners Associations within the City of Tucson. This layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Dataset ClassificationLevel 0 - OpenKnown UsesFinding a homeowner associations CCRs, boundaries, lot count, and street maintenance responsibilities.Known ErrorsDue to the nature of the data, not all HOAs were included in the layer and may be missing from the layer. Some subdivisions had evidence of an HOA and had the necessary documentation but did not have a ACC EID and therefore have null values. There are some cases where two different subdivisions have the same HOA therefore the SEQ_NUM, BOOK_PAGE, and PROJ_NUM1 may not reflect the true values of both subdivisions.Data ContactCity of Tucson Information Technology Department, GIS Services, GIS_IT@tucsonaz.govUpdate FrequencyUpdated Yearly.Last Update: 12/21/2023
Acest fișier conține limitele vectoriale digitale pentru forumurile locale de reziliență din Anglia și Țara Galilor, la 31 decembrie 2019. Limitele disponibile sunt:
Webmap for Public GIS displaying City of Tulare's Utilities - Water, Sanitary Sewer and Stormwater infrastructure.
Ravine Priority SGR PFR Capital
Not seeing a result you expected?
Learn how you can add new datasets to our index.
This vector tile layer provides a detailed basemap for the region symbolized with a classic Esri topographic map style. This vector tile layer is similar in content and style to the COT Topographic Base Map, which is delivered as raster fused map cache tile layer. This vector tile layer provides unique capabilities for customization and high-resolution display.This layer includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries, designed for use with shaded relief for added context. The map is built using the same data sources used for the COT Topographic Base Map raster basemap and other City and Esri basemaps. Use this MapThis map is designed to be used as a basemap layer or reference layer in a web map. You can add this layer to a web map and save as your own map. If you would like to use this map as a basemap layer in a web map, you may use the vector basemap Topographic web map.Customize this MapBecause this map is delivered as a vector tile layer, users can customize the map to change its content and symbology, including fonts. Users are able to turn on and off layers, change symbols for layers, switch to alternate local language (in some areas), and refine the treatment of disputed boundaries. See the Vector Basemap group for other vector tile layers. For details on how to customize this map, please refer to these articles on the ArcGIS Online Blog and view the Esri Vector Basemaps Reference Document.