Duplicate the Projection.prj file and rename the duplicate to the same name as the ASCII grid, e.g. MAT.asc and MAT.prj. When MAT.asc is imported to ESRI ArcGIS or QGIS, the GIS systems will automatically pick-up the correct grid projection.

This dataset is comprised of the .prj and .cvf files used to build the database for the Virus Particle Exposure in Residences (ViPER) Webtool, a single zone indoor air quality and ventilation analysis tool developed by the National Institute of Standards and Technology (NIST).

The outlines of the craters as a shapefile (PRJ file).

File set contains HEC-RAS associated files for Taiacupeba Sediment Model, including main project file (.prj), geometric data (.g0*), steady flow data (.f0*), quasi-unsteady flow data (.q0*), sediment boundary conditions (.s0*) and simulation plans (.p0*). Computational results are not available, one should download files and run them locally.

This dataset provides shapefile outlines of the 7,150 lakes that had temperature modeled as part of this study. The format is a shapefile for all lakes combined (.shp, .shx, .dbf, and .prj files). A csv file of lake metadata is also included. This dataset is part of a larger data release of lake temperature model inputs and outputs for 7,150 lakes in the U.S. states of Minnesota and Wisconsin (http://dx.doi.org/10.5066/P9CA6XP8).

This dataset provides shapefile of outlines of the 68 lakes where temperature was modeled as part of this study. The format is a shapefile for all lakes combined (.shp, .shx, .dbf, and .prj files). This dataset is part of a larger data release of lake temperature model inputs and outputs for 68 lakes in the U.S. states of Minnesota and Wisconsin (http://dx.doi.org/10.5066/P9AQPIVD).

Context

This dataset contains shapefiles outlining 558 neighborhoods in 50 major cities in New York state, notably including Albany, Buffalo, Ithaca, New York City, Rochester, and Syracuse. This adds context to your datasets by identifying the neighborhood of any locations you have, as coordinates on their own don't carry a lot of information.

Content

What's inside is more than just rows and columns. Make it easy for others to get started by describing how you acquired the data and what time period it represents, too. What fields does it include? What's the time period of the data and how was it collected?

Four files are included containing data about the shapes: an SHX file, a DBF file, an SHP file, and a PRJ file. Including all of them in your input data are necessary, as they all contain pieces of the data; one file alone will not have everything that you need.

Seeing how none of these files are plaintext, it can be a little difficult to get set up with them. I highly recommend using mapshaper.org to get started- this site will show you the boundaries drawn on a plane, as well as allow you to export the files in a number of different formats (e.g. GeoJSON, CSV) if you are unable to use them in the format they are provided in. Personally, I have found it easier to work with the shapefile format though.

To get started with the shapefile in R, you can use the the rgdal and rgeos packages. To see an example of these being used, be sure to check out my kernel, "Incorporating neighborhoods into your model".

Acknowledgements

These files were provided by Zillow and are available under a Creative Commons license.

Inspiration

I'll be using these in the NYC Taxi Trip Duration competition to add context to the pickup and dropoff locations of the taxi rides and hopefully greatly improve my predictions.

This submission contains an update to the previous Exploration Gap Assessment funded in 2012, which identify high potential hydrothermal areas where critical data are needed (gap analysis on exploration data).

The uploaded data are contained in two data files for each data category: A shape (SHP) file containing the grid, and a data file (CSV) containing the individual layers that intersected with the grid. This CSV can be joined with the map to retrieve a list of datasets that are available at any given site. A grid of the contiguous U.S. was created with 88,000 10-km by 10-km grid cells, and each cell was populated with the status of data availability corresponding to five data types:

1. well data
2. geologic maps
3. fault maps
4. geochemistry data
5. geophysical data Associated shapefile projection file.

GIS Grid Files For The Sampling (NCEI Accession 0208321 and NCEI Accession 0208322) - DRTO_Grid.dbf 2019-12-20 07:14 2.2M DRTO_Grid.prj 2019-12-20 07:14 424 DRTO_Grid.sbn 2019-12-20 07:14 291K DRTO_Grid.sbx 2019-12-20 07:14 17K DRTO_Grid.shp 2019-12-20 07:14 4.0M DRTO_Grid.shp.xml 2019-12-20 07:14 21K DRTO_Grid.shx 2019-12-20 07:14 243K FlaKeys_Grid.dbf 2019-12-20 07:14 16M FlaKeys_Grid.prj 2019-12-20 07:14 424 FlaKeys_Grid.sbn 2019-12-20 07:14 666K FlaKeys_Grid.sbx 2019-12-20 07:14 10K FlaKeys_Grid.shp 2019-12-20 07:14 8.8M FlaKeys_Grid.shp.xml 2019-12-20 07:14 9.1K FlaKeys_Grid.shx 2019-12-20 07:14 528K SEFCRI_Grid_100m.dbf 2019-12-20 07:14 2.1M SEFCRI_Grid_100m.prj 2019-12-20 07:14 424 SEFCRI_Grid_100m.sbn 2019-12-20 07:14 224K SEFCRI_Grid_100m.sbx 2019-12-20 07:14 5.5K SEFCRI_Grid_100m.shp 2019-12-20 07:14 3.1M SEFCRI_Grid_100m.shp.xml 2019-12-20 07:14 8.4K SEFCRI_Grid_100m.shx 2019-12-20 07:14 188K

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Description: This zipfile contains three shapefiles of linear geometries showing channel networks across the SAFE landscape.

RIVERS_UTM.shp: From Igor Lysenko's SAFE pack, this is a river network with two areas, covering Maliau and the area around the SAFE experimental region. The network density is much higher in Maliau than SAFE and the channel network around SAFE is not complete. This is projected in UTM50N WGS84. LFEriver_SL.shp: This is provided (by Sarah Luke?) through Clare Wilkinson's GIS files and adds a critical missing stream for the Logged Forest Edge (LFE) catchment. This is projected in UTM50N WGS84. all_rivers.shp: This is provided through Clare Wilkinson's GIS files and provides streams for a single region covering Danum and the SAFE experimental region but not sampled watersheds in Oil Palm plantations to the south of SAFE. The original file is missing projection information (no .prj file) but other files in the same dataset are projected in RSO Timbalai 1948 and using this projection fits with the context of other data. The version uploaded onto Zenodo has been reprojected into UTM50N WGS84.Although the files are not consistent, they do contain channels and channel data that are referenced in some studies. The provenance of these files are unknown, although the following suggests that they may be traced using GPS or from imagery:

Incomplete coverage within the regions they cover. Treatment of larger rivers, changing from a single line feature showing the stream centreline (?) to double lines showing the river banks. Variation in network density: the western edge of all_rivers.shp shows a vertical band about 4 km wide of higher stream density than the rest of the region; RIVERS_UTM.shp shows marked differences in stream density between SAFE and Maliau.

Project: This dataset was collected as part of the following SAFE research project: SAFE CORE DATA XML metadata: GEMINI compliant metadata for this dataset is available here Files: This dataset consists of 2 files: SAFE_Alternative_Stream_network_metadata.xlsx, Preexisting_SAFE_river_files.zip SAFE_Alternative_Stream_network_metadata.xlsx This file only contains metadata for the files below Preexisting_SAFE_river_files.zip Description: Contains three shapefiles of channel networks. This file contains 3 data tables:

Feature properties (described in worksheet LFEriver_SL) Description: Field descriptions for shapefile properties Number of fields: 1 Number of data rows: Unavailable (table metadata description only). Fields:

Id: Identity of river (Field type: id)

Feature properties (described in worksheet RIVERS_UTM) Description: Field descriptions for shapefile properties Number of fields: 1 Number of data rows: Unavailable (table metadata description only). Fields:

NAME: Local name of segment (Field type: comments)

Feature properties (described in worksheet all_river_UTM50N_WGS84) Description: Field descriptions for shapefile properties Number of fields: 10 Number of data rows: Unavailable (table metadata description only). Fields:

FNODE_: Unknown (Field type: numeric) TNODE_: Unknown (Field type: numeric) LPOLY_: Unknown (Field type: numeric) RPOLY_: Unknown (Field type: numeric) LENGTH_MET: Length of channel segment in metres (Field type: numeric) RIV_YSC_: Unknown (Field type: numeric) RIV_YSC_ID: Unknown (Field type: numeric) CODE: Unknown (Field type: numeric) NAME: Local name of segment (Field type: comments) AREA: Local area of segment (Field type: comments)

Date range: 2010-10-01 to 2019-10-01 Latitudinal extent: 4.0223 to 5.9761 Longitudinal extent: 116.0242 to 117.9758

This directory contains the following maps in GeoTIFF format: open-water frequency, time-series of reflectance for each band (Red and NIR), and frequency of SSSC classes.

Fassoni-Andrade, A. C., & Paiva, R. C. D. (2019). Mapping spatial-temporal sediment dynamics of river-floodplains in the Amazon. Remote Sensing of Environment, 221, 94-107.

https://www.sciencedirect.com/science/article/abs/pii/S0034425718305005

Corresponding autor: alice.fassoni@ufrgs.br

1) Data Description:

1.1) Spatial Representation Type: Raster Format: TIFF Columns and rows: 7661, 2405 Cell Size (X,Y): 0.002245, 0.002245 (~250m)

