• An image raster of Day Land Surface Temperature (LSTDAY) of September 2016;- An image raster of Normalized Difference Vegetation Index (NDVI) of September 2016;- A polygonal shapefile of disease distribution of 'West Nile Disease' in the world in 2016;- A punctual shapefile of outbreaks of 'West Nile Disease' in the world in 2016;- An excel file containing an extract from the 'west nile' outbreaks of 2016 with associated day and night temperature data and vegetation indices, each in a dedicated sheet of the excel file

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 dataset contains X-ray diffraction (XRD) data taken from wells and outcrops as part of the DOE GTO supported Utah FORGE project located near Roosevelt Hot Springs. It contains an Excel spreadsheet with the XRD data, a text file with sample site names, types, and locations in UTM, Zone 12, NAD83 coordinates, and a GIS shapefile of the sample locations with attributes.

The polygon dataset represents predicted indoor radon screening levels in counties across the United States. These data were provided by EPA’s Office of Radiation and Indoor Air as an Excel spreadsheet. In order to produce the Web mapping application, the Excel file was joined with a shapefile of U.S. county boundaries downloaded from the U.S. Census Bureau. Those two sets of data were then converted into a single polygon feature class inside a file geodatabase.

Sediment grab samples were taken in summer of 2017 and 2018 using a modified van Veen grab sampler. A sub-sample of the top two centimeters was taken for further lab analysis. Dried and homogenized splits of the samples were analyzed for chemical composition using an Innov-X Alpha series 4000 XRF (Innov-X Systems, Woburn, MA). The results of the measurements are presented as ppm. The XRF analytical protocol included the following elements: P, S, Cl, K, Ca, Ti, V, Cr, Mn, Fe, Co, Ni, Cu, Zn As, Se, Br, Rb, Sr, Zr, Mo, Ag, Cd, Sn, Sb, I, Ba, Hg, Pb, Bi, Th, and U. However, only Cl, K, Ca, Ti, Cr, Mn, Fe, Co, Cu, Zn, As, Br, Rb, Sr, Zr and Pb were consistently present at levels above background detection in surficial sediments collected in the LIS Phase II area. The data is presented here as an ESRI shapefile. There is an accompanying Excel spreadsheet. Funding was provided by the Long Island Sound Mapping Fund administered cooperatively by the EPA Long Island Sound Study and the Connecticut Department of Energy and Environmental Protection (DEEP).

2024 General Election Voting Precincts County voting precincts are the geographic units established by county commissioners courts for the purpose of election administration. Precincts can be bounded by visible or nonvisible features. Council staff collect precinct boundary changes from county officials for each statewide primary and general election. Precincts24G.zip - 2024 general election (24G) voting precincts shapefile The precincts shapefile (.shp) is provided in a compressed file (.zip) format. Precincts24G_Districts.xlsx - Excel file with 24G precincts related to district plans for the 2024 elections The Excel file (.xlsx) relates 2024 general election voting precincts to congressional, state senate, state house, and State Board of Education districts. The file was created by converting each precinct polygon into a point location within the precinct and joining the points to district plans for the 2024 elections. The file contains the following fields: FIPS - Census County Code (txt) COUNTY - County Name (txt) PREC - Voting Precinct Name (txt) <--Note: This field is text PCTKEY - Unique Identifier (txt) PlanC2193 - Texas Congressional District (num) PlanH2316 - State House District (num) PlanS2168 - State Senate District (num) PlanE2106 - State Board of Education District (num) Previous vintages of collected precinct data from the 2020s are also available for download: Precincts24P.zip - 2024 primary election (24P) voting precincts shapefile Precincts24P_Districts.xlsx - Excel file with 24P precincts related to district plans for the 2024 elections Precincts22G.zip - 2022 general election (22G) voting precincts shapefile Precincts22G_Districts.xlsx - Excel file with 22G precincts related to district plans for the 2022 elections Precincts22P_20220518.zip - 2022 primary election (22P) voting precincts shapefile Precincts22P_Districts_20220518.xlsx - Excel file with 22P precincts related to district plans for the 2022 elections Precincts20G_2020.zip - 2020 general election (20G) voting precincts shapefile Precincts20G_Districts_2020.xlsx - Excel file with 20G precincts related to district plans for the 2020 elections The council's precinct collection should be used as a reference for determining the boundaries of county voting precincts. Please consult the appropriate county agency or county election official for additional information regarding voting precinct boundaries.

