WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers (this dataset)
   • Without Coastal Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

This style comprises 20 distinct hues, plus a white version, of the firefly symbol family for points, lines, and polygons.Points have two flavors of symbols. One is a standard radial opacity decay with a molten white core. The other is a variant with a shimmer effect, if that's what you need.Line symbols are available in solid or dashed. Lines are a stack of colorized semitransparent strokes beneath a white stroke, to create a glow effect.Polygons are also available in two versions. One version applies the glow to the perimeter of the polygon in both inner and outer directions, with a semi-transparent fill. This is effective for non-adjacent polygons. The alternate version only applies an inner glow, to prevent blending and overlapping of adjacent polygons.This is an early version of these symbols and only the points respond to color selection.Learn how to install this style by visiting this salacious blog post.Learn more about Firefly Cartography here.Happy Firefly Mapping! John

Calculates the number and area of patches and gaps within quadrat polygons. Quadrats can be regular, irregular, or overlapping. Gaps can be limited to certain sizes.

Road edges are defined as the edge of the improved surface including the improved shoulder but do not include the unimproved shoulder, only the travel part of the road. The road network is compiled to include all open intersections. Features do not overlap sidewalks, but have the sidewalk area cut out of the road polygons. Overlapping features are acceptable if one of the features is hidden. Road: A generally named thoroughfare, that is usually paved and can be public or private. Unimproved thoroughfares are excluded. Road polygons are formed by a combination of road edge, curb, sidewalk, street intersection closure line, and map sheet edge. Paved Median Island: Perimeter of non-traffic paved areas that separate traffic lanes in opposing directions. Unpaved Median Island: Perimeter of non-traffic grassy, unpaved areas that separate traffic lanes in opposing directions. Paved Traffic Island: Perimeter of non-traffic concrete areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Unpaved Traffic Island: Perimeter of non-traffic unpaved, grassy areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Alley: Perimeter of alleys first plotted photogrammetrically from other indicators such as building footprints, fence lines, curb lines, walls, paved or unpaved drives, and map sheet edge. Alley polygons are closed along the lines where they intersect with road polygons. Paved Drive: A paved driveway for a building or entranceway for a parking lot. Driveways are neither streets nor alleys, but provide access to public facilities, such as a drive to a monument, museum, hotel, large estate, sports field or golf course, grounds of the U.S. Capitol, etc. If a driveway is less than 200 feet and leads to a parking lot, the entire paved area is captured as Parking Lot. Driveways are photogrammetrically compiled as polygons and not compiled from individual vectors on different levels. Parking Lot: Generally paved surfaces used for cars to park on. Paved drives usually form entrances to these features, if the drive is more than 200 feet. If the driveway is less than 200 feet leading into the parking lot, the entire paved area is captured as Parking Lot. Parking lots sharing a common boundary with linear features must have the common segment captured once, but coded as both polygon and line. Small parking areas, where individuals park their cars in the middle of a block off a public alley, are not captured as parking lots. These are either public space (e.g., alleys) or private space where owners permit parking to occur. Intersection: A location where more than one road comes together. For standard cross streets, intersection polygons are bounded by curbs and four closure lines at street intersection crosswalks (outer line) or placed arbitrarily where crosswalks could logically be placed. For "T" intersections, the polygons are bounded by curbs and three such closure lines. Complex intersections can have more closure lines. Entire traffic circles are coded as intersections. Hidden Road: A section of a road that passes underneath a bridge or overpass and is not visible in an aerial photograph, but the location can be interpreted based on the road on either side of the bridge. Hidden Median: A road median that exists underneath a bridge or overpass and is not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

As the parent to WTRBDY_AREA, WTRBDY_DET contains more detail (i.e., _DET) than its child product, WTRBDY_AREA. The layer contains the same information as WTRBDY_AREA such as areal waterbodies and double-banked streams and rivers, plus additional detail. This detail includes additional attributes, storage of tidal range information, and coding and overlapping geometry to store over-water manmade features as well as historic change. This change information includes loss of, or significant change in extent for lakes and ponds, as well as significant changes in waterfront geometry or change in major river channels. In addition, Lake Washington, Lake Sammamish, Puget Sound are stored as simple polygons but also as overlapping polygons showing jurisdictional proximity assignments. Over-water features, such as waterfront docks, marinas and industrial areas, are stored as overlapping polygons. These feature types can be unselected to show a more natural shoreline.

