The establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making. BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions. Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself. For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise. Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer. This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery. See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt

Focus on Geodatabases in ArcGIS Pro introduces readers to the geodatabase, the comprehensive information model for representing and managing geographic information across the ArcGIS platform.Sharing best practices for creating and maintaining data integrity, chapter topics include the careful design of a geodatabase schema, building geodatabases that include data integrity rules, populating geodatabases with existing data, working with topologies, editing data using various techniques, building 3D views, and sharing data on the web. Each chapter includes important concepts with hands-on, step-by-step tutorials, sample projects and datasets, 'Your turn' segments with less instruction, study questions for classroom use, and an independent project. Instructor resources are available by request.AUDIENCEProfessional and scholarly.AUTHOR BIODavid W. Allen has been working in the GIS field for over 35 years, the last 30 with the City of Euless, Texas, and has seen many versions of ArcInfo and ArcGIS come along since he started with version 5. He spent 18 years as an adjunct professor at Tarrant County College in Fort Worth, Texas, and now serves as the State Director of Operations for a volunteer emergency response group developing databases and templates. Mr. Allen is the author of GIS Tutorial 2: Spatial Analysis Workbook (Esri Press, 2016).Pub Date: Print: 6/17/2019 Digital: 4/29/2019 Format: PaperbackISBN: Print: 9781589484450 Digital: 9781589484467 Trim: 7.5 x 9.25 in.Price: Print: $59.99 USD Digital: $59.99 USD Pages: 260

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 dataset contains buildings within Montgomery County. Building ruins, buildings under construction, and parking garages are also included. Overhead rooftops, or canopies, are shown with a separate feature code and features running under are not clipped out. Each feature is attributed with height in feet and roof type of either gable or flat. This data was captured for use in general mapping at a scale of 1:1200.Countywide data updated Spring 2023.For more information, contact: GIS Manager Information Technology & Innovation (ITI) Montgomery County Planning Department, MNCPPC T: 301-650-5620.

This geodatabase includes spatial datasets that represent the Texas Coastal Uplands and Mississippi Embayment aquifer system in the States of Alabama, Arkansas, Illinois, Kentucky, Louisiana, Mississippi, Missouri, Tennessee, and Texas. Included are: (1) polygon extents; datasets that represent the aquifer system extent, the entire extent subdivided into subareas or subunits, and any polygon extents of special interest (outcrop areas, no data available, areas underlying other aquifers, anomalies, for example), (2) raster datasets for the altitude of each aquifer subarea or subunit, (3) altitude, and/or if applicable, thickness contours used to generate the surface rasters, (4) georeferenced images of the figures that were digitized to create the altitude and thickness contours. The images and digitized contours are supplied for reference. The extent of the Texas Coastal Uplands and Mississippi Embayment aquifer system is derived from the linework in the aquifer system extent maps in U.S. Geological Survey Professional Paper 1416-B (USGS PP 1416-B), plates 11, 13, 15, 16, and 17, and from a digital version of the aquifer extents presented in the U.S. Geological Survey Hydrologic Atlas 730, Chapters E and F. The Texas Coastal Uplands and Mississippi Embayment aquifer system has 6 aquifer subunits, in order from the most surficial to the deepest: A1: Upper Claiborne aquifer, A2: Middle Claiborne aquifer, A3: Lower Claiborne- Upper Wilcox aquifer, A4: Middle Wilcox aquifer, A5: Lower Wilcox aquifer, A6: McNairy-Nacatoch aquifer. The altitude and thickness contours for each available subunit were digitized from georeferenced figures of altitude contours in USGS PP 1416-B, and the resultant top and bottom altitude values were interpolated into surface rasters within a GIS using tools that create hydrologically correct surfaces from contour data, derives the altitude from the thickness (depth from the land surface), and merges the subareas into a single surface. The primary tool was an enhanced version of "Topo to Raster" used in ArcGIS, ArcMap, Esri 2014. The raster surfaces were corrected for the areas where the altitude of an underlying layer of the aquifer exceeded altitude of an overlying layer.

