This data aligns with WWC Certification requirements, and serves as the basis for our data warehouse and open data roadmap. It's a continual work in progress across all departments.Louisville Metro Technology Services builds data and technology platforms to ready our government for our community’s digital future.Data Dictionary: Field Name Description Dataset Name The official title of the dataset as listed in the inventory. Brief Description of Data A short summary explaining the contents and purpose of the dataset. Data Source The origin or system from which the data is collected or generated. Home Department The primary department responsible for the dataset. Home Department Division The specific division within the department that manages the dataset. Data Steward (Business) Name The name of person responsible for the dataset’s accuracy and relevance. Data Custodian (Technical) Name) The technical contact responsible for maintaining and managing the dataset infrastructure. Data Classification The sensitivity level of the data (e.g., Public, Internal, Confidential) Data Format The file format(s) in which the dataset is available (e.g., CSV, JSON, Shapefile). Frequency of Data Change How often the dataset is updated (e.g., Daily, Weekly, Monthly, Annually). Time Spam The overall time period the dataset covers. Start Date The beginning date of the data collection period. End Date The end date of the data collection period Geographic Coverage The geographic area that the dataset pertains to (e.g., Louisville Metro). Geographic Granularity The level of geographic detail (e.g., parcel, neighborhood, ZIP code). Link to Existing Publication A URL linking to the dataset’s public-facing page or open data portal entry.

This DPA layer delineates the dividing lines between land that will be provided wildland fire protection by the State, Federal, and Local agencies. The Cooperative Fire Management Agreement (CFMA) between the federal agencies and the California Department of Forestry and Fire Protection (CAL FIRE) is the primary mechanism that provides the framework for wildland fire protection responsibilities statewide. Through this mechanism the state has been divided into practical Direct Protection Areas (DPAs) corresponding with each agency's responsibility. The participating agencies submit proposal for changes to their DPA where necessary. If changes are agreed upon by all parties involved, then the change is approved and the layer is updated.

The National Pollutant Release Inventory (NPRI) is Canada's public inventory of pollutant releases (to air, water and land), disposals and transfers for recycling. The files below contain a map of Canada showing the locations of all facilities that reported releases to air (other than Criteria Air Contaminants (CAC)) to the NPRI. The data are for the most recent reporting year, by reported total quantities of these releases. The map is available in both ESRI REST (to use with ARC GIS) and WMS (open source) formats. For more information about the individual reporting facilities, a dataset is available in a CSV format. Please consult the following resources to enhance your analysis: - Guide on using and Interpreting NPRI Data: https://www.canada.ca/en/environment-climate-change/services/national-pollutant-release-inventory/using-interpreting-data.html - Access additional data from the NPRI, including datasets and mapping products: https://www.canada.ca/en/environment-climate-change/services/national-pollutant-release-inventory/tools-resources-data/exploredata.html

To create this app:

National Monuments Service - Archaeological Survey of Ireland. Published by Department of Housing, Local Government and Heritage. Available under the license Creative Commons Attribution 4.0 (CC-BY-4.0).This Archaeological Survey of Ireland dataset is published from the database of the National Monuments Service Sites and Monuments Record (SMR). This dataset also can be viewed and interrogated through the online Historic Environment Viewer: https://heritagedata.maps.arcgis.com/apps/webappviewer/index.html?id=0c9eb9575b544081b0d296436d8f60f8

A Sites and Monuments Record (SMR) was issued for all counties in the State between 1984 and 1992. The SMR is a manual containing a numbered list of certain and possible monuments accompanied by 6-inch Ordnance Survey maps (at a reduced scale). The SMR formed the basis for issuing the Record of Monuments and Places (RMP) - the statutory list of recorded monuments established under Section 12 of the National Monuments (Amendment) Act 1994. The RMP was issued for each county between 1995 and 1998 in a similar format to the existing SMR. The RMP differs from the earlier lists in that, as defined in the Act, only monuments with known locations or places where there are believed to be monuments are included.