This data began as geographical range data from the IUCN Red List for different mammal orders according to mammalian ranges in 2009. Using the "overlapping polygons" function in ArcGis 9.3, I converted the polygon shape files into numbers representing each species. Then calculated which species overlapped with one another. The resulting file has the species names, their corresponding polygon number, and then the polygon numbers, representing the other species, that overlap with the species of interest. Data is available for six orders of mammals. The IUCN Red List should be cited as the origin of this data:IUCN 2009. IUCN Red List of Threatened Species. www.iucnredlist.org. Downloaded on 07 September 2009.Converted by: Monroe MJ (2012) Does competition drive character differences between species on a macroevolutionary scale? Journal of Evolutionary Biology 25: 2341-2347

Unincorporated Urban Growth Areas (UGA) as defined by the Growth Management Act (GMA). The annual update is conducted by collecting UGA polygons directly from each of Washington's 39 counties. As of 2025, there are 27 counties with UGAs.All UGA polygons are normalized against the Department of Revenue's (DOR) "City Boundaries" layer (shared to the Washington Geoportal a.k.a. the GIS Open Data site: geo.wa.gov). The City Boundaries layer was processed into this UGA layer such that any overlapping area of UGA polygons (from authoritative individual counties) was erased. Since DOR polygons and county-sourced UGA polygons do not have perfect topology, many slivers resulted after the erase operation. These are attempted to be irradicated by these processing steps. "Multipart To Singlepart" Esri tool; exploded all polygons to be individualSlivers were mathematically identified using a 4 acre area threshold and a 0.3 "thinness ratio" threshold as described by Esri's "Polygon Sliver" tool. These slivers are merged into the neighboring features using Esri's "Eliminate" tool.Polygons that are less than 5,000 sq. ft. and not part of a DOR city (CITY_NM = Null) were also merged via the "Eliminate" tool. (many very small slivers were manually found yet mathematically did not meet the thinness ratio threshold)The final 8 polygons less than 25 sq. ft. were manually deleted (also slivers but were not lined up against another feature and missed by the "Eliminate" tool runs)Dissolved all features back to multipart using all fieldsAll UGAs polygons remaining are unincorporated areas beyond the city limits. Any polygon with CITY_NM populated originated from the DOR "City Boundaries" layer. The DOR's City Boundaries are updated quarterly by DOR. For the purposes of this UGA layer, the city boundaries was downloaded one time (4/24/2025) and will not be updated quarterly. Therefore, if precise city limits are required by any user of UGA boundaries, please refer to the city boundaries layer and conduct any geoprocessing needed. The DOR's "City Boundaries" layer is available here:https://www.arcgis.com/home/item.html?id=69fcb668dc8d49ea8010b6e33e42a13aData is updated in conjunction with the annual statewide parcel layer update. Latest update completed April 2025.

Source Water Assessment and Protection Program (SWAPP) is designed to provide for a proactive planning and protection for public drinking water supplies. The SWAPP data set provide a three-tiered polygon delineation of the protection areas for the purposes of inventorying potential contaminant sources in each of Zones I, II, and III. This data set is pubished as one merged statewide data set, to show spatial extent of coverage (i.e. where protection areas overlap, the individual polygons are merged). This data set covers surface water protection areas; wellhead protection areas (WHPA) are a separate data set.

This parcel layer contains the parcel's situs (physical) address maintained by the Planning Department.The parcel geometry provides a rough representation of tax parcels in relation to one another and to district boundaries. Parcels with multiple site addresses are represented by overlapping polygons.Contact Nevada County GIS for assistance.

This dataset provides a non-overlapping polygon layer containing a single dominant habitat code. This is derived from the NVC conversion data currently in the Habitat map of Scotland as of October 2023.

The summaries are derived from the Ecopia vector land cover dataset (a non-public resource) and not from the Ecopia raster land cover dataset available on this open data site.Percentages for each land cover type were calculated as compared to Ecopia’s total delineated area per summary polygon:sum_area_land_cover_type / sum_area_all_Ecopia_delineated_polygons_

