If you have ever had an error message pop up in ArcGIS Online that mentions you have exceeded the user types in your account, watch this video to see how to resolve this issue.This video takes you through the steps of how to do change students and teachers user types on the rare occasion that you are required to change user types in your schools ArcGIS Online account.ArcGIS Online Administration.Video recorded - April 2020.

Laatste update: 10 februari 2025Terug naar Esri Nederland Support HubArcGIS Online kent verschillende User Types. Elke User Type heeft verschillende functionaliteiten en rechten tot specifieke producten. Een Creator User Type heeft bijvoorbeeld toegang tot ArcGIS Pro Basic terwijl een Viewer User Type dit niet heeft. Zie ArcGIS User Type Comparison Matrix.Bij elke User Type zitten bepaalde licenties inbegrepen. Mocht dit niet voldoende zijn dan is het mogelijk om add-on licenties aan te schaffen en deze toe te wijzen aan een gebruiker. Een beheerder kan deze licenties toewijzen in het ArcGIS Online Portaal. Zie ook: Licenties toewijzen

In order to use the standard color legend for Romanian soil type maps in the ESRI ArcMap-10 electronic format, a dataset consisting a shapefile set (.dbf, .shp, .shx, .sbn, and .sbx files), four different .lyr files, and three different .style files have been prepared (ESRI, 2016). The shapefile set is not a “real” georeferenced layer/coverage; it is designed only to handle all the instants of soil types from the standard legend. This legend contains 67 standard items: 63 proper colors (different color hues, each of them having, generally, 2 - 4 degrees of lightness and/or chroma, four shades of grey, and white color), and four hatching patterns on white background (ESRI, 2016). The “color difference DE*ab” between any two legend colors, calculated with the color perceptually-uniform model CIELAB , is greater than 10 units, thus ensuring acceptably-distinguishable colors in the legend. The 67 standard items are assigned to 60 main soils existing in Romania, four main nonsoils, and three special cases of unsurveyed land. The soils are specified in terms of the current Romanian system of soil taxonomy, SRTS-2012+, and of the international soil classification system WRB-2014. The four different .lyr files presented here are: legend_soilcode_srts_wrb.lyr, legend_soilcode_wrb.lyr, legend_colourcode_srts_wrb.lyr, and legend_colourcode_wrb.lyr. The first two of them are built using as value field the ‘Soil_codes’ field, and as labels (explanation texts) the ‘Soil_name’ field (storing the soil types according to SRTS/WRB classification), respectively, the ‘WRB’ field (the soil type according to WRB classification), while the last two .lyr files are built using as value field the ‘colour_code’ field (storing the color codes) and as labels the soil name in SRTS and WRB, respectively, in WRB classification. In order to exemplify how the legend is displayed, two .jpg files are also presented: legend_soil_srts_wrb.jpg and legend_colour_wrb.jpg. The first displays the legend (symbols and labels) according to the SRTS classification order, the second according to the WRB classification. The three different .style files presented here are: soil_symbols.style, wrb_codes.style, and colour_codes.style. They use as name the soil acronym in SRTS classification, soil acronym in WRB classification, and, respectively, the color code.

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