Continuing the tradition of the best-selling Getting to Know series, Getting to Know ArcGIS Pro 2.6 teaches new and existing GIS users how to get started solving problems using ArcGIS Pro. Using ArcGIS Pro for these tasks allows you to understand complex data with the leading GIS software that many businesses and organizations use every day.Getting to Know ArcGIS Pro 2.6 introduces the basic tools and capabilities of ArcGIS Pro through practical project workflows that demonstrate best practices for productivity. Explore spatial relationships, building a geodatabase, 3D GIS, project presentation, and more. Learn how to navigate ArcGIS Pro and ArcGIS Online by visualizing, querying, creating, editing, analyzing, and presenting geospatial data in both 2D and 3D environments. Using figures to show each step, Getting to Know ArcGIS Pro 2.6 demystifies complicated process like developing a geoprocessing model, using Python to write a script tool, and the creation of space-time cubes. Cartographic techniques for both web and physical maps are included.Each chapter begins with a prompt using a real-world scenario in a different industry to help you explore how ArcGIS Pro can be applied for operational efficiency, analysis, and problem solving. A summary and glossary terms at the end of every chapter help reinforce the lessons and skills learned.Ideal for students, self-learners, and seasoned professionals looking to learn a new GIS product, Getting to Know ArcGIS Pro 2.6 is a broad textbook and desk reference designed to leave users feeling confident in using ArcGIS Pro on their own.AUDIENCEProfessional and scholarly. Higher education.AUTHOR BIOMichael Law is a cartographer and GIS professional with more than a decade of experience. He was a cartographer for Esri, where he developed cartography for books, edited and tested GIS workbooks, and was the editor of the Esri Map Book. He continues to work with GIS software, writing technical documentation, teaching training courses, and designing and optimizing user interfaces.Amy Collins is a writer and editor who has worked with GIS for over 16 years. She was a technical editor for Esri, where she honed her GIS skills and cultivated an interest in designing effective instructional materials. She continues to develop books on GIS education, among other projects.Pub Date: Print: 10/6/2020 Digital: 8/18/2020 ISBN: Print: 9781589486355 Digital: 9781589486362 Price: Print: $84.99 USD Digital: $84.99 USD Pages: 420 Trim: 7.5 x 9.25 in.Table of ContentsPrefaceChapter 1 Introducing GISExercise 1a: Explore ArcGIS OnlineChapter 2 A first look at ArcGIS Pro Exercise 2a: Learn some basics Exercise 2b: Go beyond the basics Exercise 2c: Experience 3D GISChapter 3 Exploring geospatial relationshipsExercise 3a: Extract part of a dataset Exercise 3b: Incorporate tabular data Exercise 3c: Calculate data statistics Exercise 3d: Connect spatial datasetsChapter 4 Creating and editing spatial data Exercise 4a: Build a geodatabase Exercise 4b: Create features Exercise 4c: Modify featuresChapter 5 Facilitating workflows Exercise 5a: Manage a repeatable workflow using tasks Exercise 5b: Create a geoprocessing model Exercise 5c: Run a Python command and script toolChapter 6 Collaborative mapping Exercise 6a: Prepare a database for data collection Exercise 6b: Prepare a map for data collection Exercise 6c: Collect data using ArcGIS CollectorChapter 7 Geoenabling your projectExercise 7a: Prepare project data Exercise 7b: Geocode location data Exercise 7c: Use geoprocessing tools to analyze vector dataChapter 8 Analyzing spatial and temporal patternsExercise 8a: Create a kernel density map Exercise 8b: Perform a hot spot analysis Exercise 8c: Explore the results in 3D Exercise 8d: Animate the dataChapter 9 Determining suitability Exercise 9a: Prepare project data Exercise 9b: Derive new surfaces Exercise 9c: Create a weighted suitability modelChapter 10 Presenting your project Exercise 10a: Apply detailed symbology Exercise 10b: Label features Exercise 10c: Create a page layout Exercise 10d: Share your projectAppendix Image and data source credits Data license agreement GlossaryGetting to Know ArcGIS Pro 2.6 | Official Trailer | 2020-08-10 | 00:57