Boundaries for Ordinances since 2008 that changed Tacoma Zoning. See historic paper maps for rezones prior to 2008. Errors in historic paper map have been noted in this dataset. If an area has been rezoned multiple times with different boundaries since 2008, the resulting polygon is represented as a region (overlapping polygon).Boundaries are symbolized as area-wide and site-specific. Contact: City of Tacoma Planning & Development Services

A parcel-based land use summary of the Denver region All files are uploaded in a zip archive file format- they will need to be extracted before opening in ArcGIS, QGIS, or similar programs. In general we recommend using the gdb source rather than shp sources for data due to some data loss and field truncation in the shape file archives. Projected Coordinate System NAD 1983 HARN StatePlane Colorado Central FIPS 0502 (US Feet) WKID: 2877 Sources Colorado Public Parcels – link Aggregated by the Governor's Office of Information Technology Geospatial Information Systems; contains all public parcels in the state, including land use codes supplied by counties and other jurisdictions. Sourced on 7/9/2025. Zoning 2023 – link Zoning shapefile sourced from DRCOG, used to supply possible ‘land use’ where land use codes were not provided in the Colorado Public Parcels file. Land Use Categorizations Below are the land use codes I categorized parcels by Residential: Any residence land use (single family, multi-unit, senior) Zoning Follow Up: Should not be in the final dataset – used to indicate there's no land use data and needs to be backfilled with zoning classifications Vacant: Parcel indicated as vacant Commercial: Any commercial use, including office, retail Exempt/Government: Exempt land use or government land use (eg: city hall, fire station) Agricultural: Agricultural, or ranch use Other/Unknown: Some other use / cannot be determined Industrial: Industrial, including meat packing School: Schools (K‑12, college, public and private) Mixed Use: A parcel specifically marked as mixed use Open Space/Parks/Recreation: Open space, park, outdoor recreation (eg: cabins, camping, etc) Medical: Hospitals, medical offices, etc Caveats Many parcels did not contain land use codes or contained land use codes that could not be discerned. In that case, zoning designations were appended to estimate the land use. Even with the above process, many parcels were missing a land use classification. Files & Feature Layers Land Use Parcel Standardization.xlsx: A spreadsheet where I standardized land use codes into the categories above. The tab Land Use Codes is where categorizations were based on the parcels’ land use codes and descriptions, while Zoning Code Follow Up used the zoning classification that had greatest geographic overlap with the parcel. public_parcel_drcog.shp: The original Colorado Public Parcels file, with the majority‑overlapping zoning code from Zoning 2023 added, and the land use categorizations from Land Use Parcel Standardization appended. parcel_land_use.shp: A final feature class, derived from public_parcel_drcog and dissolved by the zoning categorization appended from Land Use Parcel Standardization. Land Use Data.gdb: Contains all the above feature classes.

Abstract

The dataset was derived by the Bioregional Assessment Programme from multiple the Queensland geology and structural framework dataset. The source dataset is identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

This dataset contains a polygon shapefile of the Belyando Basin province boundary. The Belyando Basin underlies the eastern margin of the Galilee subregion. Extracted from the QLD Geology and Structural Framework of 2012 - the abstract of which is below.

The data on this DVD contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application.

The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale.

The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics).

For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info.

Purpose

This dataset provides a single, merged representation of the Belyando Basin as interpreted by the QLD Geology and Structural Framework of 2012

Dataset History

This dataset has been extracted directly from the QLD Geology and Structural Framework: QLD_STRUCTURAL_FRAMEWORK.shp.

1. Features with the following 'Heirarchy' attributes were selected and extracted:

a) Galilee Basin>Drummond Basin>Belyando Basin>Thomson Orogen

b) Eromanga Basin>Galilee Basin>Drummond Basin>Belyando Basin>Thomson Orogen

c) Drummond Basin>Belyando Basin>Thomson Orogen

d) Galilee Basin>Drummond Basin>Belyando Basin>Thomson Orogen

1. Features were merged together to produce the Belyando Basin province.

The lineage of the QLD Geology and Structural Framework is below:

Data in this release

*ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology

*ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework

*ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology

*Georeferenced Queensland geology map, gravity and magnetic images

*Queensland geology map, structural framework and schematic diagram PDF files

*Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94

Accessing the data

Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites").

Metadata

Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders.

Disclaimer

The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites.

Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination.

The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason.