This dashboard defaults to a presentation of the crash points that will cluster the crash types and determine a predominant crash type. In the case two crash types have the same number of crashes for that type the predominant type will not be colored to either of the crash types. Clicking on the clusters will include a basic analysis of the cluster. These clusters are dynamic and will change as the user zooms in an out of the map. The clustering of crashes is functionality availalble in ArcGIS Online and the popups for the clusters is based on items that include elements configured with the Arcade language. Users interested in learning more about point clustering and the configuration of popups should read through some of the examples of the following ESRI Article (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/) . The dashboard itself does include a map widget that does allow the user to toggle the visibility of layers and/or click on the crashes within the map. The popups for single crashes can be difficult to see unless the map is expanded (click in upper right of map widget). There is a Review Crashes tab that allows for another display of details of a crash that may be easier for users.This dashboard includes selectors in both the header and sidebar. By default the sidebar is collapsed and would need to be expanded. The crash dataset used in the presentation includes columns with a prefix of the unit. The persons information associated to each unit would be based on the Person that was considered the driver. Crash data can be filtered by clicking on items in chart widgets. All chart widgets have been configured to allow multiple selections and these selections will then filter the crash data accordingly. Allowing for data to be filtered by clicking on widgets is an alternative approach to setting up individual selectors. Selectors can take up a lot of space in the header and sidebar and clicking on the widget items can allow you to explore different scenarios which may ultimately be setup as selectors in the future. The Dashboard has many widgets that are stacked atop each other and underneath these stacked widgets are controls or tabs that allow the user to toggle between different visualizations. The downside to allowing a user to filter based on the output of a widget is the need for the end user to keep track of what has been clicked and the need to go back through and unclick.Many of the Crash Data Elements are based on lookups that have a fairly large range of values to select. This can be difficult sometimes with charts and the fact that a user may be overwhelmed by the number of items be plotted. Some of these values could potentially benefit by grouping similar values. The crash data being used in this dashboard hasn't been post processed to simplify some of the groupings of data and represent the value as it would appear in the Crash System. This dashboard was put together to continue the discussion on what data elements should be included in the GIS Crash Dataset. At the moment there is currently one primary dataset that is used to present crash data in Map Services. There is lots of potential to extend this dataset to include additional elements or it might be beneficial to create different versions of the crash data. Having an examples like this one will hopefully help with the discussion. Workable examples of what works and doesn't work. There are lots of data elements in the Crash System that could allow for an even more detailed safety analysis. Some of the unit items included in the example for Minot Ave in Auburn are the following. This information is included for the first three units associated to any crash.Most Damaged AreaExtent of DamageUnit TypeDirection of Travel (Northbound, Southbound, Eastbound, Westbound)Pre-Crash ActionsSequence of Events 1-4Most Harmful Event Some of the persons items included in the example for Minot Ave in Auburn are the following. This information is included for the first three units associated to any crash and the person would be based on the driver.Condition at Time of CrashDriver Action 1Driver Action 2Driver DistractedAgeSexPerson Type (Driver/Owner(6), Driver(1))In addition to the Units and Persons information included above each crash includes the standard crash data elements which includesDate, Time, Day of Week, Year, Month, HourInjury Level (K,A,B,C,PD)Type of CrashTownname, County, MDOT RegionWeather ConditionsLight ConditionsRoad Surface ConditionsRoad GradeSchool Bus RelatedTraffic Control DeviceType of LocationWork Zone ItemsLocation Type (NODE, ELEMENT) used for LRS# of K, # of A, # of B, # of C, # of PD InjuriesTotal # of UnitsTotal # of PersonsFactored AADT (Only currently applicable for crashes along the roadway (ELEMENT)).Location of First Harmful EventTotal Injury Count for the CrashBoolean Y/N if Pedestrian or Bicycles are InvolvedContributing EnvironmentsContributing RoadRoute Number, Milepoint, Element ID, Node ID

The U.S. Geological Survey has been forecasting sea-level rise impacts on the landscape to evaluate where coastal land will be available for future use. The purpose of this project is to develop a spatially explicit, probabilistic model of coastal response for the Northeastern U.S. to a variety of sea-level scenarios that take into account the variable nature of the coast and provides outputs at spatial and temporal scales suitable for decision support. Model results provide predictions of adjusted land elevation ranges (AE) with respect to forecast sea-levels, a likelihood estimate of this outcome (PAE), and a probability of coastal response (CR) characterized as either static or dynamic. The predictions span the coastal zone vertically from -12 meters (m) to 10 m above mean high water (MHW). Results are produced at a horizontal resolution of 30 meters for four decades (the 2020s, 2030s, 2050s and 2080s). Adjusted elevations and their respective probabilities are generated using regional geospatial datasets of current sea-level forecasts, vertical land movement rates, and current elevation data. Coastal response type predictions incorporate adjusted elevation predictions with land cover data and expert knowledge to determine the likelihood that an area will be able to accommodate or adapt to water level increases and maintain its initial land class state or transition to a new non-submerged state (dynamic) or become submerged (static). Intended users of these data include scientific researchers, coastal planners, and natural resource management communities.