The large Archaeological Survey of Ireland archive and supporting database are managed by the National Monuments Service and the records are continually updated and supplemented as additional monuments are discovered. On the Historic Environment viewer an area around each monument has been shaded, the scale of which varies with the class of monument. This area does not define the extent of the monument, nor does it define a buffer area beyond which ground disturbance should not take place – it merely identifies an area of land within which it is expected that the monument will be located. It is not a constraint area for screening – such must be set by the relevant authority who requires screening for their own purposes. This data has been released for download as Open Data under the DPER Open Data Strategy and is licensed for re-use under the Creative Commons Attribution 4.0 International licence. http://creativecommons.org/licenses/by/4.0

Please note that the centre point of each record is not indicative of the geographic extent of the monument. The existing point centroids were digitised relative to the OSI 6-inch mapping and the move from this older IG-referenced series to the larger-scale ITM mapping will necessitate revisions. The accuracy of the derived ITM co-ordinates is limited to the OS 6-inch scale and errors may ensue should the user apply the co-ordinates to larger scale maps. Records that do not refer to 'monuments' are designated 'Redundant record' and are retained in the archive as they may relate to features that were once considered to be monuments but which on investigation proved otherwise. Redundant records may also refer to duplicate records or errors in the data structure of the Archaeological Survey of Ireland.

This dataset is provided for re-use in a number of ways and the technical options are outlined below. For a live and current view of the data, please use the web services or the data extract tool in the Historic Environment Viewer. The National Monuments Service also provide an Open Data snapshot of its national dataset in CSV as a bulk data download. Users should consult the National Monument Service website https://www.archaeology.ie/ for further information and guidance on the National Monument Act(s) and the legal significance of this dataset.

Open Data Bulk Data Downloads (version date: 23/08/2023)

The Sites and Monuments Record (SMR) is provided as a national download in Comma Separated Value (CSV) format. This format can be easily integrated into a number of software clients for re-use and analysis. The Longitude and Latitude coordinates are also provided to aid its re-use in web mapping systems, however, the ITM easting/northings coordinates should be quoted for official purposes. ERSI Shapefiles of the SMR points and SMRZone polygons are also available The SMRZones represent an area around each monument, the scale of which varies with the class of monument. This area does not define the extent of the monument, nor does it define a buffer area beyond which ground disturbance should not take place – it merely identifies an area of land within which it is expected that the monument will be located. It is not a constraint area for screening – such must be set by the relevant authority who requires screening for their own purposes.

GIS Web Service APIs (live views):

For users with access to GIS software please note that the Archaeological Survey of Ireland data is also available spatial data web services. By accessing and consuming the web service users are deemed to have accepted the Terms and Conditions. The web services are available at the URL endpoints advertised below:

SMR; https://services-eu1.arcgis.com/HyjXgkV6KGMSF3jt/arcgis/rest/services/SMROpenData/FeatureServer

SMRZone; https://services-eu1.arcgis.com/HyjXgkV6KGMSF3jt/arcgis/rest/services/SMRZoneOpenData/FeatureServer

Historic Environment Viewer - Query Tool

The "Query" tool can alternatively be used to selectively filter and download the data represented in the Historic Environment Viewer. The instructions for using this tool in the Historic Environment Viewer are detailed in the associated Help file: https://www.archaeology.ie/sites/default/files/media/pdf/HEV_UserGuide_v01.pdf...

Original and derived data products referenced in the original manuscript are provided in the data package.

Description of the data and file structure

Original data:

Table_1_source_papers.csv: Papers that met review criteria and which are summarized in Table 1 of the manuscript.