Abstract

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

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

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

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

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

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

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

Dataset History

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

Data in this release

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

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

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

*Georeferenced Queensland geology map, gravity and magnetic images

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

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

Accessing the data

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

Metadata

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

Disclaimer

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

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

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

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

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

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

Dataset Citation

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

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. An ArcInfo(tm) (ESRI) GIS database was designed for WICA using the National Park GIS Database Design, Layout, and Procedures created by the BOR. This was created through Arc Macro Language (AML) scripts that helped automate the transfer process and ensure that all spatial and attribute data was consistent and stored properly. Actual transfer of information from the interpreted aerial photographs to a digital, geo-referenced format involved two techniques, scanning (for the vegetation classes) and on-screen digitizing (for the land-use classes). Both techniques required the use of 14 digital black-and-white orthophoto quarter quadrangles (DOQQ's) covering the study area. Transferred information was used to create vegetation polygon coverages and ancillary linear coverages in ArcInfo(tm) for each WICA DOQQ. Attribute information including vegetation map unit, location, and aerial photo number was subsequently entered for all polygons.

Note: please go to https://data.sfgov.org/d/ynuv-fyni to access the same data in additional open formats. These footprint extents are collapsed from an earlier 3D building model provided by Pictometry of 2010, and have been refined from a version of building masses publicly available on the open data portal for over two years. The building masses were manually split with reference to parcel lines, but using vertices from the building mass wherever possible. These split footprints correspond closely to individual structures even where there are common walls; the goal of the splitting process was to divide the building mass wherever there was likely to be a firewall.An arbitrary identifier was assigned based on a descending sort of building area for 177,023 footprints. The centroid of each footprint was used to join a property identifier from a draft of the San Francisco Enterprise GIS Program's cartographic base, which provides continuous coverage with distinct right-of-way areas as well as selected nearby parcels from adjacent counties. See accompanying document SF_BldgFoot_2017-05_description.pdf for more on methodology and motivation https://data.sfgov.org/d/ynuv-fyni/ about

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. An ArcInfo (copyright ESRI) GIS database was designed for THRO using the National Park GIS Database Design, Layout, and Procedures created by RSGIG. This was created through Arc Macro Language (AML) scripts that helped automate the transfer process and ensure that all spatial and attribute data was consistent and stored properly. Actual transfer of information from the interpreted aerial photographs to a digital, geo-referenced format involved two techniques, scanning (for the vegetation classes) and on-screen digitizing (for the land-use classes). Transferred information used to create vegetation polygon coverages and linear coverages in ArcInfo were based on quarter-quad borders. Attribute information including vegetation map unit, location, and aerial photo number was subsequently entered for all polygons. In addition, the spatial database has an FGDC-compliant metadata file.

This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address.

Contact: Lynn Flaaen-Hanna, Development Services Specialist

Contact E-mail



Link: Map that Lets You Explore and Export Address Data



Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.


Data Source Type: ESRI ArcGIS Enterprise Geodatabase

Preparation Method: N/A

Publish Frequency: Weekly

Publish Method: Automatic

Data Dictionary

Abstract

This dataset was derived by the Bioregional Assessment Programme. The parent datasets are identified in the Lineage statement in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

This dataset comprises of interpreted elevation surfaces and contours for the major Triassic and Upper Permian units of the Galilee Geological Basin.

Purpose

This dataset was created to provide formation extents for aquifers in the Galilee geological basin

Dataset History

A Quality Assurance (QA) and validation process was conducted on the original well and bore data to choose wells/bores that are within 25 kilometres of the BA Galilee Region extent.

The QA/Validation process is as follows:

1. Well data

   a. Obtained excel file "QPED_July_2013_galilee.xlsx" from GA

   b. Based on stratigraphic information in "BH_costrat" tab formation names were regularised and simplified based on current naming conventions.

   c. Simplified names added to QPED_July_2013_galileet.xlsx as "Steve_geo" and "Steve_group"

   d. Produced new file "GSQ_Geology.xlsx" contained decimal latitude and longitude, KB elevation, top of unit in metres from KB, top of unit in metres AHD, bottom of unit in metres from KB, bottom of unit in metres AHD, original geology, simplified geology, simplified Group geology.

    i.     KB obtained from "BH_wellhist"
   
    ii.    Where no KB information was available ie KB=0, sample the 1S DEM at the well's location to obtain height. KB=DEM+10. Marked well as having lower reliability.
   
    iii.    Calculated Top_m_AHD = KB - Top_m_KB
   
    iv.    Calculated Bottom_m_AHD = KB - Bottom_m_KB
   

   e. Brought GSQ_Geology.xlsx into ArcGIS

   f. Selected wells based on "Steve_geo" field for each model layer to produce a geodatabase for each layer.

    i.     GSQ_basement_wells
   
    ii.    GSQ_top_joe_joe_group
   
    iii.    GSQ_top_bandanna_merge
   
    iv.    GSQ_rewan_group
   
    v.     GSQ_clematis
   
    vi.    GSQ_moolyember
   

   g. Additional wells and reinterpreted tops added to appropriate geodatabase based on well completion reports

   h. Additional wells added to coverages to help model building process

    i.     Well_name listed as Fake
   
    ii.    Exception being GSQ_top_basement_fake which was created as a separate geodatabase
   

2. Bore data

   a. Obtained QLD_DNRM_GroundwaterDatabaseExtract_20131111 from GA

   b. Used files REGISTRATIONS.txt, ELEVATIONS.txt and AQUIFER.txt to build GW_stratigraphy.xlsx

    i.     Based on RN
   
    ii.    Latitude from GIS_LAT (REGISTRATIONS.txt)
   
    iii.    Longitude from GIS_LNG (REGISTRATIONS.txt)
   
    iv.    Elevation from (ELEVATIONS.txt)
   
    v.     FORM_DESC from (AQUIFER.txt)
   
    vi.    Top from (AQUIFER.txt)
   
    vii.    Bottom from (AQUIFER.txt)
   

   c. Brought GW_stratigraphy.xlsx into ArcGIS

   d. Created gw_bores_galilee_dem

    i.     Sampled 1S DEM to obtain ground level elevation column RASTERVALU
   
    ii.    Created column top_m_AHD by RASTERVALU - Top
   

   e. Selected bores based on "FORM_DESC" field for each model layer to produce a geodatabase for each layer.

    i.     Gw_basement
   
    ii.    GW_bores_joe_joe_group
   
    iii.    GW_bores_bandanna
   
    iv.    Gw_bores_rewan
   
    v.     Gw_bores_clematis
   
    vi.    Gw_bores_moolyember
   

3. Georectified seismic surfaces

   a. Extracted interpreted seismic surfaces for base Permian (interpreted as basement) and top Bandanna (in time) from the following seismic surveys

    i.     Y80A, W81A, Carmichael, Pendine, T81A, Quilpie, Ward and Powell Creek seismic survey downloaded https://qdexguest.deedi.qld.gov.au/portal/site/qdex/search?searchType=general 
   
    ii.    Brought TIF images into ArcGIS and georectified
   
    iii.    Digitised shape of contours and faults into geodatabase
   
        1.   Basement_contours and basement_faults
   
        2.   bandanna_contours_new_data and bandanna_faults
   
    iv.    Added field "contour" to geodatabase
   
    v.     Converted contours to depth in "contour" field based on well and bore data (top_m_AHD) and contour progression
   
    vi.    Use the shape and depth derived from OZ SEEBASE to help to add additional contours and faults to basement and bandanna datasets
   

4. Additional contour and fault surfaces were built derived from underlying surfaces and wells/bore data

   a. Joejoe_contours and joejoe)faults

   b. Rewan_contour_clip (used bandanna_faults as fault coverage)

   c. Clematis_contour and clematis_faults

   d. Moolyember_contour (used clematis_faults as fault coverage)