The shape file GWB_horizon_public_h0 comprises all Ground Water Bodies of Spain lacking a horizon allocation and all GWBs of Estonia. The dbf tables of the shape files include the columns “EU_CD_GW” as the GWB identifier and “Horizon” describing the vertical positioning. The polygon identifier “Polygon_ID” was added subsequently, because some GWBs consist of several polygons with identical “EU_CD_GW”even in the same horizon. Some further GWB characteristics are provided with the Microsoft Excel file “GWB_attributes_2012June.xls” including the column “EU_CD_GW”, which serves as a key for joining spatial and attribute data. There is no corresponding spatial data for GWBs in the Microsoft Excel table without an entry in column “EU_CD_GW”. The spatial resolution is given for about a half of the GWBs in the column "Scale" of the xls file, which is varying between the MS from 1:10,000 to 1:1,000,000 and mostly in the range from 1:50,000 to 1:250,000.

Modeled Bouger-Corrected Gravity data was extracted from the Pan American Center for Earth and Environmental Studies Gravity Database of the U.S. at http://irpsrvgis08.utep.edu/viewers/Flex/GravityMagnetic/GravityMagnetic_CyberShare/ on 2/29/2012. The downloaded text file was opened in an Excel spreadsheet. This spreadsheet data was then converted into an ESRI point shapefile in UTM Zone 13 NAD27 projection, showing location and gravity (in milligals). This data was then converted to grid and then contoured using ESRI Spatial Analyst.

Data from From University of Texas: Pan American Center for Earth and Environmental Studies Zip file containing point data and contours for Bouger anomaly in a portion of west-central Colorado. Includes the original spreadsheet data, a point shapefile showing gravity station locations and Bouger gravity, and a line shapefile showing 1 milligal contours. Projection: UTM Zone 13 NAD27.