1.2) Extent (coordinate system): Top: -0.025 Left: -67.28 Right: -50.081055 Botton: -5.424225

1.3) Spatial Reference Properties (GCS_WGS_1984.prj file): Type: Geographic Geographic Coordinate Reference: WGS 1984 Open Geospatial Consortium (OGC) Well Known Text (WKT): GEOGCS["GCS_WGS_1984", DATUM["D_WGS_1984", SPHEROID["WGS_1984",6378137.0,298.257223563]], PRIMEM["Greenwich",0.0], UNIT["Degree",0.0174532925199433], AUTHORITY["EPSG",4326]]

2) Data description for individual files:

2.1) File: open_water_frequency.tif This map indicates for how long, during 15 years (2003-2017), each pixel in rivers and lakes of central Amazon basin remained as open-water at every four days. Number of Bands: 1 Values between 0 and 100. Pixel Type: floating point Pixel Depth: 32 bit No Data Value: 0

2.2) File: class_SSC_frequency.tif This map represents a 15-year frequency (2003-2017) at which each pixel in rivers and lakes of central Amazon basin remains in one of the surface suspended sediments concentration classes (SSSC): high, moderate, and low. The open-water frequency map must be considered to interpret the sediments temporal dynamics in the class frequency map. For example, a pixel in the floodplain lake with frequency of 10, 30, and 20% in SSSC classes low, medium and high respectively, remains 40% of the time as no open-water. Number of Bands: 3 band 1: low SSSC class; band 2: Moderate SSSC class; band 3: High SSSC class Composition of bands for best visualization: R(3)G(2)B(1) without contrast Values between 0 and 100. Pixel Type: double precision Pixel Depth: 64 bit No Data Value: 0

