Screencast on how to export field observations with gps coordinates in Excel to a .csv file.

The Residential Schools Locations Dataset in Geodatabase format (IRS_Locations.gbd) contains a feature layer "IRS_Locations" that contains the locations (latitude and longitude) of Residential Schools and student hostels operated by the federal government in Canada. All the residential schools and hostels that are listed in the Residential Schools Settlement Agreement are included in this dataset, as well as several Industrial schools and residential schools that were not part of the IRRSA. This version of the dataset doesn’t include the five schools under the Newfoundland and Labrador Residential Schools Settlement Agreement. The original school location data was created by the Truth and Reconciliation Commission, and was provided to the researcher (Rosa Orlandini) by the National Centre for Truth and Reconciliation in April 2017. The dataset was created by Rosa Orlandini, and builds upon and enhances the previous work of the Truth and Reconcilation Commission, Morgan Hite (creator of the Atlas of Indian Residential Schools in Canada that was produced for the Tk'emlups First Nation and Justice for Day Scholar's Initiative, and Stephanie Pyne (project lead for the Residential Schools Interactive Map). Each individual school location in this dataset is attributed either to RSIM, Morgan Hite, NCTR or Rosa Orlandini. Many schools/hostels had several locations throughout the history of the institution. If the school/hostel moved from its’ original location to another property, then the school is considered to have two unique locations in this dataset,the original location and the new location. For example, Lejac Indian Residential School had two locations while it was operating, Stuart Lake and Fraser Lake. If a new school building was constructed on the same property as the original school building, it isn't considered to be a new location, as is the case of Girouard Indian Residential School.When the precise location is known, the coordinates of the main building are provided, and when the precise location of the building isn’t known, an approximate location is provided. For each residential school institution location, the following information is provided: official names, alternative name, dates of operation, religious affiliation, latitude and longitude coordinates, community location, Indigenous community name, contributor (of the location coordinates), school/institution photo (when available), location point precision, type of school (hostel or residential school) and list of references used to determine the location of the main buildings or sites. Access Instructions: there are 47 files in this data package. Please download the entire data package by selecting all the 47 files and click on download. Two files will be downloaded, IRS_Locations.gbd.zip and IRS_LocFields.csv. Uncompress the IRS_Locations.gbd.zip. Use QGIS, ArcGIS Pro, and ArcMap to open the feature layer IRS_Locations that is contained within the IRS_Locations.gbd data package. The feature layer is in WGS 1984 coordinate system. There is also detailed file level metadata included in this feature layer file. The IRS_locations.csv provides the full description of the fields and codes used in this dataset.

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

This collection consists of geospatial data layers and summary data at the country and country sub-division levels that are part of USAID's Demographic Health Survey Spatial Data Repository. This collection includes geographically-linked health and demographic data from the DHS Program and the U.S. Census Bureau for mapping in a geographic information system (GIS). The data includes indicators related to: fertility, family planning, maternal and child health, gender, HIV/AIDS, literacy, malaria, nutrition, and sanitation. Each set of files is associated with a specific health survey for a given year for over 90 different countries that were part of the following surveys:Demographic Health Survey (DHS)Malaria Indicator Survey (MIS)Service Provisions Assessment (SPA)Other qualitative surveys (OTH)Individual files are named with identifiers that indicate: country, survey year, survey, and in some cases the name of a variable or indicator. A list of the two-letter country codes is included in a CSV file.Datasets are subdivided into the following folders:Survey boundaries: polygon shapefiles of administrative subdivision boundaries for countries used in specific surveys. Indicator data: polygon shapefiles and geodatabases of countries and subdivisions with 25 of the most common health indicators collected in the DHS. Estimates generated from survey data.Modeled surfaces: geospatial raster files that represent gridded population and health indicators generated from survey data, for several countries.Geospatial covariates: CSV files that link survey cluster locations to ancillary data (known as covariates) that contain data on topics including population, climate, and environmental factors.Population estimates: spreadsheets and polygon shapefiles for countries and subdivisions with 5-year age/sex group population estimates and projections for 2000-2020 from the US Census Bureau, for designated countries in the PEPFAR program.Workshop materials: a tutorial with sample data for learning how to map health data using DHS SDR datasets with QGIS. Documentation that is specific to each dataset is included in the subfolders, and a methodological summary for all of the datasets is included in the root folder as an HTML file. File-level metadata is available for most files. Countries for which data included in the repository include: Afghanistan, Albania, Angola, Armenia, Azerbaijan, Bangladesh, Benin, Bolivia, Botswana, Brazil, Burkina Faso, Burundi, Cape Verde, Cambodia, Cameroon, Central African Republic, Chad, Colombia, Comoros, Congo, Congo (Democratic Republic of the), Cote d'Ivoire, Dominican Republic, Ecuador, Egypt, El Salvador, Equatorial Guinea, Eritrea, Eswatini (Swaziland), Ethiopia, Gabon, Gambia, Ghana, Guatemala, Guinea, Guyana, Haiti, Honduras, India, Indonesia, Jordan, Kazakhstan, Kenya, Kyrgyzstan, Lesotho, Liberia, Madagascar, Malawi, Maldives, Mali, Mauritania, Mexico, Moldova, Morocco, Mozambique, Myanmar, Namibia, Nepal, Nicaragua, Niger, Nigeria, Pakistan, Papua New Guinea, Paraguay, Peru, Philippines, Russia, Rwanda, Samoa, Sao Tome and Principe, Senegal, Sierra Leone, South Africa, Sri Lanka, Sudan, Tajikistan, Tanzania, Thailand, Timor-Leste, Togo, Trinidad and Tobago, Tunisia, Turkey, Turkmenistan, Uganda, Ukraine, Uzbekistan, Viet Nam, Yemen, Zambia, Zimbabwe

This data package contains supplementary materials related to development and validation of the Global Urban Heat Vulnerability Index (GUHVI) conducted for 8 Australian capital cities, and 9 diverse cities worldwide. This research was initiated by the Global Observatory of Healthy and Sustainable Cities for the 1000 Cities Challenge and inclusion in the Global Healthy & Sustainable City Indicators (GHSCI) open-source software.

This data package contains the following:

1. The Jupyter Notebook hosting a custom Python script that makes use of the Google Earth Engine API and geemap API to generate an overall heat vulnerability raster, three sub-index rasters, and ten input rasters.
2. POPD, SHDI, and IMR input rasters. The remaining inputs into the GUHVI are automatically fetched from cloud storage as the script runs.
3. GUHVI and iHVI visual comparison as .jpg file.
4. A folder for each of the 8 Australian cities involved in the study, containing the 14 GUHVI rasters, urban centre boundary in .shp format, and hottest third of the year date range in .txt format in the 'GUHVI Outputs' folder. The 'iHVI Outputs' folder contains the input LST, NDVI, NDBI .csv files, and the output heat vulnerability and sub-index .csv files. The 'QGIS Data' folder contains the SA1 .shp files attributed with heat vulnerability scores, and the iHVI and GUHVI comparison rasters.
5. A folder for each of the 9 international cities involved in the study, containing the 14 GUHVI rasters, urban centre boundary in .shp format, hottest third of the year date range in .txt format, and the QGIS project file provided to collaborators for validation.
6. R scripts for generating the normalized mean results, population percentage per heat vulnerability class table, and combined box, half-violin and strip plots for each city.
7. The instructional video provided to collaborators as a .mp4 file, which outlines how to navigate the QGIS project, and how to access and record comments in the live spreadsheet.
8. The complete validation spreadsheet with comments included as a .pdf file.
9. Supplementary tables listing the urban centre boundary source files for each city, and the OpenStreetMap data source used to perform the coastal pixel overlap methodology as a .pdf file.

UNI-CEN Standardized Census Data Tables contain Census data that have been reformatted into a common table format with standardized variable names and codes. The data are provided in two tabular formats for different use cases. "Long" tables are suitable for use in statistical environments, while "wide" tables are commonly used in GIS environments. The long tables are provided in Stata Binary (dta) format, which is readable by all statistics software. The wide tables are provided in comma-separated values (csv) and dBase 3 (dbf) formats with codebooks. The wide tables are easily joined to the UNI-CEN Digital Boundary Files. For the csv files, a .csvt file is provided to ensure that column data formats are correctly formatted when importing into QGIS. A schema.ini file does the same when importing into ArcGIS environments. As the DBF file format supports a maximum of 250 columns, tables with a larger number of variables are divided into multiple DBF files. For more information about file sources, the methods used to create them, and how to use them, consult the documentation at https://borealisdata.ca/dataverse/unicen_docs. For more information about the project, visit https://observatory.uwo.ca/unicen.

Introduction

We are enclosing the database used in our research titled "Concentration and Geospatial Modelling of Health Development Offices' Accessibility for the Total and Elderly Populations in Hungary", along with our statistical calculations. For the sake of reproducibility, further information can be found in the file Short_Description_of_Data_Analysis.pdf and Statistical_formulas.pdf

The sharing of data is part of our aim to strengthen the base of our scientific research. As of March 7, 2024, the detailed submission and analysis of our research findings to a scientific journal has not yet been completed.

The dataset was expanded on 23rd September 2024 to include SPSS statistical analysis data, a heatmap, and buffer zone analysis around the Health Development Offices (HDOs) created in QGIS software.

Short Description of Data Analysis and Attached Files (datasets):

Our research utilised data from 2022, serving as the basis for statistical standardisation. The 2022 Hungarian census provided an objective basis for our analysis, with age group data available at the county level from the Hungarian Central Statistical Office (KSH) website. The 2022 demographic data provided an accurate picture compared to the data available from the 2023 microcensus. The used calculation is based on our standardisation of the 2022 data. For xlsx files, we used MS Excel 2019 (version: 1808, build: 10406.20006) with the SOLVER add-in.

Hungarian Central Statistical Office served as the data source for population by age group, county, and regions: https://www.ksh.hu/stadat_files/nep/hu/nep0035.html, (accessed 04 Jan. 2024.) with data recorded in MS Excel in the Data_of_demography.xlsx file.

In 2022, 108 Health Development Offices (HDOs) were operational, and it's noteworthy that no developments have occurred in this area since 2022. The availability of these offices and the demographic data from the Central Statistical Office in Hungary are considered public interest data, freely usable for research purposes without requiring permission.

The contact details for the Health Development Offices were sourced from the following page (Hungarian National Population Centre (NNK)): https://www.nnk.gov.hu/index.php/efi (n=107). The Semmelweis University Health Development Centre was not listed by NNK, hence it was separately recorded as the 108th HDO. More information about the office can be found here: https://semmelweis.hu/egeszsegfejlesztes/en/ (n=1). (accessed 05 Dec. 2023.)

Geocoordinates were determined using Google Maps (N=108): https://www.google.com/maps. (accessed 02 Jan. 2024.) Recording of geocoordinates (latitude and longitude according to WGS 84 standard), address data (postal code, town name, street, and house number), and the name of each HDO was carried out in the: Geo_coordinates_and_names_of_Hungarian_Health_Development_Offices.csv file.

The foundational software for geospatial modelling and display (QGIS 3.34), an open-source software, can be downloaded from:

https://qgis.org/en/site/forusers/download.html. (accessed 04 Jan. 2024.)

The HDOs_GeoCoordinates.gpkg QGIS project file contains Hungary's administrative map and the recorded addresses of the HDOs from the

Geo_coordinates_and_names_of_Hungarian_Health_Development_Offices.csv file,

imported via .csv file.

The OpenStreetMap tileset is directly accessible from www.openstreetmap.org in QGIS. (accessed 04 Jan. 2024.)

The Hungarian county administrative boundaries were downloaded from the following website: https://data2.openstreetmap.hu/hatarok/index.php?admin=6 (accessed 04 Jan. 2024.)

HDO_Buffers.gpkg is a QGIS project file that includes the administrative map of Hungary, the county boundaries, as well as the HDO offices and their corresponding buffer zones with a radius of 7.5 km.

Heatmap.gpkg is a QGIS project file that includes the administrative map of Hungary, the county boundaries, as well as the HDO offices and their corresponding heatmap (Kernel Density Estimation).

A brief description of the statistical formulas applied is included in the Statistical_formulas.pdf.

Recording of our base data for statistical concentration and diversification measurement was done using MS Excel 2019 (version: 1808, build: 10406.20006) in .xlsx format.

• Aggregated number of HDOs by county: Number_of_HDOs.xlsx
• Standardised data (Number of HDOs per 100,000 residents): Standardized_data.xlsx
• Calculation of the Lorenz curve: Lorenz_curve.xlsx
• Calculation of the Gini index: Gini_Index.xlsx
• Calculation of the LQ index: LQ_Index.xlsx
• Calculation of the Herfindahl-Hirschman Index: Herfindahl_Hirschman_Index.xlsx
• Calculation of the Entropy index: Entropy_Index.xlsx
• Regression and correlation analysis calculation: Regression_correlation.xlsx

Using the SPSS 29.0.1.0 program, we performed the following statistical calculations with the databases Data_HDOs_population_without_outliers.sav and Data_HDOs_population.sav:

• Regression curve estimation with elderly population and number of HDOs, excluding outlier values (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_elderly_without_outlier.spv
• Pearson correlation table between the total population, elderly population, and number of HDOs per county, excluding outlier values such as Budapest and Pest County: Pearson_Correlation_populations_HDOs_number_without_outliers.spv.
• Dot diagram including total population and number of HDOs per county, excluding outlier values such as Budapest and Pest Counties: Dot_HDO_total_population_without_outliers.spv.
• Dot diagram including elderly (64<) population and number of HDOs per county, excluding outlier values such as Budapest and Pest Counties: Dot_HDO_elderly_population_without_outliers.spv
• Regression curve estimation with total population and number of HDOs, excluding outlier values (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_without_outlier.spv
• Dot diagram including elderly (64<) population and number of HDOs per county: Dot_HDO_elderly_population.spv
• Dot diagram including total population and number of HDOs per county: Dot_HDO_total_population.spv
• Pearson correlation table between the total population, elderly population, and number of HDOs per county: Pearson_Correlation_populations_HDOs_number.spv
• Regression curve estimation with total population and number of HDOs, (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_total_population.spv

For easier readability, the files have been provided in both SPV and PDF formats.

The translation of these supplementary files into English was completed on 23rd Sept. 2024.

If you have any further questions regarding the dataset, please contact the corresponding author: domjan.peter@phd.semmelweis.hu

Here is an image of the global municipal tax (founcier bati + habitation). Average tax per asset Nancy 2014

To do it again you will need: — QGIS software (Free: https://www.qgis.org/fr/site/forusers/download.html), — a qgs file of your department (http://www.actualitix.com/shapefiles-des-departements-de-france.html) — an export of tax rates (https://www.data.gouv.fr/fr/datasets/impots-locaux/ > Municipal and intercommunal data > Your Department > Local Direct Tax Data 2014 (XLS format)) — data (most days of INSEE here 2012 http://www.insee.fr/fr/themes/detail.asp?reg_id=99&ref_id=base-cc-emploi-pop-active-2012)

Operating Mode: — process your data in your favorite spreadsheet (Excel or OpenOffice Calc) by integrating impot data, and INSEE to pull out the numbers that seem revealing to you — Install QGIS — Open the.qgs of your department

Add columns — Right click property on the main layer — Go to the field menu (on the left) — Add (via pencil) the desired columns (here average housing tax per asset, average property tax per asset, and the sum of both) — These are reals of precision 2, and length 6 — Register

Insert data: — Right-click on the “Open attribute table” layer — Select all — Copy — Paste in excel (or openOffice calcs) — Put the ad hoc formulas in excel (SOMME.SI.ENS to recover the rate) — Save the desired tab in CSV DOS with the new values — In QGIS > Menu > Layer > Add a delimited layer of text — Import the CSV

Present the data: — To simplify I advise you to make a layer by rate, and layers sums. So rots you in three clicks out the image of the desired rate — For each layer (or rate) — Right click properties on the csv layer — Labels to add city name and desired rate — Style for fct coloring of a csv field

Print the data in pdf: — To print, you need to define a print template — In the menu choose new printing dialer — choose the format (a department in A0 is rather readable) — Add vas legend, scale, and other — Print and here...

NB: this method creates aberrations: — in the case where the INSEE does not have a number or numbers that have moved a lot since — it is assumed that only assets pay taxes (which is more fair, but not 100 %)

This dataset maps the location of anti-social graffiti around the University of Edinburgh's central campus. The data was collected over a 2 week period between the 19th May and the 2nd June 2014. The data was collected using a smartphone through an app called Fieldtrip GB (http://fieldtripgb.blogs.edina.ac.uk/). Multiple asset collectors were deployed to use a pre-defined data collection form which allowed users to log the following attributes: Date / Name of asset collector / Type of graffiti (image/tag/words/advert/.....) / What the graffiti was on (building/wall/lamppost/....) / What medium was used (paint/paper/chalk/....) / Density of graffiti / Photograph / Location. The data is by no means complete and realistically captured only around 50% of the graffiti in the study area. It is hoped that this dataset will be updated every 3 months to chart the distribution of graffiti over time. data was collected using the app Fieldtrip GB Once collected, data from multiple asset collectors was merged in FtGB's authoring tool and exported as a CSV file. This was then imported into QGIS and saved as a vector dataset in ESRI Shapefile format. GIS vector data. This dataset was first accessioned in the EDINA ShareGeo Open repository on 2014-06-06 and migrated to Edinburgh DataShare on 2017-02-22.

This data set includes yearly maps of land cover classification for the state of Mato Grosso, Brasil, from 2001 to 2017, based on MODIS image time series (collection 6) at 250 meter spatial resolution (product MOD13Q1).

Ground samples consisting of 1,892 time series with known labels are used as training data for a support vector machine classifier. We used the radial basis function kernel, with cost C=1 and gamma = 0.01086957. The classes include natural and human-transformed land areas, discriminating among different agricultural crops in state of Land cover change maps for Mato Grosso State in BrazilMato Grosso, Brazil's agricultural frontier. The results provide spatially explicit estimates of productivity increases in agriculture as well as the trade-offs between crop and pasture expansion.

Quality assessment using a 5-fold cross-validation of the training samples indicates an overall accuracy of 96% and the following user's and producer's accuracy for the land cover classes:

Cerrado: UA - 98% PA - 99% Fallow_Cotton UA - 96% PA - 93% Forest UA - 99% PA - 98% Pasture UA - 97% PA - 98% Soy-Corn UA- 91% PA - 93% Soy-Cotton UA - 97% PA - 97% Soy-Fallow UA - 98% PA - 98% Soy-Millet UA- 90% PA - 89% Soy-Sunflower UA - 77% PA - 65%

The correlation coefficients between the agricultural areas classified by our method and the estimates by IBGE (Brazil's Census Bureau) for the harvests from 2001 to 2017, were equal to 0.98. At state level the soybean, cotton, corn and sunflower areas had a correlation equal 0.97, 0.85, 0.98 and 0.80.

The areas classified as forest were compared with the Hansen et al. (2013) mapping for the year 2000. In order to separate the forest areas, we examined the areas with more than 25% tree cover on the Hansen et al. (2013, doi:10.1126/science.1244693) map. We found that 99% of the pixels classified as forest match the pixels indicated by Hansen et al. (2013) as having more than 25% tree cover. When we joined the cerrado and forest classes, 84% of the pixels match the pixels by Hansen et al. (2013, doi:10.1126/science.1244693) as having more than 25% tree cover.

The pixels labelled as pasture were compared to the pasture mapping done by Parente et al. (2017, doi:10.1016/j.jag.2017.06.003) . We found that 80% of the pixels classified as pasture match the pixels indicated by Parente et al. (2017, doi:10.1016/j.jag.2017.06.003) for the state of Mato Grosso.

In the data set "Land cover change maps for Mato Grosso State in Brazil version 2", we analysed the samples from the clustering process using self-organizing maps. The samples with high level of confusion were removed from the dataset. In addition, we used a Bayesian smoothing method to reclassify the pixels based on machine learning probabilities associated to each class and each pixel. The main rationale is to change those pixels classes with low certainty (high entropy) to the neighborhood classes with high certainty (low entropy) using a Bayesian inference. To reclassify pixels we used a 3x3 window from which we computed the neighborhood entropy.

The following data sets are provided: (a) The classified maps in compressed TIFF format (one per year) at MODIS resolution. (b) A QGIS style file for displaying the data in the QGIS software (c) An csv file with the training data set (1,892 ground samples).

The software used to produce the analysis is available as open source on https://github.com/e-sensing.

Note: The TIFF raster files use the Sinusoidal Projection, which is the same cartographical projection used by the input MODIS images. When opening the TIFF raster maps in QGIS, to ensure correct navigation please use the Sinusoidal Projection, by selecting in QGIS projection menu, the following option: "Generated CRS (+proj=sinu +lon_0=0 +x_0=0 +y_0=0 +a=6371007.181 +b=6371007.181 +units=m +no_defs)"

Survey results are available in two seperate formats. The .csv output contains all non-spatial data from the main survey form, and can be loaded in spreadsheet programs such as Microsoft Excel. The spatial content of the survey is available as a zipped collection of one or more shapefiles. These files can be opened in GIS applications such as ArcGISor QGIS. Please note, only completed survey responses are exported. Those still in draft will be excluded.Output columns in both the CSV and shapefile formats are named based on the exportidspecified in the form field configuration. If you are looking to analyze spatial data from the shapefiles based on attributes collected in the main response form, you can join fields from the CSV file with spatial features by joining on the RESPONSE_ID field.

Dataset for "Fresh rockfalls near the landing site of ExoMars Rosalind Franklin Rover: drivers, trafficability, and implications".

The catalog contains rockfall locations (shapefiles compatible with QGIS/ArcGIS and a .csv file).

Summary:

The files contained herein represent green roof footprints in NYC visible in 2016 high-resolution orthoimagery of NYC (described at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_AerialImagery.md). Previously documented green roofs were aggregated in 2016 from multiple data sources including from NYC Department of Parks and Recreation and the NYC Department of Environmental Protection, greenroofs.com, and greenhomenyc.org. Footprints of the green roof surfaces were manually digitized based on the 2016 imagery, and a sample of other roof types were digitized to create a set of training data for classification of the imagery. A Mahalanobis distance classifier was employed in Google Earth Engine, and results were manually corrected, removing non-green roofs that were classified and adjusting shape/outlines of the classified green roofs to remove significant errors based on visual inspection with imagery across multiple time points. Ultimately, these initial data represent an estimate of where green roofs existed as of the imagery used, in 2016.

These data are associated with an existing GitHub Repository, https://github.com/tnc-ny-science/NYC_GreenRoofMapping, and as needed and appropriate pending future work, versioned updates will be released here.

Terms of Use:

The Nature Conservancy and co-authors of this work shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any sale, distribution, loan, or offering for use of these digital data, in whole or in part, is prohibited without the approval of The Nature Conservancy and co-authors. The use of these data to produce other GIS products and services with the intent to sell for a profit is prohibited without the written consent of The Nature Conservancy and co-authors. All parties receiving these data must be informed of these restrictions. Authors of this work shall be acknowledged as data contributors to any reports or other products derived from these data.

Associated Files:

As of this release, the specific files included here are:

• GreenRoofData2016_20180917.geojson is in the human-readable, GeoJSON format, in geographic coordinates (Lat/Long, WGS84; EPSG 4263).
• GreenRoofData2016_20180917.gpkg is in the GeoPackage format, which is an Open Standard readable by most GIS software including Esri products (tested on ArcMap 10.3.1 and multiple versions of QGIS). This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917_Shapefile.zip is a zipped folder containing a Shapefile and associated files. Please note that some field names were truncated due to limitations of Shapefiles, but columns are in the same order as for other files and in the same order as listed below. This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917.csv is a comma-separated values file (CSV) with coordinates for centroids for the green roofs stored in the table itself. This allows for easily opening the data in a tool like spreadsheet software (e.g., Microsoft Excel) or a text editor.

Column Information for the datasets:

Some, but not all fields were joined to the green roof footprint data based on building footprint and tax lot data; those datasets are embedded as hyperlinks below.

• fid - Unique identifier
• bin - NYC Building ID Number based on overlap between green roof areas and a building footprint dataset for NYC from August, 2017. (Newer building footprint datasets do not have linkages to the tax lot identifier (bbl), thus this older dataset was used). The most current building footprint dataset should be available at: https://data.cityofnewyork.us/Housing-Development/Building-Footprints/nqwf-w8eh. Associated metadata for fields from that dataset are available at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_BuildingFootprints.md.
• bbl - Boro Block and Lot number as a single string. This field is a tax lot identifier for NYC, which can be tied to the Digital Tax Map (http://gis.nyc.gov/taxmap/map.htm) and PLUTO/MapPLUTO (https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page). Metadata for fields pulled from PLUTO/MapPLUTO can be found in the PLUTO Data Dictionary found on the aforementioned page. All joins to this bbl were based on MapPLUTO version 18v1.
• gr_area - Total area of the footprint of the green roof as per this data layer, in square feet, calculated using the projected coordinate system (EPSG 2263).
• bldg_area - Total area of the footprint of the associated building, in square feet, calculated using the projected coordinate system (EPSG 2263).
• prop_gr - Proportion of the building covered by green roof according to this layer (gr_area/bldg_area).
• cnstrct_yr - Year the building was constructed, pulled from the Building Footprint data.
• doitt_id - An identifier for the building assigned by the NYC Dept. of Information Technology and Telecommunications, pulled from the Building Footprint Data.
• heightroof - Height of the roof of the associated building, pulled from the Building Footprint Data.
• feat_code - Code describing the type of building, pulled from the Building Footprint Data.
• groundelev - Lowest elevation at the building level, pulled from the Building Footprint Data.
• qa - Flag indicating a positive QA/QC check (using multiple types of imagery); all data in this dataset should have 'Good'
• notes - Any notes about the green roof taken during visual inspection of imagery; for example, it was noted if the green roof appeared to be missing in newer imagery, or if there were parts of the roof for which it was unclear whether there was green roof area or potted plants.
• classified - Flag indicating whether the green roof was detected image classification. (1 for yes, 0 for no)
• digitized - Flag indicating whether the green roof was digitized prior to image classification and used as training data. (1 for yes, 0 for no)
• newlyadded - Flag indicating whether the green roof was detected solely by visual inspection after the image classification and added. (1 for yes, 0 for no)
• original_source - Indication of what the original data source was, whether a specific website, agency such as NYC Dept. of Parks and Recreation (DPR), or NYC Dept. of Environmental Protection (DEP). Multiple sources are separated by a slash.
• address - Address based on MapPLUTO, joined to the dataset based on bbl.
• borough - Borough abbreviation pulled from MapPLUTO.
• ownertype - Owner type field pulled from MapPLUTO.
• zonedist1 - Zoning District 1 type pulled from MapPLUTO.
• spdist1 - Special District 1 pulled from MapPLUTO.
• bbl_fixed - Flag to indicate whether bbl was manually fixed. Since tax lot data may have changed slightly since the release of the building footprint data used in this work, a small percentage of bbl codes had to be manually updated based on overlay between the green roof footprint and the MapPLUTO data, when no join was feasible based on the bbl code from the building footprint data. (1 for yes, 0 for no)

For GreenRoofData2016_20180917.csv there are two additional columns, representing the coordinates of centroids in geographic coordinates (Lat/Long, WGS84; EPSG 4263):

• xcoord - Longitude in decimal degrees.
• ycoord - Latitude in decimal degrees.

Acknowledgements:

This work was primarily supported through funding from the J.M. Kaplan Fund, awarded to the New York City Program of The Nature Conservancy, with additional support from the New York Community Trust, through New York City Audubon and the Green Roof Researchers Alliance.

Update NotesMar 16 2024, remove spaces in the file and folder names.Mar 31 2024, delete the underscore in the city names with a space (such as San Francisco) in the '02_TransCAD_results' folder to ensure correct data loading by TransCAD (software version: 9.0).Aug 31 2024, add the 'cityname_link_LinkFlows.csv' file in the '02_TransCAD_results' folder to match the link from input data and the link from TransCAD results (LinkFlows) with the same Link_ID.IntroductionThis is a unified and validated traffic dataset for 20 US cities. There are 3 folders for each city.01 Input datathe initial network data obtained from OpenStreetMap (OSM)the visualization of the OSM dataprocessed node / link / od data02 TransCAD results (software version: 9.0)cityname.dbd : geographical network database of the city supported by TransCAD (version 9.0)cityname_link.shp / cityname_node.shp : network data supported by GIS software, which can be imported into TransCAD manually. Then the corresponding '.dbd' file can be generated for TransCAD with a version lower than 9.0od.mtx : OD matrix supported by TransCADLinkFlows.bin / LinkFlows.csv : traffic assignment results by TransCADcityname_link_LinkFlows.csv: the input link attributes with the traffic assignment results by TransCADShortestPath.mtx / ue_travel_time.csv : the traval time (min) between OD pairs by TransCAD03 AequilibraE results (software version: 0.9.3)cityname.shp : shapefile network data of the city support by QGIS or other GIS softwareod_demand.aem : OD matrix supported by AequilibraEnetwork.csv : the network file used for traffic assignment in AequilibraEassignment_result.csv : traffic assignment results by AequilibraEPublicationXu, X., Zheng, Z., Hu, Z. et al. (2024). A unified dataset for the city-scale traffic assignment model in 20 U.S. cities. Sci Data 11, 325. https://doi.org/10.1038/s41597-024-03149-8Usage NotesIf you use this dataset in your research or any other work, please cite both the dataset and paper above.A brief introduction about how to use this dataset can be found in GitHub. More detailed illustration for compiling the traffic dataset on AequilibraE can be referred to GitHub code or Colab code.ContactIf you have any inquiries, please contact Xiaotong Xu (email: kid-a.xu@connect.polyu.hk).

Introduction This travel time matrix records travel times and travel distances for routes between all centroids (N = 13231) of a 250 × 250 m grid over the populated areas in the Helsinki metropolitan area by walking, cycling, public transportation, and private car. If applicable, the routes have been calculated for different times of the day (rush hour, midday, off-peak), and assuming different physical abilities (such as walking and cycling speeds), see details below. The grid follows the geometric properties and enumeration of the versatile Yhdyskuntarakenteen seurantajärjestelmä (YKR) grid used in applications across many domains in Finland, and covers the municipalities of Helsinki, Espoo, Kauniainen, and Vantaa in the Finnish capital region. Data formats The data is available in multiple different formats that cater to different requirements, such as different software environments. All data formats share a common set of columns (see below), and can be used interchangeably. Helsinki_Travel_Time_Matrix_2023.csv.zst: comma-separated values (CSV) of all data columns, without geometries. This data set contains all routes in one file, and can be filtered by origin or destination according to the analysis at hand. The data records can also be joined to the geometries as available below. The file is compressed using the Zstandard algorithm, that many data science libraries, for instance, pandas, support transparently, directly, and automatically. Helsinki_Travel_Time_Matrix_2023_travel_times.gpkg.zip: an OGC GeoPackage standard file containing all data columns and the geometries that relate to the destination grid cell. The data set is delivered as a ZIP archive, which many GIS systems and libraries, e.g., GDAL/OGR, QGIS, or geopandas, support natively. Helsinki_Travel_Matrix_2023_travel_times.csv.zip: a set of 13231 comma-separated value files containing the routes to one destination grid cell each. The files contain all data columns, no geometry, and can be joined to the geometries as available below. Filenames of the individual files within the ZIP archive follow the pattern Helsinki_Travel_Time_Matrix_2023_travel_times_to_5787545.csv where 5787545 is replaced by the to_id by which the rows in the file are grouped. Use the from_id column to join with the geometries from one of the files below. Geometry, only: Helsinki_Travel_Time_Matrix_2023_grid.gpkg.zip: an OGC GeoPackage standard file containing the geometries and IDs of the grid used in the analysis. This file can be joined both to the from_id and to_id columns of the data files. The data set is delivered as a ZIP archive, which many GIS systems and libraries, e.g., GDAL/OGR, QGIS, or geopandas, support natively. Helsinki_Travel_Time_Matrix_2023_grid.shp.zip: an ESRI Shapefile archive containing the geometries and IDs of the grid used in the analysis. This file can be joined both to the from_id and to_id columns of the data files. Table structure from_id ID number of the origin grid cell to_id ID number of the destination grid cell walk_avg Travel time in minutes from origin to destination by walking at an average speed walk_slo Travel time in minutes from origin to destination by walking slowly bike_avg Travel time in minutes from origin to destination by cycling at an average speed; incl. extra time (1 min) to unlock and lock bicycle bike_fst Travel time in minutes from origin to destination by cycling fast; incl. extra time (1 min) to unlock and lock bicycle bike_slo Travel time in minutes from origin to destination by cycling slowly; incl. extra time (1 min) to unlock and lock bicycle pt_r_avg Travel time in minutes from origin to destination by public transportation in rush hour traffic, walking at an average speed pt_r_slo Travel time in minutes from origin to destination by public transportation in rush hour traffic, walking at a slower speed pt_m_avg Travel time in minutes from origin to destination by public transportation in midday traffic, walking at an average speed pt_m_slo Travel time in minutes from origin to destination by public transportation in midday traffic, walking at a slower speed pt_n_avg Travel time in minutes from origin to destination by public transportation in nighttime traffic, walking at an average speed pt_n_slo Travel time in minutes from origin to destination by public transportation in nighttime traffic, walking at a lower speed car_r Travel time in minutes from origin to destination by private car in rush hour traffic car_m Travel time in minutes from origin to destination by private car in midday traffic car_n Travel time in minutes from origin to destination by private car in nighttime traffic walk_d Distance from origin to destination, in metres, on foot Data for 2013, 2015, and 2018 At the Digital Geography Lab, we started computing travel time matrices in 2013. Our methodology has changed in between the iterations, and naturally, there are systematic differences between the iter

This dataset is a part of research work titled: "Investigation of Oil Well Blowouts Triggered by Wastewater Injection in the Permian Basin, USA."

Authors:
Vamshi Karanam, Zhong Lu, Jin-Woo Kim, Roger P Denlinger

The folder contains six datasets. They are explained in detail below.

1. Deformation rate map
filename: deformation_rate.geojson
The data can be accessed using QGIS, ArcGIS or other GIS software
The attribute table contains:
field_0: point number
field_1:Code
field_2:height
field_3: height standard deviation
field_4:deformation rate (mm/yr)
field_5:standard deviation of deformation rate
field_6: Coherence
field_7: effective area

2. Monthly njection volumes
filename: injection_volumes.geojson
The data can be accessed using QGIS, ArcGIS or other GIS software
The attributes table contains:
field_0: API Number
field_1 to field_150: Monthly injection volumes from 20100101 to 20220601 (m^3)
field_151: Longitude
field_152 : Latitude

3. Depth to the top of formations
filename: main_formations_new.geojson
The data can be accessed using QGIS, ArcGIS or other GIS software
The attribute table contains:
field_0: API Number
field_1 to field_12: Depth to top of different formations (m)
field_13: True depth of the well (m)
field_14: Latitude
field_15: Longitude

4. Blowout Modeling results
This dataset contains six files as follows:
i. blowout_bestfit_alpha.mat: best fit parameters for the Modeling of sill alpha.
ii. blowout_bestfit_alpha_summary.mat: summary of the best fit parameters for the Modeling of sill alpha
iii. blowout_bestfit_beta.mat: best fit parameters for the Modeling of sill beta
iv. blowout_bestfit_beta_summary.mat: summary of the best fit parameters for the Modeling of sill beta
v. blowout_bestfit_results.csv: Best fit results of the penny crack modeling. The csv file contains five columns: Longitude, Latitude, Observed deformation, Modeled deformation and Residual
vi. blowout_input_data.mat: Input data for the modeling of blowout. The mat file contains five files. InSAR Phase (Phase), Incidence angle (Inc), Heading angle (Heading), Longitude (Lon), Latitude (Lat)

5. Cumulative uplift Modeling results
This dataset contains six files as follows:
i. uplift_bestfit_alpha.mat: best fit parameters for the Modeling of sill alpha.
ii. uplift_bestfit_alpha_summary.mat: summary of the best fit parameters for the Modeling of sill alpha
iii. uplift_bestfit_beta.mat: best fit parameters for the Modeling of sill beta
iv. uplift_bestfit_beta_summary.mat: summary of the best fit parameters for the Modeling of sill beta
v. uplift_bestfit_results.csv: Best fit results of the penny crack modeling. The csv file contains five columns: Longitude, Latitude, Observed deformation, Modeled deformation and Residual
vi. uplift_input_data.mat: Input data for the modeling of cumulative uplift. The mat file contains five files. InSAR Phase (Phase), Incidence angle (Inc), Heading angle (Heading), Longitude (Lon), Latitude (Lat)

6. Metadata for the Sentinel-1 datasets used in this study

i. sentinel_1_datasets_descending.csv: CSV file with filenames, date of acquisition and other metadata along with URL to access the datasets in descending geometry

ii. sentinel_1_datasets_ascending.csv: CSV file with filenames, date of acquisition and other metadata along with URL to access the datasets in ascending geometry

This dataset provides all output data generated in the standard settings of HANZE v2.0 model. The 100-m pan-European maps (GeoTIFF) provide gridded totals of five variables for years 1870-2020 for 42 countries. The rasters are group in five ZIP files:

• CLC: land cover/use (Corine Land Cover classification; legend files are included in a separate ZIP)

• Pop: population

• GDP: gross domestic product (2020 euros)

• FA: fixed asset value (2020 euros)

• imp: imperviousness density (%)

Two additional CSV files contain uncertainty estimates of population, GDP and fixed asset value per NUTS3 region and flood hazard zone. The files provide 5th, 20th, 50th, 80th and 95th percentile for all timesteps, separately for coastal and riverine floods.

Two further Excel files contain subnational and national-level statistical data on population, land use and economic variables.

For detailed description of the files, see the documentation provided with the code.

This version replaces the airport list, which was previously incorrectly taken from HANZE v1, and adds land cover/use legend files for ArcGIS and QGIS.

UNI-CEN Standardized Census Data Tables contain Census data that have been reformatted into a common table format with standardized variable names and codes. The data are provided in two tabular formats for different use cases. "Long" tables are suitable for use in statistical environments, while "wide" tables are commonly used in GIS environments. The long tables are provided in Stata Binary (dta) format, which is readable by all statistics software. The wide tables are provided in comma-separated values (csv) and dBase 3 (dbf) formats with codebooks. The wide tables are easily joined to the UNI-CEN Digital Boundary Files. For the csv files, a .csvt file is provided to ensure that column data formats are correctly formatted when importing into QGIS. A schema.ini file does the same when importing into ArcGIS environments. As the DBF file format supports a maximum of 250 columns, tables with a larger number of variables are divided into multiple DBF files. For more information about file sources, the methods used to create them, and how to use them, consult the documentation at https://borealisdata.ca/dataverse/unicen_docs. For more information about the project, visit https://observatory.uwo.ca/unicen.