1. ID: The paper identification number
2. Topic: The broad topic (i.e., each row of Table 1)
3. Authors: The names of the authors of the paper
4. Article Title: The title of the paper
5. Source Title: The name of the journal in which the paper was published
6. Abstract: The paper's abstract, retrieved from the Web of Science search
7. study_type: Classification of the study methodology/approach. "A" = a designed study that shows effect ,"B" = a pre/post study, "C" = a comparison of health outcomes or pathogen risk relative to a 'control/comparison' area, "D" = some quantitative effect but no control, "E" = qualitative comments but little supporting evidence, and/or a qualitative review.
8. pathogen_broad: Broad classification of the type of pathogen discussed in the paper.
9. transmission_type: Categorization of indirect, direct, sexual, vector, or other transmission modes.
10. pathogen_type: Categorization of bacteria, helminth, virus, protozoa, fungi, or other pathogen types.
11. country: Country in which the study was performed or results discussed. When countries were not available, regions were used. NA values indicate papers in which a geographic region was not relevant to the study (i.e., a methods-based study).

Derived data:

change_livestock_country.csv: A dataframe containing values used to generate Figure 4a in the manuscript.

1. County Name: The name of the county in Kenya
2. Sheep and goats 1980: The estimated number of sheep and goats in 1980
3. Sheep and goats 2016: The estimated number of sheep and goats in 2016
4. pct_change_shoat: The percent change in sheep and goat numbers from 1980 to 2016
5. Cattle 1980: The estimated number of cattle in 1980
6. Cattle 2016: The estimated number of cattle in 2016
7. pct_change_cattle: The percent change in cattle numbers from 1980 to 2016
8. Camel 1980: The estimated number of camels in 1980
9. Camel 2016: The estimated number of camels in 2016
10. pct_change_camel: The percent change in camel numbers from 1980 to 2016
11. human_pop 1980: The estimated human population in the county in 1980
12. human_pop 2016: The estimated human population in the county in 1980
13. pct_change_human: The percent change in the human population from 1980 to 2016
14. area_sq_km: The land area of the county
15. change_ind_per_sq_km_shoat: Absolute change in number of sheep and goats from 1980 to 2016
16. change_ind_per_sq_km_cattle: Absolute change in number of cattle from 1980 to 2016
17. change_ind_per_sq_km_camel: Absolute change in number of camels from 1980 to 2016

country_avg_schist_wormy_world.csv: A dataframe containing values used to generate Figure 3 in the manuscript.

• Country: The country in which the schistosome prevalence studies were performed.
• Latitude: The latitute in decimal degrees
• Longitude: The longitute in decimal degrees
• Maximum.prevalence: The mean maximum schistosomiasis prevalence of studies conducted within each country.

kenya_precip_change_1951_2020.csv: A dataframe containing values used to generate Figure 4b in the manuscript.

• Precipitation (mm): Binned annual precipitation values
• 1951-1980: The density of observations for each annual precipitation value for the 1951-1980 period
• 1971-2000: The density of observations for each annual precipitation value for the 1971-2000 period
• 1991-2020: The density of observations for each annual precipitation value for the 1991-2020 period

Sharing/Access information

Data were derived from the following sources:

• Ogutu, J. O., Piepho, H.-P., Said, M. Y., Ojwang, G. O., Njino, L. W., Kifugo, S. C., & Wargute, P. W. (2016). Extreme wildlife declines and concurrent increase in livestock numbers in Kenya: What are the causes? PloS ONE, 11(9), e0163249. https://doi.org/10.1371/journal.pone.0163249

• London Applied & Spatial Epidemiology Research Group (LASER). (2023). Global Atlas of Helminth Infections: STH and Schistosomiasis [dataset]. London School of Hygiene and Tropical Medicine. https://lshtm.maps.arcgis.com/apps/webappviewer/index.html?id=2e1bc70731114537a8504e3260b6fbc0

• World Bank Group. (2023). Climate Data & Projections—Kenya. Climate Change Knowledge Portal. https://climateknowledgeportal.worldbank.org/country/kenya/climate-data-projections