2.3) File: time_series_nir.tif This map represents the climatology time series of infrared (nir) reflectance in period of four-days in rivers and lakes of central Amazon basin between 2003 and 2017 (15 years). Number of Bands: 92 (each band represent a date that is identified in dates.txt file) Values between 0 and 10000. Pixel Type: floating point Pixel Depth: 32 bit No Data Value: 0

2.4) File: time_series_red.tif This map represents the climatology time series of red reflectance in period of four-days in rivers and lakes of central Amazon basin between 2003 and 2017 (15 years). Number of Bands: 92 (each band represent a date that is identified in dates.txt file) Values between 0 and 10000. Pixel Type: floating point Pixel Depth: 32 bit No Data Value: 0

Abstract

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

This dataset defines the boundaries of the 66 groundwater SDL resource units in the Murray-Darling Basin. These include 7 groundwater SDL resource units for deep groundwater that lie beneath the 59 groundwater SDL resource units. 2 of the groundwater SDL resource units have different boundaries in their surface expression and in deep groundwater and therefore are shown with both a Groundwater and Deep Groundwater extent.

In some areas, there are SDL resource units that overlap one another (eg: GS1). This occurs where SDLs have been set for discrete aquifers that overlie one another under the same area of land. These can be differentiated by the GWSDLName field.

There are areas of overlap between the groundwater and deep groundwater SDL resource units which need to be taken into account when viewing the data. These can be differentiated by the GWSDLType field

Purpose

The Basin Plan provides a coordinated approach to water use across the Basin's four States and the ACT. The Basin Plan is a plan for the integrated management of Basin water resources made under the Water Act 2007. It limits water use at environmentally sustainable levels by determining long-term average Sustainable Diversion Limits for both surface water and groundwater resources.

Date of Ceasing: To be ceased 01 Apr 2023

Dataset History

The following data has been used in the development of groundwater SDL resource unit boundaries:

Queensland: - Upper Condamine Basalts (as contained in the data files titled: basalts.dbf, basalts.prj, basalts.sbn, basalts.sbx, basalts.shp, basalts.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Texas beds (as contained in the data files titled: texas beds.dbf, texas beds.prj, texas beds.sbn, texas beds.sbx, texas beds.shp, texas beds.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Griman Creek Formation (as contained in the data files titled: Griman Ck Formation.dbf, Griman Ck Formation.prj, Griman Ck Formation.sbn, Griman Ck Formation.sbx, Griman Ck Formation.shp, Griman Ck Formation.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Great Artesian Basin geology (as contained in the data files titled: Geology.dbf, Geology.prj, Geology.sbn, Geology.sbx, Geology.shp, Geology.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Queensland Murray-Darling Groundwater Management Units (as contained in the data files titled: QLD_MurrayDarling_GMU_GCS_v7.dbf, QLD_MurrayDarling_GMU_GCS_v7.prj, QLD_MurrayDarling_GMU_GCS_v7.sbn, QLD_MurrayDarling_GMU_GCS_v7.sbx, QLD_MurrayDarling_GMU_GCS_v7.shp, QLD_MurrayDarling_GMU_GCS_v7.shx) provided by SKM on 16/12/2009. - Geology sheet sh5502 (as contained in the data files titled: sh5502.dbf, sh5502.prj, sh5502.sbn, sh5502.sbx, sh5502.shp, sh5502.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Geology sheet sh5501 (as contained in the data files titled: sh5501,dbf, sh5501.prj, sh5501.sbn, sh5501.sbx, sh5501.shp, sh5501.shx), provided by the Department of Environment and Resource Management on 18/12/2009. - Geology sheet sh5513 (as contained in the data files titled: sg5513.dbf, sg5513.prj, sg5513.sbn, sg5513.sbx, sg5513.shp, sg5513.shx) provided by the Department of Environment and Resource Management on 18/12/2009. - Geology sheet sh5609 (as contained in the data files titled: sg5609.dbf, sg5609.prj, sg5609.sbn, sg5609.sbx, sg5609.shp, sg5609.shx) provided by the Department of Environment and Resource Management, Queensland, on 18/12/2009. - Central Condamine Alluvium boundaries (as contained in the files:Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.dbf, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.prj, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.sbn, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.sbx, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.shp, Central_Condamine_Amendment_Plan_Boundary_updatedApril2010.shx) provided by the Department of Environment and Resource Management on 27/5/2011 - DERM Revised Queensland Groundwater SDL Areas (as contained in the files: DERM_Revised_QLD_GW_SDL_AREAS.dbf, DERM_Revised_QLD_GW_SDL_AREAS.prj, DERM_Revised_QLD_GW_SDL_AREAS.sbn, DERM_Revised_QLD_GW_SDL_AREAS.sbx, DERM_Revised_QLD_GW_SDL_AREAS.shp, DERM_Revised_QLD_GW_SDL_AREAS.shp.xml, DERM_Revised_QLD_GW_SDL_AREAS.shx ) provided by the Queensland Department of Environment & Resource Management on 26/9/2011

New South Wales: - Groundwater macro water sharing plan areas (as contained in the data file titled: DraftGWMacroPlanOctober2010.mdb) provided by NSW Office of Water on 14/12/2010. - Groundwater macro water sharing plan areas (as contained in the data file titled: GWMacroPlanFeb2012.gdb) provided by NSW Office of Water on 8/3/2012.

Victoria: - Goulburn-Murray water boundary (as contained in the data files titled: G-MW_Boundary.dbf, G-MW_Boundary.prj, G-MW_Boundary.sbn, G-MW_Boundary.sbx, G-MW_Boundary.shp, G-MW_Boundary.shx) provided by Goulburn-Murray Water on 21/12/2009. - Murray geological basin (as contained in the data files titled: Murray_GB_250K.dbf, Murray_GB_250K.prj, Murray_GB_250K.sbn, Murray_GB_250K.sbx, Murray_GB_250K.shp, Murray_GB_250K.shx) provided by Sinclair Knight Merz on 14/12/2009. - Southern Campaspe Plain (as contained in the data files titled: S_Camp_Plains.dbf, S_Camp_Plains.prj, S_Camp_Plains.sbn, S_Camp_Plains.sbx, S_Camp_Plains.shp, S_Camp_Plains.shx) provided by Department of Sustainability and Environment, Victoria, on 03/03/2010. - West Wimmera and Murrayville water sharing plan area (as contained in the data files titled: West_Wimmera_&_Murrayville_WSPA.dbf, West_Wimmera_&_Murrayville_WSPA.prj, West_Wimmera_&_Murrayville_WSPA.sbn, West_Wimmera_&_Murrayville_WSPA.sbx, West_Wimmera_&_Murrayville_WSPA.shp, West_Wimmera_&_Murrayville_WSPA.shx) provided by Department of Sustainability and Environment, Victoria, on 11/01/2010. - Victorian groundwater management unit (as contained in the data files titled: Vic_GMU_gcs_v02.dbf, Vic_GMU_gcs_v02.prj, Vic_GMU_gcs_v02.sbn, Vic_GMU_gcs_v02.sbx, Vic_GMU_gcs_v02.shp, Vic_GMU_gcs_v02.shx) provided by Sinclair Knight Merz on 30/11/2009. - SA/VIC Border zone agreement area (as contained in the data files titled: Border_Agreement.dbf, Border_Agreement.prj, Border_Agreement.sbn, Border_Agreement.sbx. Border_Agreement.shp, Border_Agreement.shx) provided by Sinclair Knight Merz on 30/11/2009. - AWRC Basins (as contained in the data files titled: AWRC_BASINS.dbf, AWRC_BASINS.prj, AWRC_BASINS.sbn, AWRC_BASINS.sbx, AWRC_BASINS.shp, AWRC_BASINS.shx) provided by MDBA on 19/01/2009.

• Basin water resources exclusions contained in the data files titled westwimmera.dbf, westwimmera.prj, westwimmera.sbn, westwimmera.sbx, westwimmera.shp, westwimmera.shp.xml, westwimmera.shx provided by the Department of Environment on 14/11/2013

South Australia: - South Australian groundwater management unit (as contained in the data files titled: SA_GMU_gcs_v03.dbf, SA_GMU_gcs_v03.prj, SA_GMU_gcs_v03.sbn, SA_GMU_gcs_v03.sbx, SA_GMU_gcs_v03.shp, SA_GMU_gcs_v03.shx) provided by Sincliar Knight Merz on 30/11/2009. - SA/VIC Border zone agreement area (as contained in the data files titled: Border_Agreement.dbf, Border_Agreement.prj, Border_Agreement.sbn, Border_Agreement.sbx. Border_Agreement.shp, Border_Agreement.shx) provided by Sinclair Knight Merz on 30/11/2009. - Murray-Darling Basin Rivers (as contained in the data files titled: MDB_MAIN_RIVERS.dbf, MDB_MAIN_RIVERS.prj, MDB_MAIN_RIVERS.sbn, MDB_MAIN_RIVERS.sbx, MDB_MAIN_RIVERS.shp, MDB_MAIN_RIVERS.shx) provided by the MDBA on 19/01/2009.

• Basin water resources exclusions as contained in the data files titled: Split_poly_MDB_PWRA_Area1_IW.dbf, Split_poly_MDB_PWRA_Area1_IW.prj, Split_poly_MDB_PWRA_Area1_IW..sbn, Split_poly_MDB_PWRA_Area1_IW.sbx, Split_poly_MDB_PWRA_Area1_IW.shp, Split_poly_MDB_PWRA_Area1_IW.shp.xml, Split_poly_MDB_PWRA_Area1_IW.shx, Split_poly_MDB_PWRA_Area2_IW.dbf, Split_poly_MDB_PWRA_Area2_IW.prj, Split_poly_MDB_PWRA_Area2_IW..sbn, Split_poly_MDB_PWRA_Area2_IW.sbx, Split_poly_MDB_PWRA_Area2_IW.shp, Split_poly_MDB_PWRA_Area2_IW.shp.xml, Split_poly_MDB_PWRA_Area2_IW.shx, Split_poly_MDB_PWRA_Area4_IW.dbf, Split_poly_MDB_PWRA_Area4_IW.prj, Split_poly_MDB_PWRA_Area4_IW..sbn, Split_poly_MDB_PWRA_Area4_IW.sbx, Split_poly_MDB_PWRA_Area4_IW.shp, Split_poly_MDB_PWRA_Area4_IW.shp.xml, Split_poly_MDB_PWRA_Area4_IW.shx, Split_poly_MDB_PWRA_Area5_IW.dbf, Split_poly_MDB_PWRA_Area5_IW.prj, Split_poly_MDB_PWRA_Area5_IW..sbn, Split_poly_MDB_PWRA_Area5_IW.sbx, Split_poly_MDB_PWRA_Area5_IW.shp, Split_poly_MDB_PWRA_Area5_IW.shp.xml, Split_poly_MDB_PWRA_Area5_IW.shx, Split_poly_MDB_PWRA_Area6_IW.dbf, Split_poly_MDB_PWRA_Area6_IW.prj, Split_poly_MDB_PWRA_Area6_IW..sbn, Split_poly_MDB_PWRA_Area6_IW.sbx, Split_poly_MDB_PWRA_Area6_IW.shp, Split_poly_MDB_PWRA_Area6_IW.shp.xml, Split_poly_MDB_PWRA_Area6_IW.shx, provided by the Department of Sustainability, Environment, Water, Population and Communities on 27/5/2013 and 28/05/2013.

ACT: - ACT GMU Boundaries (as contained in the data files titled: ACT_GMU_gcs_v01.dbf, ACT_GMU_gcs_v01.prj, ACT_GMU_gcs_v01sbn, ACT_GMU_gcs_v01.sbx, ACT_GMU_gcs_v01.shp, ACT_GMU_gcs_v01.shx) provided by Sinclair Knight Merz on 30/11/2009.

State Borders: - State Borders (as contained in the data files titled: AUS_STATE_BORDER.dbf, AUS_STATE_BORDER.prj, AUS_STATE_BORDER.sbn, AUS_STATE_BORDER.sbx, AUS_STATE_BORDER.shp, AUS_STATE_BORDER.shx) provided by the MDBA on 19/01/2009.

Deep groundwater SDL resource unit boundaries:

• Boundary for the Oaklands Basin (as contained in the files:

Includes DBF spreadsheet of data on individual trees as well as SHP/SHX/PRJ files for GIS representation.

Large-scale_prediction_archiveThis compressed archive includes multiple other files including data files (in .rdata format) GIS shapefiles (in folders with the associated .shp, .shx, .dbf, and .prj files for each map) and an R script that will run all analyses and plot all figures. Specific descriptions of each file are supplied in the README.TXT file.

This dataset provides shapefile outlines of the 881 lakes that had temperature modeled as part of this study. The format is a shapefile for all lakes combined (.shp, .shx, .dbf, and .prj files). A csv file of lake metadata is also included. This dataset is part of a larger data release of lake temperature model inputs and outputs for 881 lakes in the U.S. state of Minnesota (https://doi.org/10.5066/P9PPHJE2).

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

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

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

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

Key specifications:

Topologized ZIP polygons​

GeoJunxion ZIP+4 polygons follow USPS postal codes ​

ZIP+4 code polygons: ​

ZIP5 attributes ​

State codes. ​

Overlapping ZIP+4 ​

boundaries for multiple ZIP+4 addresses on one area​

Updated USPS source (January 2021) ​

Distinct ZIP5 codes: 34 731​

Distinct ZIP+4 codes: 35 146 957 ​

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

The four components for the shapefile data are: ​

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

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

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

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

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

​

This data set provides a grid of quads and projection information to be used for rover operations and the informal geographic naming convention for the regional geography of Oxia Planum. Both subject to update prior to the landed mission.Contents This data set contains 4 shapefiles and 1 zipped folder.OxiaPlanum_GeographicFeatures_2021_08_26. Point shapefile with the names of geographic features last updated at the date indicatedOxiaPlanum_GeographicRegions_2021_08_26. Polygon shapefile with the outlines of geographic regions fitted to the master quad grid and last updated at the date indicated.OxiaPlanum_QuadGrid_1km. Polygon shapefile of 1km quad that will be used for ExoMars rover missionOxiaPlanum_Origin_clong_335_45E_18_20N. The center point of the Oxia Planum as defined by the Rover Operations and Control center and origin point used for the Quad gridCRS_PRJ_Equirectangular_OxiaPlanum_Mars2000.zip. Zip folder containing the projection information use for all the data associated with this study. These are saved in the ESRI projection (.prj) and well know text formal (.wkt)Guide to individual filesFile name (example) Description OxiaPlanum_QuadGrid_1km.cpg Text display information OxiaPlanum_QuadGrid_1km.dbf Database file OxiaPlanum_QuadGrid_1km.prj Projection information OxiaPlanum_QuadGrid_1km.sbx Spatial index file OxiaPlanum_QuadGrid_1km.shp Shape file data