5. Surface geology

   a. Extracted surface geology from QUEENSLAND GEOLOGY_AUGUST_2012 using Galilee BA region boundary with 25 kilometre boundary to form geodatabase QLD_geology_galilee

   b. Selected relevant surface geology from QLD_geology_galilee based on field "Name" for each model layer and created new geodatabase layers

    i.     Basement_geology: Argentine Metamorphics,Running River Metamorphics,Charters Towers Metamorphics; Bimurra Volcanics, Foyle Volcanics, Mount Wyatt Formation, Saint Anns Formation, Silver Hills Volcanics, Stones Creek Volcanics; Bulliwallah Formation, Ducabrook Formation, Mount Rankin Formation, Natal Formation, Star of Hope Formation; Cape River Metamorphics; Einasleigh Metamorphics; Gem Park Granite; Macrossan Province Cambrian-Ordovician intrusives; Macrossan Province Ordovician-Silurian intrusives; Macrossan Province Ordovician intrusives; Mount Formartine, unnamed plutonic units; Pama Province Silurian-Devonian intrusives; Seventy Mile Range Group; and Kirk River beds, Les Jumelles beds.
   
    ii.    Joe_joe_geology: Joe Joe Group
   
    iii.    Galilee_permian_geology: Back Creek Group, Betts Creek Group, Blackwater Group
   
    iv.    Rewan_geology: Rewan Group
   
       1.    Later also made dunda_beds_geology to be included in Rewan model: Dunda beds
   
    v.     Clematis_geology: Clematis Group
   
       1.    Later also made warang_sandstone_geology to be included in Clematis model: Warang Sandstone
   
    vi.    Moolyember_surface_geology: Moolyember Formation
   