The HANZE dataset covers riverine, pluvial, coastal and compound floods that have occurred in 42 European countries between 1870 and 2020. The data was collected by extensive data-collection from more than 800 sources ranging from news reports through government databases to scientific papers. The dataset includes 2521 events characterized by at least one impact statistic: area inundated, fatalities, persons affected or economic loss. Economic losses are presented both in the original currencies and price levels as well as inflation and exchange-rate adjusted to 2020 value of the euro. The spatial footprint of affected areas is consistently recorded using more than 1400 subnational units corresponding, with minor exceptions, to the European Union’s Nomenclature of Territorial Units for Statistics (NUTS), level 3. Daily start and end dates, information on causes of the event, notes on data quality issues or associated non-flood impacts, and full bibliography of each record supplement the dataset. Apart from the possibility to download the data, the database can be viewed, filtered and visualized online: https://naturalhazards.eu. The dataset is designed to be complimentary to HANZE-Exposure, a high-resolution model of historical exposure changes (such as population and asset value), and be easily usable in statistical and spatial analyses.

The dataset contains the following files (CSV comma-delimited, UTF8, and ESRI shapefiles in zipped folders)

HANZE flood events database

HANZE_events.csv - Flood event data

HANZE_references.csv - List of all references

HANZE_events_regions_2010.zip - Flood event data as GIS file (regions v2010)

HANZE_events_regions_2021.zip - Flood event data as GIS file (regions v2021)

Supplementary data

S1_countries_codes_and_names.csv - Country codes/names

S2_regions_codes_and_names_v2010.csv - Region codes/names, v2010

S3_regions_codes_and_names_v2021.csv - Region codes/names, v2021

S4_list_of_all_currencies_by_country.csv - Data on all currencies used in the study area since 1870

S5_currency_conversion_rates.csv - Conversion rates applied to compute losses in 2020 euros

S6_GDP_deflators_by_country.csv - Gross domestic product deflator by country, 1870-2020

S7_floods_removed_from_HANZE.csv - Flood events in HANZE v1, which were excluded from v2

Regions_v2010_simplified.zip - Map of subnational regions used in the database, v2010

Regions_v2021_simplified.zip - Map of subnational regions used in the database, v2021

Note: this is a minor update of the original upload. It corrects the erroneous rendering of NUTS regions for event 2751, fixes some geometry problems with the GIS files and makes some small changes to the flood data (2 events were added and the regional codes for Kosovo in version 2021 were modified based on the upcoming NUTS 2024 classification).

This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.

Landslides are damaging and deadly, and they occur in every U.S. state. However, our current ability to understand landslide hazards at the national scale is limited, in part because spatial data on landslide occurrence across the U.S. varies greatly in quality, accessibility, and extent. Landslide inventories are typically collected and maintained by different agencies and institutions, usually within specific jurisdictional boundaries, and often with varied objectives and information attributes or even in disparate formats. The purpose of this data release is to provide an openly accessible, centralized map of existing information about landslide occurrence across the entire U.S. This data release is an update of previous versions 1 (Jones and others, 2019) and 2 (Belair and others, 2022). Changes relative to version 2 are summarized in us_ls_v3_changes.txt. It provides an integrated database of the landslides from these inventories (refer to US_Landslide_v3_gpkg) with a selection of uniform attributes, including links to the original digital inventory files (whenever available) (“Inv_URL”). The data release includes digital inventories created by both USGS and non-USGS authors. The original inventory is denoted by an abbreviation in the “Inventory” attribute. The full citation for each abbreviation can be found in us_ls_v3_references.csv. The date of the landslide event is included as a minimum and maximum (“Date_Min” and “Date_Max”) to accommodate events that happen within a range of dates. The date value is inherently difficult to interpret or discern due to the nature of landsliding, where some landslides move for long periods of time or move intermittently, and some areas can exhibit multiple landslide events. To preserve the constituent inventories as much as possible, we include all entries even if they are not considered landslides, such as “gullies” or “avalanche chutes.” We include a landslide type attribute when that information is available (“LS_Type”). The landslide classification system used in the original inventories is not always known or stated in the metadata, but many mapping entities use the schema from Cruden and Varnes (1996) or the updated schema from Hungr and others (2014). Given the wide range of landslide information sources in this data compilation, we provide an attribute to assess the relative confidence in the characterization of the location and extent of each landslide (entry) (“Confidence”). The confidence level reflects the resolution and quality of input data, as well as the method used for identification and mapping. This confidence does not reflect a formal accuracy assessment of field attributes. Relative to the previous data releases (version 1 and 2), this update (v3) includes more inventories, updated confidence rules, a new landslide type attribute, a new unique identifier (“USGS_ID”), new machine-readable date fields, and an ancillary database containing all fields from the original inventories (refer to US_Landslide_v3_ancillary). Please contact gs-haz_landslides_inventory@usgs.gov for more information on how to contribute additional inventories to this community effort. When possible, please cite the constituent inventories as well as this data release.This data release includes: (1) a landslide point file and polygon file in multiple forms (US_Landslide_v3_gpkg, US_Landslide_v3_shp, US_Landslide_v3_csv), (2) an ancillary database with original fields (US_Landslide_v3_ancillary), (3) a spreadsheet that summarizes the confidence rules, their justification, and any extra analyses (us_ls_v3_analyses.csv), (4) a summary file of the changes made between version 2 and version 3 (us_ls_v3_changes.txt), (5) a file containing the references of the constituent inventories (us_ls_v3_references.csv), (6) and a readme (README.txt).Disclaimer: Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.