This dataset contains documentation on the 146 global regions used to organize responses to the ArchaeGLOBE land use questionnaire between May 18 and July 31, 2018. The regions were formed from modern administrative regions (Natural Earth 1:50m Admin1 - states and provinces, https://www.naturalearthdata.com/downloads/50m-cultural-vectors/50m-admin-1-states-provinces/). The boundaries of the polygons represent rough geographic areas that serve as analytical units useful in two respects - for the history of land use over the past 10,000 years (a moving target) and for the history of archaeological research. Some consideration was also given to creating regions that were relatively equal in size. The regionalization process went through several rounds of feedback and redrawing before arriving at the 146 regions used in the survey. No bounded regional system could ever truly reflect the complex spatial distribution of archaeological knowledge on past human land use, but operating at a regional scale was necessary to facilitate timely collaboration while achieving global coverage. Map in Google Earth Format: ArchaeGLOBE_Regions_kml.kmz Map in ArcGIS Shapefile Format: ArchaeGLOBE_Regions.zip (multiple files in zip file) The shapefile format is a digital vector file that stores geographic location and associated attribute information. It is actually a collection of several different file types: .shp — shape format: the feature geometry .shx — shape index format: a positional index of the feature geometry .dbf — attribute format: columnar attributes for each shape .prj — projection format: the coordinate system and projection information .sbn and .sbx — a spatial index of the features .shp.xml — geospatial metadata in XML format .cpg — specifies the code page for identifying character encoding Attributes: FID - a unique identifier for every object in a shapefile table (0-145) Shape - the type of object (polygon) World_ID - coded value assigned to each feature according to its division into one of seventeen ‘World Regions’ based on the geographic regions used by the Statistics Division of the United Nations (https://unstats.un.org/unsd/methodology/m49/), with small changes to better reflect archaeological scholarly communities. These large regions provide organizational structure, but are not analytical units for the study. World_RG - text description of each ‘World Region’ Archaeo_ID - unique identifier (1-146) corresponding to the region code used in the ArchaeoGLOBE land use questionnaire and all ArchaeoGLOBE datasets Archaeo_RG - text description of each region Total_Area - the total area, in square kilometers, of each region Land-Area - the total area minus the area of all lakes and reservoirs found within each region (source: https://www.naturalearthdata.com/downloads/10m-physical-vectors/10m-lakes/) PDF of Region Attribute Table: ArchaeoGLOBE Regions Attributes.pdf Excel file of Region Attribute Table: ArchaeoGLOBE Regions Attributes.xls Printed Maps in PDF Format: ArchaeoGLOBE Regions.pdf Documentation of the ArchaeoGLOBE Regional Map: ArchaeoGLOBE Regions README.doc

This dataset contains a shapefile and an excel document. The shapefile data includes the spatial data of ChengYu Urban Agglomeration and its attributes such as population, GDP, transportation, education, and public health. The excel document contains the traffic cost between cities for different modes of travel, such as expressway, high-speed railway, and general speed railway.

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. In order to hold a water right in the western United States, an entity, (e.g., an individual, corporation, municipality, sovereign government, or non-profit) must register a physical document with the state's water regulatory agency. State water agencies each maintain their own database containing all registered water right documents within the state, along with relevant metadata such as the point of diversion and place of use of the water. All western U.S. states have digitized their individual water rights databases, along with the geospatial data describing the spatial units where water rights are managed. Each state maintains and provides their own water rights data in accordance with individual state regulations and standards. We collected water rights databases from 11 western United States states either by downloading them from publicly accessible web portals, or by contacting state water management representatives; detailed descriptions of where and when the data was collected is provided in the README.txt, as well as Lisk et al.(in review). This collection of data are those raw water rights. Each state formats their data differently, meaning that file types, field availability, and names vary from state to state. Note, the data provided here reflects the state of the water rights databases at the time we collected the data; updates have likely occurred in many states. Some pieces of information are common among all states. These are: priority date, volume or flow of water allowed by the right, stated water use of the right, and some means of identifying the geography and source of the water pertaining to the right - typically the coordinates of the Point of Diversion (PoD) of a waterbody or well. Arizona regulates water in a different way than the other 10 states. Outside of some relatively small critical agricultural areas called Active Management Areas (AMAs), Arizona does not maintain any water rights. However, the state does require registration of surface and groundwater pumping devices, which includes disclosing the mechanical specifics of the devices. We used these records as a proxy for water rights. Each state, and their respective water right authorities, have made their water right records available for non-commercial reference uses. In addition, the states make no guarantees as to the completeness, accuracy, or timeliness of their respective databases, let alone the modifications which we, the authors of this paper, have made to the collected records. None of the states should be held liable for using this data outside of its intended use. In addition, the following states have requested specifically worded disclaimers to be included with their data. Colorado: "The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk." Montana: "The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time." Oregon: "This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information." The available data is provided as a series of compressed files, which each containing the full data collected from each state. Some of the files have been renamed, to more easily know which state the data belongs to. The file renaming was also required as some files from different states had the same name. In other cases, the data for a state has been placed in a folder indicating which state it belongs to - as the state organized its data by selected subregions. Below is a brief description of the format of the collected data from each state. ArizonaRights_StatementOfClaimants: A folder containing a database of interconnected CSV files. The soc_erd.pdf file contains a visual flowchart of how the various files are connected, beginning with SOC_MAIN.csv in the center of the page. ArizonaRights_SurfaceWaterRightsData: A folder containing a database of a single Shapefile and 10 associated CSVs. SurfaceWater.pdf contains a visual flowchart of how the various files are connected, beginning with ADWR_SW_APPL_REGRY.csv. ArizonaRights_Well55Registry: A folder containing a database of a single Shapefile and 59 associated CSVs. Wells55.pdf contains a visual flowchart of how the various files are connected, beginning with WellRegistry.shp. CaliforniaRights_eWRIMS_directDatabase: A folder containing a collection of four "series" Microsoft Excel files, as either XLS or XLSX. The four "series": byCounty, byEntity (what type of legal entity holds the right), byUse (stated water use), and byWatershed, are various methods by which the California water rights are organized within the state's database. However, it was observed that by only collecting a single series, not all water rights were being provided. So, essentially, the majority of records within each "series" are copies of each other, with each "series" containing some unique records. ColoradoRights_NetAmounts: A folder containing 78 CSV files, with one file per Colorado Water District. IdahoRights_PointOfDiversion: A Shapefile containing the Points of Diversion for the entire state of Idaho. IdahoRights_PlaceOfUse: A Shapefile containing the Place of Use polygons for the entire state of Idaho. MontanaRights_WaterRights: A Geodatabase file containing the Points of Diversion and Places of Use for the entire state of Montana. The name of the Points of Diversion Feature Layer within the Geodatabase is "WRDIV", and the name of the Places of Use Feature Layer is "WRPOU". NevadaRights_POD_Sites: A Shapefile containing the Points of Diversion for the entire state of Nevada. NewMexicoRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of New Mexico. OregonRights_state_shp: A folder containing 36 Shapefiles and are split between "pod" (Point of Diversion) and "pou" (Place of Use) for each water management basin within Oregon. In other words, each basin has one "pod" file and one "pou" file. The "pod" files are point shapes, and the "pou" files are polygons. UtahRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of Utah. WashingtonRights_WaterDiversions_ECY_NHD: A Geodatabase file containing both the Points of Diversion for the entire state of Washington. The name of the Feature Layer within the Geodatabase is "WaterDiversions_ECY_NHD". WyomingRights: A folder containing four subdirectories, one for each Wyoming Water Division. Each Division directory includes a varying number of subdirectories for each Wyoming Water District. Each District folder contains two copies of the Point of Diversion records for that area, with one copying being in CSV and one copy in Microsoft Excel XLS format.

Abstract The dataset was derived by the Bioregional Assessment Programme from multiple datasets. The source dataset is identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement. The dataset consists of an excel spreadsheet and shapefile representing the locations of simulation nodes used in the AWRA-R model. Some of the nodes correspond to gauging station locations or dam …Show full descriptionAbstract The dataset was derived by the Bioregional Assessment Programme from multiple datasets. The source dataset is identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement. The dataset consists of an excel spreadsheet and shapefile representing the locations of simulation nodes used in the AWRA-R model. Some of the nodes correspond to gauging station locations or dam locations whereas other locations represent river confluences or catchment outlets which have no gauging. These are marked as "Dummy". Purpose Locations are used as pour points in oder to define reach areas for river system modelling. Dataset History Subset of data for the Hunter that was extracted from the Bureau of Meteorology's hydstra system and includes all gauges where data has been received from the lead water agency of each jurisdiction. Simulation nodes were added in locations in which the model will provide simulated streamflow. There are 3 files that have been extracted from the Hydstra database to aid in identifying sites in each bioregion and the type of data collected from each on. These data were used to determine the simulation node locations where model outputs were generated. The 3 files contained within the source dataset used for this determination are: Site - lists all sites available in Hydstra from data providers. The data provider is listed in the #Station as _xxx. For example, sites in NSW are _77, QLD are _66. Some sites do not have locational information and will not be able to be plotted. Period - the period table lists all the variables that are recorded at each site and the period of record. Variable - the variable table shows variable codes and names which can be linked to the period table. Relevant location information and other data were extracted to construct the spreadsheet and shapefile within this dataset. Dataset Citation Bioregional Assessment Programme (XXXX) HUN AWRA-R simulation nodes v01. Bioregional Assessment Derived Dataset. Viewed 13 March 2019, http://data.bioregionalassessments.gov.au/dataset/fda20928-d486-49d2-b362-e860c1918b06. Dataset Ancestors Derived From National Surface Water sites Hydstra

Abstract The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement. Contains line shapefiles and an excel spreadsheet and csv text file lookup table. The line shapefile derived from the Geofabric Surface Water Network streams (source data) and spatially represents the reaches described in the accompanying lookup table so that surface water modelling based Hydrological Response Variables (HRVs) can be applied spatially along stream lengths. Differs from previous versions in that some reaches previous designated as Ph (potentially impacted but not quantified) have now been assigned to a surface water modelling node. They include reach sections with no modelled change, no inferred change etc and thus extend outside the SW ZoPHC. All reaches described in interpolations spreadsheet are intact in that they extent outside the ZoPHC and event the PAE. Also included are the "rch_200" and "rch_300 reaches". These are reaches identified as additional potentially impacted reaches over and above those described by the interpolations spreadsheet. Also included is the revised reach to SW node lookup table for the HRVs. ## Dataset History Line segments from the Geofabric Network Streams source dataset were grouped into reach sections based on descriptions in the accompanying interpolations lookup table (supplied by Surface Water Modelling team) using the surface water node locations and described river junctions and other defined locations as spatial reference. Reaches were given a unique ID and dissolved into a multipart lines. In addition to the reaches described in the interpolations spreadsheet, additional reaches were identified (using the riverine perenniality classified stream network) as subject to potential hydrological change. These were non-ephemeral streams (LC_id = 22, 23, 25) rising out of or intersecting the groundwater zone of potential hydrological change (rch_200) and ephemeral reaches (LC_id = 24) rising out of or intersecting baseline mine pits (rch_300). ## Dataset Citation Bioregional Assessment Programme (2017) HUN SW Modelling Reaches and HRV lookup 20171121 v05. Bioregional Assessment Derived Dataset. Viewed 13 March 2019, http://data.bioregionalassessments.gov.au/dataset/8c330d59-2ecc-4c35-8f9e-68b91a4ae98a. ## Dataset Ancestors * Derived From HUN SW Model nodes 20170110 * Derived From HUN AWRA-L simulation nodes_v01 * Derived From National Surface Water sites Hydstra * Derived From Geofabric Surface Network - V2.1 * Derived From HUN AWRA-L simulation nodes v02 * Derived From HUN River Perenniality v01 * Derived From Geofabric Surface Network - V2.1.1

This data is associated with the Nevada Play Fairway project and includes excel files containing raw 2-meter temperature data and corrections. GIS shapefiles and layer files contain ing location and attribute information for the data are included. Well data includes both deep and shallow TG holes, GIS shapefiles and layer files. ArcGIS shapefile with location and attribute information

Contains Archive readme file (text file), country code ID key (excel file), and country code ID shapefile. Also contains production code for base grids and for additional spatial datasets.

Abstract The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement. Contains a line shapefile and an excel spreadsheet lookup table. The line shapefile derived from the Geofabric Surface Water Network streams (source data) and spatially represents the …Show full descriptionAbstract The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement. Contains a line shapefile and an excel spreadsheet lookup table. The line shapefile derived from the Geofabric Surface Water Network streams (source data) and spatially represents the reaches described in the accompanying lookup table so that surface water modelling based Hydrological Response Variables (HRVs) can be applied spatially along stream lengths. The interpolation is also applied to the Geofabric Cartographic Streams for mapping purposes. Dataset History Line segments from the Geofabric Network Streams and Cartogrpahic Streams source dataset were grouped into reach sections based on descriptions in the accompanying lookup table (supplied by Surface Water Modelling team) using the surface water node locations and described river junctions and other defined locations as spatial reference. Reaches were given a unique ID and dissolved into a multpart lines. There is also a Network version which further breaks the reaches into their Riverine Landscape classes. Dataset Citation Bioregional Assessment Programme (2017) HUN SW Modelling Reaches and HRV lookup 20170221 v02. Bioregional Assessment Derived Dataset. Viewed 13 March 2019, http://data.bioregionalassessments.gov.au/dataset/af0272b4-3a44-44ad-adba-5345a2b15f41. Dataset Ancestors Derived From HUN SW Model nodes 20170110 Derived From HUN AWRA-L simulation nodes_v01 Derived From National Surface Water sites Hydstra Derived From Geofabric Surface Network - V2.1 Derived From HUN AWRA-L simulation nodes v02 Derived From HUN River Perenniality v01 Derived From Geofabric Surface Network - V2.1.1

This project contains the Stata code as well as additional information used for the following paper:Randell, H & C Gray (Forthcoming). Climate Change and Educational Attainment in the Global Tropics. Proceedings of the National Academy of Sciences.The data are publicly available and can be accessed freely. The census data were obtained from IPUMS-International (https://international.ipums.org/international/) and the climate data were obtained from the CRU-Time Series Version 4.00 (http://data.ceda.ac.uk//badc/cru/data/cru_ts/cru_ts_4.00/).We include three do-files in this project:"Climate_-1_to_5.do" -- this file was used to convert the climate data into z-scores of climatic conditions experienced during ages -1 to 5 years among children in the sample. "ClimEducation_PNAS_FINAL.do" -- this file was used to process the census data downloaded from IPUMS-International, link it to the climate data, and perform all of the analyses in the study."Climate_6-10_and_11-current.do" -- this file was used to convert the climate data into z-scores of climatic conditions experienced during ages 6-10 and 11-current age among children in the sample.In addition, we include a shapefile (as well as related GIS files) for the final sample of analysis countries. The attribute "birthplace" is used to link the climate data to the census data. We include Python scripts for extracting monthly climate data for each 10-year temperature and precipitation file downloaded from CRU. "py0_60" extracts data for years one through five, and "py61_120" extracts data for years six through ten.Lastly, we include an excel file with inclusion/exclusion criteria for the countries and censuses available from IPUMS.

The Ontario government, generates and maintains thousands of datasets. Since 2012, we have shared data with Ontarians via a data catalogue. Open data is data that is shared with the public. Click here to learn more about open data and why Ontario releases it. Ontario’s Open Data Directive states that all data must be open, unless there is good reason for it to remain confidential. Ontario’s Chief Digital and Data Officer also has the authority to make certain datasets available publicly. Datasets listed in the catalogue that are not open will have one of the following labels: If you want to use data you find in the catalogue, that data must have a licence – a set of rules that describes how you can use it. A licence: Most of the data available in the catalogue is released under Ontario’s Open Government Licence. However, each dataset may be shared with the public under other kinds of licences or no licence at all. If a dataset doesn’t have a licence, you don’t have the right to use the data. If you have questions about how you can use a specific dataset, please contact us. The Ontario Data Catalogue endeavors to publish open data in a machine readable format. For machine readable datasets, you can simply retrieve the file you need using the file URL. The Ontario Data Catalogue is built on CKAN, which means the catalogue has the following features you can use when building applications. APIs (Application programming interfaces) let software applications communicate directly with each other. If you are using the catalogue in a software application, you might want to extract data from the catalogue through the catalogue API. Note: All Datastore API requests to the Ontario Data Catalogue must be made server-side. The catalogue's collection of dataset metadata (and dataset files) is searchable through the CKAN API. The Ontario Data Catalogue has more than just CKAN's documented search fields. You can also search these custom fields. You can also use the CKAN API to retrieve metadata about a particular dataset and check for updated files. Read the complete documentation for CKAN's API. Some of the open data in the Ontario Data Catalogue is available through the Datastore API. You can also search and access the machine-readable open data that is available in the catalogue. How to use the API feature: Read the complete documentation for CKAN's Datastore API. The Ontario Data Catalogue contains a record for each dataset that the Government of Ontario possesses. Some of these datasets will be available to you as open data. Others will not be available to you. This is because the Government of Ontario is unable to share data that would break the law or put someone's safety at risk. You can search for a dataset with a word that might describe a dataset or topic. Use words like “taxes” or “hospital locations” to discover what datasets the catalogue contains. You can search for a dataset from 3 spots on the catalogue: the homepage, the dataset search page, or the menu bar available across the catalogue. On the dataset search page, you can also filter your search results. You can select filters on the left hand side of the page to limit your search for datasets with your favourite file format, datasets that are updated weekly, datasets released by a particular organization, or datasets that are released under a specific licence. Go to the dataset search page to see the filters that are available to make your search easier. You can also do a quick search by selecting one of the catalogue’s categories on the homepage. These categories can help you see the types of data we have on key topic areas. When you find the dataset you are looking for, click on it to go to the dataset record. Each dataset record will tell you whether the data is available, and, if so, tell you about the data available. An open dataset might contain several data files. These files might represent different periods of time, different sub-sets of the dataset, different regions, language translations, or other breakdowns. You can select a file and either download it or preview it. Make sure to read the licence agreement to make sure you have permission to use it the way you want. Read more about previewing data. A non-open dataset may be not available for many reasons. Read more about non-open data. Read more about restricted data. Data that is non-open may still be subject to freedom of information requests. The catalogue has tools that enable all users to visualize the data in the catalogue without leaving the catalogue – no additional software needed. Have a look at our walk-through of how to make a chart in the catalogue. Get automatic notifications when datasets are updated. You can choose to get notifications for individual datasets, an organization’s datasets or the full catalogue. You don’t have to provide and personal information – just subscribe to our feeds using any feed reader you like using the corresponding notification web addresses. Copy those addresses and paste them into your reader. Your feed reader will let you know when the catalogue has been updated. The catalogue provides open data in several file formats (e.g., spreadsheets, geospatial data, etc). Learn about each format and how you can access and use the data each file contains. A file that has a list of items and values separated by commas without formatting (e.g. colours, italics, etc.) or extra visual features. This format provides just the data that you would display in a table. XLSX (Excel) files may be converted to CSV so they can be opened in a text editor. How to access the data: Open with any spreadsheet software application (e.g., Open Office Calc, Microsoft Excel) or text editor. Note: This format is considered machine-readable, it can be easily processed and used by a computer. Files that have visual formatting (e.g. bolded headers and colour-coded rows) can be hard for machines to understand, these elements make a file more human-readable and less machine-readable. A file that provides information without formatted text or extra visual features that may not follow a pattern of separated values like a CSV. How to access the data: Open with any word processor or text editor available on your device (e.g., Microsoft Word, Notepad). A spreadsheet file that may also include charts, graphs, and formatting. How to access the data: Open with a spreadsheet software application that supports this format (e.g., Open Office Calc, Microsoft Excel). Data can be converted to a CSV for a non-proprietary format of the same data without formatted text or extra visual features. A shapefile provides geographic information that can be used to create a map or perform geospatial analysis based on location, points/lines and other data about the shape and features of the area. It includes required files (.shp, .shx, .dbt) and might include corresponding files (e.g., .prj). How to access the data: Open with a geographic information system (GIS) software program (e.g., QGIS). A package of files and folders. The package can contain any number of different file types. How to access the data: Open with an unzipping software application (e.g., WinZIP, 7Zip). Note: If a ZIP file contains .shp, .shx, and .dbt file types, it is an ArcGIS ZIP: a package of shapefiles which provide information to create maps or perform geospatial analysis that can be opened with ArcGIS (a geographic information system software program). A file that provides information related to a geographic area (e.g., phone number, address, average rainfall, number of owl sightings in 2011 etc.) and its geospatial location (i.e., points/lines). How to access the data: Open using a GIS software application to create a map or do geospatial analysis. It can also be opened with a text editor to view raw information. Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. A text-based format for sharing data in a machine-readable way that can store data with more unconventional structures such as complex lists. How to access the data: Open with any text editor (e.g., Notepad) or access through a browser. Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. A text-based format to store and organize data in a machine-readable way that can store data with more unconventional structures (not just data organized in tables). How to access the data: Open with any text editor (e.g., Notepad). Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. A file that provides information related to an area (e.g., phone number, address, average rainfall, number of owl sightings in 2011 etc.) and its geospatial location (i.e., points/lines). How to access the data: Open with a geospatial software application that supports the KML format (e.g., Google Earth). Note: This format is machine-readable, and it can be easily processed and used by a computer. Human-readable data (including visual formatting) is easy for users to read and understand. This format contains files with data from tables used for statistical analysis and data visualization of Statistics Canada census data. How to access the data: Open with the Beyond 20/20 application. A database which links and combines data from different files or applications (including HTML, XML, Excel, etc.). The database file can be converted to a CSV/TXT to make the data machine-readable, but human-readable formatting will be lost. How to access the data: Open with Microsoft Office Access (a database management system used to develop application software). A file that keeps the original layout and

Modeled ground magnetic data was extracted from the Pan American Center for Earth and Environmental Studies database at http://irpsrvgis08.utep.edu/viewers/Flex/GravityMagnetic/GravityMagnetic_CyberShare/ on 2/29/2012. The downloaded text file was then imported into an Excel spreadsheet. This spreadsheet data was converted into an ESRI point shapefile in UTM Zone 13 NAD27 projection, showing location and magnetic field strength in nano-Teslas. This point shapefile was then interpolated to an ESRI grid using an inverse-distance weighting method, using ESRI Spatial Analyst. The grid was used to create a contour map of magnetic field strength.

The GIS Department has now created an Open Data Site for the free distribution of GIS Data. This site allows you to search for layers by key words or by themes. You can download the data in Excel spreadsheet format, or via ArcGIS Shapefile format. You can also filter the selection prior to downloading the data. Additionally, we have links to our public facing Mapping websites and story boards.