6. DEM for each model layer

   a. Using surface geology geodatabase extent extract grid from dem_s_1s to represent the top of the model layer at the surface

    i.     Basement_dem
   
    ii.    Joejoe_dem
   
    iii.    Bandanna_dem
   
    iv.    Rewan_dem and dunda_dem
   
    v.     Clematis_dem and warang_dem
   
    vi.    Moolyember_surface_dem
   

   b. Used Contour tool in ArcGIS to obtain a 25 metre contour geodatabase from the relevant model DEM

    i.     Basement_dem_contours
   
    ii.    Joejoe_dem_contours
   
    iii.    Bandanna_dem_contours
   
    iv.    Rewan_dem_contours and dunda_dem_contours
   
    v.     Clematis_dem_contours and warang_dem_contours
   
    vi.    Moolyember_dem_contours
   

   c. For the purpose of guiding the model building process additional fields were added to each DEM contour geodatabase was added based on average thickness derived from groundwater bores and petroleum wells.

    i.     Basement_dem_contours: Joejoe, bandanna, rewan, clematis, moolyember
   
    ii.    Joejoe_dem_contours: basement, bandanna
   
    iii.    Bandanna_dem_contours: joejoe, rewan
   
    iv.    Rewan_dem_contours and dunda_dem_contours: clematis, rewan
   
    v.     Clematis_dem_contours and warang_dem_contours: moolyember, rewan
   
    vi.  Moolyember_dem_contours: clematis
   

The model building process is as follows:

1. Used the tope to raster tool to create surface based on the following rules

   a. Environment

       i.  Extent
   
          1. Top: -19.7012030024424
   
          2. Right: 148.891511819054
   
          3. Bottom: -27.5812030024424
   
          4. Left: 139.141511819054
   
       ii. Output cell size: 0.01 degrees
   
       iii. Drainage enforcement: No_enforce
   

   b. Input

       i.  Basement
   
          1. Basement_dem_contour; field - contour; type - contour
   
          2. Joejoe_dem_contour; field - basement; type - contour
   
          3. Basement_contour; field - contour; type - contour
   
          4. GSQ_basement_wells; field - top_m_AHD; type - point elevation
   
          5. GW_basement; field - top_m_AHDl type - point elevation
   
          6. GSQ_top_basement_fake; field - top_m_AHDl type - point elevation
   
          7. Basement_faults; type - cliff
   
      ii.  Joe Joe Group
   
          1. Joejoe_dem_contour; field - basement; type - contour
   
          2. Basement_dem_contour; field - joejoe; type - contour
   
          3. permian_dem_contour; field - joejoe, type - contour
   
          4. joejoe_contour; field - joejoe; type - contour
   
          5. GSQ_top_joejoe_group; field - top_m_AHD; type - point elevation
   
          6. GW_bores_joe_joe_group; field - top_m_AHDl type - point elevation
   
          7. joejoe_faults; type - cliff
   
      iii.  Bandanna Group
   
          1. Permian_dem_contour; field - contour; type - contour
   
          2. Joejoe_dem_contour; field - bandanna; type - contour
   
          3. Rewan_dem_contour: field - bandanna; type - contour
   
          4. Dunda_dem_contour; field - bandanna; type - contour
   

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We used ERDAS Imagine ® Professional 9.2, ENVI ® 4.5, and ArcGIS ® 9.3 with Arc Workstation to develop the vegetation spatial database. Existing GIS datasets that we used to provide mapping information include a NPS park boundary shapefile for VICK (including a 100 meter buffer boundary around the Louisiana Circle, South Fort, and Navy Circle satellite units), a land cover shapefile created by the NWRC (Rangoonwala et al. 2007), and the National Elevation Dataset (NED) (used as the source of the 10-meter elevation model and derived streams, slope, and hillshade). To make the entire spatial data set consistent with NPSVI policies to map only to park boundaries, we clipped the vegetation in and around the previously buffered areas around the Louisiana Circle, South Fort, and Navy Circle satellite unit NPS boundaries. We also added to the spatial database vegetation polygons for the previously omitted Grant’s Canal satellite unit by heads-up digitizing this area from a National Agricultural Information Program (NAIP) image.

Footprint of buildings (outer envelope) with an area greater than 100 square feet. Interior rooflines, such as dormers, not captured. Attached garages captured as part of the structure. Carports and other extensions over pavement, typically serving as protection from inclement weather, captured as canopies. Decks, patios, stairs, etc. not captured as part of the structure. Countywide data updated Spring 2023. For more information, contact: GIS Manager Information Technology & Innovation (ITI) Montgomery County Planning Department, MNCPPC T: 301-650-5620

Footprint of buildings (outer envelope) with an area greater than 100 square feet. Interior rooflines, such as dormers, not captured. Attached garages captured as part of the structure. Carports and other extensions over pavement, typically serving as protection from inclement weather, captured as canopies. Decks, patios, stairs, etc. not captured as part of the structure. Countywide data updated Spring 2020. For more information, contact: GIS Manager Information Technology & Innovation (ITI) Montgomery County Planning Department, MNCPPC T: 301-650-5620

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles.

To produce the digital map 38 map units (21 vegetated and 17 land use) were developed and directly cross-walked or matched to their corresponding plant associations and land use classes. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. Draft maps were printed, field tested, reviewed, and revised.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer of INDU and immediate environs. At this stage, the map layer has only map attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map class names, physiognomic definitions, link to NVC association and alliance codes), we produced a feature class table along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature class layers produced from this project, including vegetation sample plots, accuracy assessment sites, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