The National Pollutant Release Inventory (NPRI) is Canada's public inventory of pollutant releases (to air, water and land), disposals and transfers for recycling. The files below contain a map of Canada showing the locations of all facilities that reported direct releases to land to the NPRI. The data are for the most recent reporting year, by reported total quantities of these releases. The map is available in both ESRI REST (to use with ARC GIS) and WMS (open source) formats. For more information about the individual reporting facilities, a dataset is available in a CSV format. Please consult the following resources to enhance your analysis: - Guide on using and Interpreting NPRI Data: https://www.canada.ca/en/environment-climate-change/services/national-pollutant-release-inventory/using-interpreting-data.html - Access additional data from the NPRI, including datasets and mapping products: https://www.canada.ca/en/environment-climate-change/services/national-pollutant-release-inventory/tools-resources-data/exploredata.html

Dataset contains census usually resident population counts from the 2013, 2018, and 2023 Censuses, as well as the percentage change in the population count between the 2013 and 2018 Censuses, and between the 2018 and 2023 Censuses. Data is available by statistical area 2.

Map shows the percentage change in the census usually resident population count between the 2018 and 2023 Censuses.

Download lookup file from Stats NZ ArcGIS Online or embedded attachment in Stats NZ geographic data service. Download data table (excluding the geometry column for CSV files) using the instructions in the Koordinates help guide.

​

Footnotes

Geographical boundaries

Statistical standard for geographic areas 2023 (updated December 2023) has information about geographic boundaries as of 1 January 2023. Address data from 2013 and 2018 Censuses was updated to be consistent with the 2023 areas. Due to the changes in area boundaries and coding methodologies, 2013 and 2018 counts published in 2023 may be slightly different to those published in 2013 or 2018.

​

Subnational census usually resident population

The census usually resident population count of an area (subnational count) is a count of all people who usually live in that area and were present in New Zealand on census night. It excludes visitors from overseas, visitors from elsewhere in New Zealand, and residents temporarily overseas on census night. For example, a person who usually lives in Christchurch city and is visiting Wellington city on census night will be included in the census usually resident population count of Christchurch city.

​

Caution using time series

Time series data should be interpreted with care due to changes in census methodology and differences in response rates between censuses. The 2023 and 2018 Censuses used a combined census methodology (using census responses and administrative data), while the 2013 Census used a full-field enumeration methodology (with no use of administrative data).

​

About the 2023 Census dataset