The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way.

WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties.

Dataset Citation

Bioregional Assessment Programme (XXXX) Belyando Basin Boundary - QLD Structural Framework. Bioregional Assessment Derived Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/4add856a-eb40-4bb2-bd41-f89788884782.

Dataset Ancestors

• Derived From Queensland geology and structural framework - GIS data July 2012

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

This dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows:

This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application.

The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale.

In the ESRI version, a layer file is provided which presents the units in the colours and patterns used on the printed hard copy map. For Map Info users, a simplified colour palette is provided without patterns. However a georeferenced image of the hard copy map is included and can be displayed as a background in both Arc Map and Map Info.

The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics).

For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info.

Dataset History

Details on the source data can be found in the xml file associated with data layer.

Data in this release

\*ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology

\*ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework

\*ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology

\*Georeferenced Queensland geology map, gravity and magnetic images

\*Queensland geology map, structural framework and schematic diagram PDF files

\*Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94

Accessing the data

Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites").

Metadata

Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders.

Disclaimer

The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites.

Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination.

The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason.

The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way.

WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties.

Please view the 'readme.html' and 'licence.html' file for further, more complete information

Dataset Citation

Geological Survey of Queensland (2012) Queensland geology and structural framework - GIS data July 2012. Bioregional Assessment Source Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/69da6301-04c1-4993-93c1-4673f3e22762.

First, we would like to thank the wildland fire advisory group. Their wisdom and guidance helped us build the dataset as it currently exists. Currently, there are multiple, freely available wildland fire datasets that identify wildfire and prescribed fire areas across the United States. However, these datasets are all limited in some way. Time periods, spatial extents, attributes, and maintenance for these datasets are highly variable, and none of the existing datasets provide a comprehensive picture of wildfires that have burned since the 1800s. Utilizing a series of both manual processes and ArcGIS Python (arcpy) scripts, we merged 40 of these disparate datasets into a single dataset that encompasses the known wildfires within the United States from the 1800s to the present. These datasets were ranked by order of observed quality, and overlapping polygons in the same year were used individually or dissolved together with other polygons based on ranked quality (see individual ste ...

PLEASE NOTE: the verified list is not a list of all waters that do not meet water quality standards - it only contains waters that are awaiting a TMDL. Please see the Waters Not Attaining Standards (WNAS) layer to see all waters that do not meet water quality standards. As part of DEP’s watershed management approach, all of the basins in Florida are assessed every two years. The "verified list" is the list of Florida's impaired waterbodies in need of a total maximum daily load (TMDL) and that fail to attain designated uses and/or meet the minimum criteria for surface waters established in the Surface Water Quality Standards (62-302, F.A.C.) and the Impaired Waters Rule (IWR, 62-303, F.A.C.). If a waterbody is assessed as impaired, a TMDL must be developed to determine the maximum amount of a pollutant that a waterbody can receive and remain healthy. Once a TMDL has been completed, the waterbody is removed from the verified list regardless of whether or not the waterbody meets standards. For more information or questions regarding the verified list and assessments, please contact Jessica Mostyn (Jessica.Mostyn@FloridaDEP.gov). For more information or questions regarding TMDLs please contact Kevin O'Donnell (Kevin.ODonnell@FloridaDEP.gov). Purpose: Coverage includes all the WBIDs (Waterbody IDs - RUN 64) that are currently included on the verified list for any parameter from Group 1, Cycle 1 through the 2022-24 Biennial Assessment (referenced as Cycle 6), excluding WBID/parameter combinations that have subsequently been delisted in a later cycle. If a WBID is listed for multiple parameters the coverage contains overlapping polygons for each parameter.

The fully intersected data is the atomic level of the PLSS that is similar to the coverage or the smallest pieces used to build the PLSS. Polygons may overlap in this feature class. This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication.

RPA Boundaries with overlap (that do not edge-match) with MAPC region. Where some constituent municipalities are considered to be part of both MAPC and also part of the RPA (OCPC), they are enclosed by overlapping polygons for both of those regions. Original title of this layer: RPAs with overlap. See also the layer in which the boundary lines do not overlap: RPA Boundaries (With Shared Munis Separated). [MAPC metadata. UNLINKED. Source: MassGIS. Publisher: MAPC. Scale Limits: none.]