This geodatabase includes spatial datasets that represent the Mississippian aquifer in the States of Alabama, Illinois, Indiana, Iowa, Kentucky, Maryland, Missouri, Ohio, Pennsylvania, Tennessee, Virginia and West Virginia. The aquifer is divided into three subareas, based on the data availability. In subarea 1 (SA1), which is the aquifer extent in Iowa, data exist of the aquifer top altitude and aquifer thickness. In subarea 2 (SA2), which is the aquifer extent in Missouri, data exist of the aquifer top and bottom aquifer surface altitudes. In subarea 3 (SA3), which is the aquifer area of the remaining States, no altitude or thickness data exist. Included in this geodatabase are: (1) a feature dataset "ds40MSSPPI_altitude_and_thickness_contours that includes aquifer altitude and thickness contours used to generate the surface rasters for SA1 and SA2, (2) a feature dataset "ds40MSSPPI_extents" that includes a polygon dataset that represents the subarea extents, a polygon dataset that represents the combined overall aquifer extent, and a polygon dataset of the Ft. Dodge Fault and Manson Anomaly, (3) raster datasets that represent the altitude of the top and the bottom of the aquifer in SA1 and SA2, and (4) georeferenced images of the figures that were digitized to create the aquifer top- and bottom-altitude contours or aquifer thickness contours for SA1 and SA2. The images and digitized contours are supplied for reference. The extent of the Mississippian aquifer for all subareas was produced from the digital version of the HA-730 Mississippian aquifer extent, (USGS HA-730). For the two Subareas with vertical-surface information, SA1 and SA2, data were retrieved from the sources as described below. 1. The aquifer-altitude contours for the top and the aquifer-thickness contours for the top-to-bottom thickness of SA1 were received in digital format from the Iowa Geologic Survey. The URL for the top was ftp://ftp.igsb.uiowa.edu/GIS_Library/IA_State/Hydrologic/Ground_Waters/ Mississippian_aquifer/mississippian_topography.zip. The URL for the thickness was ftp://ftp.igsb.uiowa.edu/GIS_Library/IA_State/Hydrologic/Ground_Waters/ Mississippian_aquifer/mississippian_isopach.zip Reference for the top map is Altitude and Configuration, in feet above mean sea level, of the Mississipian Aquifer modified from a scanned image of Map 1, Sheet 1, Miscellaneous Map Series 3, Mississippian Aquifer of Iowa by P.J. Horick and W.L. Steinhilber, Iowa Geological Survey, 1973; IGS MMS-3, Map 1, Sheet 1 Reference for the thickness map is Distribution and isopach thickness, in feet, of the Mississipian Aquifer, modified from a scanned image of Map 1, Sheet 2, Miscellaneous Map Series 3, Mississippian Aquifer of Iowa by P.J. Horick and W.L. Steinhilber, Iowa Geological Survey, 1973; IGS MMS-3, Map 1, Sheet 2 The altitude contours for the top and bottom of SA2 were digitized from georeferenced figures of altitude contours in U.S. Geological Survey Professional Paper 1305 (USGS PP1305), figure 6 (for the top surface) and figure 9 (for the bottom surface). The altitude contours for SA1 and SA2 were interpolated into surface rasters within a GIS using tools that create hydrologically correct surfaces from contour data, derive the altitude from the thickness (depth from the land surface), and merge the subareas into a single surface. The primary tool was an enhanced version of "Topo to Raster" used in ArcGIS, ArcMap, Esri 2014. ArcGIS Desktop: Release 10.2 Redlands, CA: Environmental Systems Research Institute. The raster surfaces were corrected in areas where the altitude of the top of the aquifer exceeded the land surface, and where the bottom of an aquifer exceeded the altitude of the corrected top of the aquifer.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. To produce the digital map, a combination of 1:12,000-scale true color digital ortho-imagery acquired in 2003, 1:12,000-scale true color ortho-rectified imagery acquired in 2005, and all of the GPS referenced ground data were used. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. All of the resulting map unit names, map unit codes, NVC information, and other relevant attributes were added to each polygon in the GIS layer.

Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13