For information on the 2023 dataset see Using a combined census model for the 2023 Census. We combined data from the census forms with administrative data to create the 2023 Census dataset, which meets Stats NZ's quality criteria for population structure information. We added real data about real people to the dataset where we were confident the people who hadn’t completed a census form (which is known as admin enumeration) will be counted. We also used data from the 2018 and 2013 Censuses, administrative data sources, and statistical imputation methods to fill in some missing characteristics of people and dwellings.

​

Data quality

The quality of data in the 2023 Census is assessed using the quality rating scale and the quality assurance framework to determine whether data is fit for purpose and suitable for release. Data quality assurance in the 2023 Census has more information.

​

Quality rating of a variable

The quality rating of a variable provides an overall evaluation of data quality for that variable, usually at the highest levels of classification. The quality ratings shown are for the 2023 Census unless stated. There is variability in the quality of data at smaller geographies. Data quality may also vary between censuses, for subpopulations, or when cross tabulated with other variables or at lower levels of the classification. Data quality ratings for 2023 Census variables has more information on quality ratings by variable.

​

Census usually resident population count concept quality rating

The census usually resident population count is rated as very high quality.

Census usually resident population count – 2023 Census: Information by concept has more information, for example, definitions and data quality.

​

Using data for good

Stats NZ expects that, when working with census data, it is done so with a positive purpose, as outlined in the Māori Data Governance Model (Data Iwi Leaders Group, 2023). This model states that "data should support transformative outcomes and should uplift and strengthen our relationships with each other and with our environments. The avoidance of harm is the minimum expectation for data use. Māori data should also contribute to iwi and hapū tino rangatiratanga”.

​

Confidentiality

The 2023 Census confidentiality rules have been applied to 2013, 2018, and 2023 data. These rules protect the confidentiality of individuals, families, households, dwellings, and undertakings in 2023 Census data. Counts are calculated using fixed random rounding to base 3 (FRR3) and suppression of ‘sensitive’ counts less than six, where tables report multiple geographic variables and/or small populations. Individual figures may not always sum to stated totals. Applying confidentiality rules to 2023 Census data and summary of changes since 2018 and 2013 Censuses has more information about 2023 Census confidentiality rules.

​

Symbol

-998 Not applicable

The Healthy Forest Restoration Act feature class depicts National Forest System (NFS) Lands within 38 States designated under section 602 and 603 of the Healthy Forest Restoration Act. Designated areas were selected based on a set of eligibility criteria regarding forest health and do not include any areas coinciding with Wilderness and Wilderness Study Areas. The data is comprised of selected HUC-6 units or other areas of similar size and scope clipped to Proclaimed National Forest System lands. Non-Forest Service land ownership areas (inholdings) are also removed. In some cases, entire National Forests were designated. Some state designations' methodologies may differ from the national standard. Metadata and DownloadsPlease note that this data is current as of the last refresh date, and changes to designated areas will be republished and archived on a weekly basis.This record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.

Dataset contains life-cycle age group census usually resident population counts from the 2013, 2018, and 2023 Censuses, as well as the percentage change in the age group population counts between the 2013 and 2018 Censuses, and between the 2018 and 2023 Censuses. Data is available by regional council.

The life-cycle age groups are:

• under 15 years
• 15 to 29 years
• 30 to 64 years
• 65 years and over.

Map shows the percentage change in the census usually resident population count for life-cycle age groups between the 2018 and 2023 Censuses.

Download lookup file from Stats NZ ArcGIS Online or embedded attachment in Stats NZ geographic data service. Download data table (excluding the geometry column for CSV files) using the instructions in the Koordinates help guide.

​

Footnotes

Geographical boundaries

Statistical standard for geographic areas 2023 (updated December 2023) has information about geographic boundaries as of 1 January 2023. Address data from 2013 and 2018 Censuses was updated to be consistent with the 2023 areas. Due to the changes in area boundaries and coding methodologies, 2013 and 2018 counts published in 2023 may be slightly different to those published in 2013 or 2018.