The Digital Geologic-GIS Map of San Miguel Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (smis_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (smis_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (smis_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (smis_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (smis_geology_metadata.txt or smis_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Soil_Samples_BACI Available only by request on a case by case basis. Contact rthe author, David Nowak, at dnowak@fs.fed.us Tags Biophysical Resources, Land, Social Institutions, Health, BES, Soil, Lead, Sample, UFORE Summary Samples were taken to relate soil data to vegetation data obtained for the Urban Forestry Effects Model (UFORE). Description The data is soil concentrations and characteristics of the following: land use, bulk density, sand, silt, clay, pH, organic matter, nitrogen, Al, P, S, Ti, Cr, Mn, Fe, Co, Ni, Cu Zn, Mo, Pb, Cd, Na, Mg, K, Ca, and V. Soils were sampled in 125 plots located within the City of Baltimore in the summer of 2000. The plots were randomly stratified by Anderson Land Cover Classification System Level II, which included commercial, industrial, institutional, transportation right-of-ways, high and medium density residential (there were no low density residential areas identified within the city boundaries), golf course, park, urban open, forest, and wetland land-use types. The number of plots situated in each land-use type was weighted to their proportion of spatial area within the City. The resultant number of plots sampled for soil by land-use type was: commercial (n = 2); industrial (n = 3); institutional (n = 10); transportation right-of-ways (n = 7); high density residential (n = 19); medium density residential (n = 33); golf course (n = 3); riparian (n=2); park (n = 10); urban open (n = 10); and forest (n = 26) land-use types, respectively. The distribution of plots represents the proportion of area covered by impervious surfaces. Credits Rich Pouyat, USDA Forest Service Use limitations Not for profit use only Extent West -76.711030 East -76.530612 North 39.371355 South 39.200686 Scale Range There is no scale range for this item. The data is soil concentrations and characteristics of the following: land use, bulk density, sand, silt, clay, pH, organic matter, nitrogen, Al, P, S, Ti, Cr, Mn, Fe, Co, Ni, Cu Zn, Mo, Pb, Cd, Na, Mg, K, Ca, and V. Soils were sampled in 125 plots located within the City of Baltimore in the summer of 2000. The plots were randomly stratified by Anderson Land Cover Classification System Level II, which included commercial, industrial, institutional, transportation right-of-ways, high and medium density residential (there were no low density residential areas identified within the city boundaries), golf course, park, urban open, forest, and wetland land-use types. The number of plots situated in each land-use type was weighted to their proportion of spatial area within the City. The resultant number of plots sampled for soil by land-use type was: commercial (n = 2); industrial (n = 3); institutional (n = 10); transportation right-of-ways (n = 7); high density residential (n = 19); medium density residential (n = 33); golf course (n = 3); riparian (n=2); park (n = 10); urban open (n = 10); and forest (n = 26) land-use types, respectively. The distribution of plots represents the proportion of area covered by impervious surfaces.

Land cover describes the surface of the earth. Land-cover maps are useful in urban planning, resource management, change detection, agriculture, and a variety of other applications in which information related to the earth's surface is required. Land-cover classification is a complex exercise and is difficult to capture using traditional means. Deep learning models are highly capable of learning these complex semantics and can produce superior results.There are a few public datasets for land cover, but the spatial and temporal coverage of these public datasets may not always meet the user’s requirements. It is also difficult to create datasets for a specific time, as it requires expertise and time. Use this deep learning model to automate the manual process and reduce the required time and effort significantly.Using the modelFollow the guide to use the model. Before using this model, ensure that the supported deep learning libraries are installed. For more details, check Deep Learning Libraries Installer for ArcGIS.Fine-tuning the modelThis model can be fine-tuned using the Train Deep Learning Model tool. Follow the guide to fine-tune this model.Input8-bit, 3-band very high-resolution (10 cm) imagery.OutputClassified raster with the 8 classes as in the LA county landcover dataset.Applicable geographiesThe model is expected to work well in the United States and will produce the best results in the urban areas of California.Model architectureThis model uses the UNet model architecture implemented in ArcGIS API for Python.Accuracy metricsThis model has an overall accuracy of 84.8%. The table below summarizes the precision, recall and F1-score of the model on the validation dataset: ClassPrecisionRecallF1 ScoreTree Canopy0.8043890.8461520.824742Grass/Shrubs0.7199930.6272780.670445Bare Soil0.89270.9099580.901246Water0.9808850.9874990.984181Buildings0.9222020.9450320.933478Roads/Railroads0.8696370.8629210.866266Other Paved0.8114650.8119610.811713Tall Shrubs0.7076740.6382740.671185Training dataThis model has been trained on very high-resolution Landcover dataset (produced by LA County).LimitationsSince the model is trained on imagery of urban areas of LA County it will work best in urban areas of California or similar geography.Model is trained on limited classes and may lead to misclassification for other types of LULC classes.Sample resultsHere are a few results from the model.

The Digital Geologic-GIS Map of Yosemite Valley Glacial and Postglacial Deposits, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (yova_glacial_and_surficial_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (yova_glacial_and_surficial_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (yova_glacial_and_surficial_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (yose_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (yova_glacial_and_surficial_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (yova_glacial_and_surficial_geology_metadata_faq.pdf). Please read the yose_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (yova_glacial_and_surficial_geology_metadata.txt or yova_glacial_and_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

THE EARTH SCIENCE GEOINQUIRY COLLECTION

http://www.esri.com/geoinquiries

To support Esri’s involvement in the White House ConnectED Initiative, GeoInquiry instructional materials using ArcGIS Online for Earth Science education are now freely available.

The Earth Science GeoInquiry collection contains 15 free, web-mapping activities that correspond and extend map-based concepts in leading middle school Earth science textbooks. The activities, developed with GISetc of Dallas, TX use a standard inquiry-based instructional model, require only 15 minutes for a teacher to deliver, and are device agnostic. The activities harmonize with the Next Generation Science Standards. Activity topics include:

Teachers, GeoMentors, and administrators can learn more at http://www.esri.com/geoinquiries

The Unpublished Digital Geologic-GIS Map of Tuzigoot National Monument, Arizona is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (tuzi_geology.gdb), a 10.1 ArcMap (.MXD) map document (tuzi_geology.mxd), individual 10.1 layer (.LYR) files for each GIS data layer, an ancillary map information (.PDF) document (moca_tuzi_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.TXT) and FAQ (.HTML) formats, and a GIS readme file (moca_tuzi_geology_gis_readme.pdf). Please read the moca_tuzi_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. Google Earth software is available for free at: http://www.google.com/earth/index.html. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (tuzi_geology_metadata_faq.html; available at http://nrdata.nps.gov/geology/gri_data/gis/tuzi/tuzi_geology_metadata_faq.html). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:48,000 and United States National Map Accuracy Standards features are within (horizontally) 24.4 meters or 80 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 12N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Tuzigoot National Monument.

The Digital Geologic-GIS Map of Sagamore Hill National Historic Site and Vicinity, New York is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (sahi_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (sahi_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sahi_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (sahi_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (sahi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (sahi_geology_metadata_faq.pdf). Please read the sahi_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sahi_geology_metadata.txt or sahi_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The Digital Geomorphic-GIS Map of Gulf Islands National Seashore (5-meter accuracy and 1-foot resolution 2006-2007 mapping), Mississippi and Florida is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (guis_geomorphology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (guis_geomorphology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (guis_geomorphology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (guis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (guis_geomorphology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (guis_geomorphology_metadata_faq.pdf). Please read the guis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (guis_geomorphology_metadata.txt or guis_geomorphology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:26,000 and United States National Map Accuracy Standards features are within (horizontally) 13.2 meters or 43.3 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

THE GEOINQUIRIES™ COLLECTION FOR EARTH SCIENCE

http://www.esri.com/geoinquiries

The Esri GeoInquiry™ collection for Earth Science contains 15 free, web-mapping activities that correspond and extend map-based concepts in leading middle school Earth science textbooks. The activities use a standard inquiry-based instructional model, require only 15 minutes for a teacher to deliver, and are device agnostic. The activities harmonize with the Next Generation Science Standards.

All American Literature GeoInquiries™ can be found at: http://esriurl.com/earthGeoInquiry

All GeoInquiries™ can be found at: http://www.esri.com/geoinquiries

Author: Titus, Maxwell (mtitus@esri.com)Last Updated: 3/4/2025Intended Environment: ArcGIS Online or ArcGIS PortalPurpose: A notebook designed to help batch transfer content between users while maintaining folder structure and sharing privileges. Description: This ArcGIS Notebook will batch-transfer content from one user to another. The full capabilities of this Notebook include:Batch transfer content from one user to anotherWhen content is transferred, the original folder structure that the user maintained is created by creating new folders in the new owner's portal content.Optionally, enable group sharing integrity when transferring item ownership. When enabled, the new item's owner will be added to any groups shared with the items.Optionally specify all content to transfer, content by a specific type, and content by a particular folder. - This includes specifying content to ignore based on specific types and specific folders. Notebook Requirements: This Notebook has the following requirements:This ArcGIS Notebook requires admin privileges to functionally run.

GIS shapefile of extensive land use and geographic data at the tax lot level. The PLUTO files contain more than seventy fields derived from data maintained by city agencies. Essentially, displays a plethora of plot data including size, tax lot, and other publicly available information. MapPLUTO merges PLUTO tax lot data with tax lot features from the Department of Finance’s Digital Tax Map (DTM), clipped to the shoreline. It contains extensive land use and geographic data at the tax lot level in ESRI shape file format and dbase table format.

The Digital Geologic-GIS Map of Santa Cruz Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (scis_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (scis_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (scis_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (scis_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (scis_geology_metadata.txt or scis_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).