​

Subnational census usually resident population

The census usually resident population count of an area (subnational count) is a count of all people who usually live in that area and were present in New Zealand on census night. It excludes visitors from overseas, visitors from elsewhere in New Zealand, and residents temporarily overseas on census night. For example, a person who usually lives in Christchurch city and is visiting Wellington city on census night will be included in the census usually resident population count of Christchurch city.

​

Caution using time series

Time series data should be interpreted with care due to changes in census methodology and differences in response rates between censuses. The 2023 and 2018 Censuses used a combined census methodology (using census responses and administrative data), while the 2013 Census used a full-field enumeration methodology (with no use of administrative data).

​

About the 2023 Census dataset

For information on the 2023 dataset see Using a combined census model for the 2023 Census. We combined data from the census forms with administrative data to create the 2023 Census dataset, which meets Stats NZ's quality criteria for population structure information. We added real data about real people to the dataset where we were confident the people who hadn’t completed a census form (which is known as admin enumeration) will be counted. We also used data from the 2018 and 2013 Censuses, administrative data sources, and statistical imputation methods to fill in some missing characteristics of people and dwellings.

​

Data quality

The quality of data in the 2023 Census is assessed using the quality rating scale and the quality assurance framework to determine whether data is fit for purpose and suitable for release. Data quality assurance in the 2023 Census has more information.

​

Quality rating of a variable

The quality rating of a variable provides an overall evaluation of data quality for that variable, usually at the highest levels of classification. The quality ratings shown are for the 2023 Census unless stated. There is variability in the quality of data at smaller geographies. Data quality may also vary between censuses, for subpopulations, or when cross tabulated with other variables or at lower levels of the classification. Data quality ratings for 2023 Census variables has more information on quality ratings by variable.

​

Age concept quality rating

Age is rated as very high quality.

Age – 2023 Census: Information by concept has more information, for example, definitions and data quality.

​

Using data for good

Stats NZ expects that, when working with census data, it is done so with a positive purpose, as outlined in the Māori Data Governance Model (Data Iwi Leaders Group, 2023). This model states that "data should support transformative outcomes and should uplift and strengthen our relationships with each other and with our environments. The avoidance of harm is the minimum expectation for data use. Māori data should also contribute to iwi and hapū tino rangatiratanga”.

​

Confidentiality

The 2023 Census confidentiality rules have been applied to 2013, 2018, and 2023 data. These rules protect the confidentiality of individuals, families, households, dwellings, and undertakings in 2023 Census data. Counts are calculated using fixed random rounding to base 3 (FRR3) and suppression of ‘sensitive’ counts less than six, where tables report multiple geographic variables and/or small populations. Individual figures may not always sum to stated totals. Applying confidentiality rules to 2023 Census data and summary of changes since 2018 and 2013 Censuses has more information about 2023 Census confidentiality rules.

Due to limitations of the shapefile format, the full Forest Management Unit data can only be downloaded using the “Complete” files under Additional Resources.Access a file geodatabase by clicking Download > Additional Resources > Complete File Geodatabase.Access a shapefile by clicking Download > Additional Resources > Complete shapefile.You can also download a full .csv copy from the link in the Additional Documentation section below. Ontario’s Crown forest is divided into geographic planning areas, known as forest management units. Most of these units are managed by individual forest companies under a Sustainable Forest License. A forest management unit is identified by an assigned official name (e.g. Black Spruce Forest) and a unique numeric code.Before any forestry activities can take place in a management unit, there must be an approved forest management plan in place for each management unit. Additional Documentation Forest Management Unit - User Guide (PDF)Forest Management Unit - Documentation (Word)Forest Management Unit - Data Description (PDF)Forest Management Unit - csv (CSV) Status On going: data is being continually updated Maintenance and Update Frequency As needed: data is updated as deemed necessary Contact Chris Ransom, Ministry of Natural Resources and Forestry, chris.ransom@ontario.ca Recommendations Not for Legal Purposes. The user must consider the FMU's source/origin when associating a spatial accuracy level to any given FMU's boundary. Only a subset of FMU boundaries originate from an FRI/OBM source (1:10000,20000). The remainder of FMU boundaries were derived from coarse scales and different map bases (Old 1:15840, 100000 etc-). The user should be mindful of the FMU implementation date (stored in NRVIS as 'Business Effective Date') in association with the business identifier, since FMU boundaries may change over a specific period in time. This is a crucial step to meet the user's requirements, especially when using historical FMU boundaries with other historical datasets, such as Forest Resource Inventories.

GeoJunxion‘s ZIP+4 is a complete dataset based on US postal data consisting of plus 35 millions of polygons​. The dataset is NOT JUST a table of spot data, which can be downloaded as csv or other text file as it happens with other suppliers​. The data can be delivered as shapefile through a single RAW data delivery or through an API​.

The January 2021 USPS data source has significantly changed since the previous delivery. Some States have sizably lower ZIP+4 totals across all counties when compared with previous deliveries due to USPS parcelpoint cleanup, while other States have a significant increase in ZIP+4 totals across all counties due to cleanup and other rezoning. California and North Carolina in particular have several new ZIP5s, contributing to the increase in distinct ZIPs and ZIP+4s​.

GeoJunxion‘s ZIP+4 data can be used as an additional layer on an existing map to run customer or other analysis, e.g. who is my customer who not, what is the density of my customer base in a certain ZIP+4 etc.

Information can be put into visual context, due to the polygons, which is good for complex overviews or management decisions. ​CRM data can be enriched with the ZIP+4 to have more detailed customer information​.

Key specifications:

Topologized ZIP polygons​

GeoJunxion ZIP+4 polygons follow USPS postal codes ​

ZIP+4 code polygons: ​

ZIP5 attributes ​

State codes. ​

Overlapping ZIP+4 ​

boundaries for multiple ZIP+4 addresses on one area​

Updated USPS source (January 2021) ​

Distinct ZIP5 codes: 34 731​

Distinct ZIP+4 codes: 35 146 957 ​

The ZIP + 4 polygons are delivered in Esri shapefile format. This format allows the storage of geometry and attribute information for each of the features. ​

The four components for the shapefile data are: ​

.shp – This file stores the geometry of the feature​

.shx –This file stores an index that stores the feature geometry​

.dbf –This file stores attribute information relating to individual features​

.prj –This file stores projection information associated with features​

​Current release version 2021. Earlier versions from previous years available on request.

​

This data is a graphic representation of natural gas utility service territories. The file has not been certified by a Professional Surveyor. This data is not suitable for legal purposes. The purpose of this data is to provide a generalized statewide view of electric service territories. The data does not include individual or commercial releases. A release is an agreement between adjoining utilities that release customers from one utility to be served by the adjoining utility. A customer release does not change the territory boundary. The file has been compiled from numerous sources and as such contains errors. The data only contains the electric utility service territories and the name of the utility.The data was derived from ESRI zipcode boundary and utility companies.

The National Pollutant Release Inventory (NPRI) is Canada's public inventory of pollutant releases (to air, water and land), disposals and transfers for recycling. The files below contain a map of Canada showing the locations of all facilities that reported disposals and transfers to the NPRI in the most recent reporting year, by reported total quantities. The map is available in both ESRI REST (to use with ARC GIS) and WMS (open source) formats. For more information about the individual reporting facilities, a dataset is available in an csv format. Please consult the following resources to enhance your analysis: - Guide on using and Interpreting NPRI Data: https://www.canada.ca/en/environment-climate-change/services/national-pollutant-release-inventory/using-interpreting-data.html - Access additional data from the NPRI, including datasets and mapping products: https://www.canada.ca/en/environment-climate-change/services/national-pollutant-release-inventory/tools-resources-data/exploredata.html

Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov