The Minnesota DNR Toolbox and Hydro Tools provide a number of convenience geoprocessing tools used regularly by MNDNR staff. Many of these may be useful to the wider public. However, some tools may rely on data that is not available outside of the DNR. All tools require at least ArcGIS 10+.

If you create a GDRS using GDRS Manager and include this toolbox resource and MNDNR Quick Layers, the DNR toolboxes will automatically be added to the ArcToolbox window whenever Quick Layers GDRS Location is set to the GDRS location that has the toolboxes.

Toolsets included in MNDNR Tools V10:
- Analysis Tools
- Conversion Tools
- Division Tools
- General Tools
- Hydrology Tools
- LiDAR and DEM Tools
- Raster Tools
- Sampling Tools

These toolboxes are provided free of charge and are not warrantied for any specific use. We do not provide support or assistance in downloading or using these tools. We do, however, strive to produce high-quality tools and appreciate comments you have about them.

The Minnesota DNR Toolbox provides a number of convenience geoprocessing tools used regularly by MNDNR staff. Many of these may be useful to the wider public. However, some tools may rely on data that is not available outside of the DNR.

Toolsets included in MNDNR Tools:
- Analysis Tools
- Conversion Tools
- General Tools
- LiDAR and DEM Tools
- Sampling Tools

The application download includes a comprehensive help document, which you can also access separately here: ArcGISPro_MNDNR_Toolbox_Pro_User_Guide.pdf

These toolboxes are provided free of charge and are not warrantied for any specific use. We do not provide support or assistance in downloading or using these tools. We do, however, strive to produce high-quality tools and appreciate comments you have about them.

SSURGO-QA ArcGIS Pro Toolbox1. SetupDownload SSURGO by Areasymbol - Use Soil Data Access and Web Soil Survey download page to get SSURGO datasets. User can a wildcard to query the database by Areasymbol or by age.Download SSURGO by Region - Downloads SSURGO Soil Survey Areas that are owned by a specific region including an approximiate 2 soil survey area buffer.Generate Regional Transactional Geodatabase - Used to create the Regional Transactional Spatial Database (RTSD) for SSURGO.Generate SSO SSURGO Datasets - Create a SSURGO file geodatabase for a selected MLRA Soil Survey Office.Import SSURGO Datasets in FGDB - This tooll will import SSURGO spatial and tabular datasets within a given location into a File Geodatabase and establish the necessary table and feature class relationships to interact with the dataset.Insert NATSYM and MUNAME Value - This tool adds the National Mapunit Symbol (NATMUSYM) and the Mapunit Name (MUNAME) values to the corresponding MUKEY. An MUKEY field is required to execute. A network connection is required in order to submit a query to SDacess.RTSD - Check SDJR Project Out - Designed to work with the RTSD to manage SDJR projects and export data for those projects to be sent to the MLRA SSO.

The Grid Garage Toolbox is designed to help you undertake the Geographic Information System (GIS) tasks required to process GIS data (geodata) into a standard, spatially aligned format. This format is required by most, grid or raster, spatial modelling tools such as the Multi-criteria Analysis Shell for Spatial Decision Support (MCAS-S). Grid Garage contains 36 tools designed to save you time by batch processing repetitive GIS tasks as well diagnosing problems with data and capturing a record of processing step and any errors encountered.

Grid Garage provides tools that function using a list based approach to batch processing where both inputs and outputs are specified in tables to enable selective batch processing and detailed result reporting. In many cases the tools simply extend the functionality of standard ArcGIS tools, providing some or all of the inputs required by these tools via the input table to enable batch processing on a 'per item' basis. This approach differs slightly from normal batch processing in ArcGIS, instead of manually selecting single items or a folder on which to apply a tool or model you provide a table listing target datasets. In summary the Grid Garage allows you to:

• List, describe and manage very large volumes of geodata.
• Batch process repetitive GIS tasks such as managing (renaming, describing etc.) or processing (clipping, resampling, reprojecting etc.) many geodata inputs such as time-series geodata derived from satellite imagery or climate models.
• Record any errors when batch processing and diagnose errors by interrogating the input geodata that failed.
• Develop your own models in ArcGIS ModelBuilder that allow you to automate any GIS workflow utilising one or more of the Grid Garage tools that can process an unlimited number of inputs.
• Automate the process of generating MCAS-S TIP metadata files for any number of input raster datasets.

The Grid Garage is intended for use by anyone with an understanding of GIS principles and an intermediate to advanced level of GIS skills. Using the Grid Garage tools in ArcGIS ModelBuilder requires skills in the use of the ArcGIS ModelBuilder tool.

Download Instructions: Create a new folder on your computer or network and then download and unzip the zip file from the GitHub Release page for each of the following items in the 'Data and Resources' section below. There is a folder in each zip file that contains all the files. See the Grid Garage User Guide for instructions on how to install and use the Grid Garage Toolbox with the sample data provided.

Succeeds and combines earlier versions of the tools - Topography Toolbox for ArcGIS 9.x - http://arcscripts.esri.com/details.asp?dbid=15996Riparian Topography Toolbox for calculating Height Above River and Height Above Nearest Drainage - http://arcscripts.esri.com/details.asp?dbid=16792PRISM Data Helper - http://arcscripts.esri.com/details.asp?dbid=15976Tools:UplandBeer’s AspectMcCune and Keon Heat Load IndexLandform ClassifcationPRISM Data HelperSlope Position ClassificationSolar Illumination IndexTopographic Convergence/Wetness IndexTopographic Position IndexRiparianDerive Stream Raster using Cost DistanceHeight Above Nearest DrainageHeight Above RiverMiscellaneousMoving Window Correlation

The Seabed Landform Classification Toolset is a GIS toolbox designed to classify seabed landforms on continental and island shelf settings. The user is guided through a series of classification steps within an ArcGIS toolbox to classify prominent seabed features termed ‘seabed landforms’, which characterise the morphology of the seabed surface. Seabed landforms include reefs/banks, peaks, plains, scarps, channels and depressions. Plain areas can additionally be classified into high and low features at localised and broad scales to capture features within plain surfaces. Common variables for seabed classification are utilised, including slope, bathymetric position index and ruggedness, and a series of procedures are applied to identify reef outcrops and minimise noise. The classification approach applies a whole-seascape classification which is aimed to offer a flexible and user-friendly approach to extract key seabed features from high-resolution shelf bathymetry data.

This toolset was developed using ESRI ArcGIS Desktop 10.8 and requires an Advanced licence with Spatial Analyst and 3D Analyst and extensions. It utilises scripts within the Benthic Terrain Modeler toolset (Walbridge et al. 2018) and Geomorphometry and Gradients Metrics Toolbox (Evans et al., 2014).

Please read the User Guide and supporting documentation for information on how to run the toolset. A web explainer is available at: https://arcg.is/1Tqmv50

The Seabed Landform Classification Toolset is also available for download on GitHub (https://github.com/LinklaterM/Seabed-Landforms-Classification-Toolset/).

The toolset was developed by the Coastal and Marine Team, NSW Department of Climate Change, Energy, the Environment and Water (formerly NSW Department of Planning and Environment), funded by NSW Climate Change Fund through the Coastal Management Funding Package and the Marine Estate Management Authority.

Please cite this toolset as: Linklater, M, Morris, B.D. and Hanslow, D.J. (2023) Classification of seabed landforms on continental and island shelves. Frontiers of Marine Science, 10, https://doi.org/10.3389/fmars.2023.1258556.

Other toolsets utilised by the Seabed Landform Classification Toolset include: Benthic Terrain Modeler: Walbridge, S., Slocum, N., Pobuda, M., and Wright, D. J. (2018). Unified geomorphological analysis workflows with Benthic Terrain Modeler. Geosciences 8, 94. Geomorphometry and Gradients Metrics Toolbox: Evans, J., Oakleaf, J., and Cushman, S. (2014). An ArcGIS Toolbox for Surface Gradient and Geomorphometric Modeling, Version 2.0-0. https://github.com/jeffreyevans/GradientMetrics.

The Topography Toolbox has been updated and expanded for ArcGIS Pro. Tools calculate:McCune and Keon (2002) Heat Load IndexSlope Position ClassificationTopographic Convergence/Wetness IndexTopographic Position IndexMultiscale Topographic Position IndexHeight Above Nearest DrainageHeight Above RiverVector Ruggedness MeasureLocalized Vector Ruggedness MeasureWind Exposure/Shelter IndexHypsometric Integral

Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum

The Travel Time Tool was created by the MN DNR to use GIS analysis for calculation of hydraulic travel time from gridded surfaces and develop a downstream travel time raster for each cell in a watershed. This hydraulic travel time process, known as Time of Concentration, is a concept from the science of hydrology that measures watershed response to a precipitation event. The analysis uses watershed characteristics such as land-use, geology, channel shape, surface roughness, and topography to measure time of travel for water. Described as Travel Time, it calculates the elapsed time for a simulated drop of water to migrate from its source along a hydraulic path across different surfaces of the replicated watershed landscape, ultimately reaching the watershed outlet. The Travel Time Tool creates a raster whereas each cell is a measure of the length of time (in seconds) that it takes water to flow across it, and then accumulates the time (in hours) from the cell to the outlet of the watershed.

The Travel Time Tool creates an impedance raster from Manning's Equation that determines the velocity of water flowing across the cell as a measure of time (in feet per second). The Flow Length Tool uses the travel time Grid for the impedance factor and determines the downstream flow time from each cell to the outlet of the watershed.

The toolbox works with ArcMap 10.6.1 and newer and ArcGIS Pro.

For step-by-step instructions on how to use the tool, please view MN DNR Travel Time Guidance.pdf

ssurgoOnDemandThe purpose of these tools are to give users the ability to get Soil Survey Geographic Database (SSURGO) properties and interpretations in an efficient manner. They are very similiar to the United States Department of Agriculture - Natural Resource Conservation Service's distributed Soil Data Viewer (SDV), although there are distinct differences. The most important difference is the data collected with the SSURGO On-Demand (SOD) tools are collected in real-time via web requests to Soil Data Access (https://sdmdataaccess.nrcs.usda.gov/). SOD tools do not require users to have the data found in a traditional SSURGO download from the NRCS's official repository, Web Soil Survey (https://websoilsurvey.sc.egov.usda.gov/App/HomePage.htm). The main intent of both SOD and SDV are to hide the complex relationships of the SSURGO tables and allow the users to focus on asking the question they need to get the information they want. This is accomplished in the user interface of the tools and the subsequent SQL is built and executed for the user. Currently, the tools packaged here are designed to run within the ESRI ArcGIS Desktop Application - ArcMap, version 10.1 or greater. However, much of the Python code is recyclable and could run within a Python intepreter or other GIS applications such as Quantum GIS with some modification.NOTE: The queries in these tools only consider the major components of soil map units.Within the SOD tools are 2 primary toolsets, descibed as follows:<1. AreasymbolThe Areasymbol tools collect SSURGO properties and interpretations based on a user supplied list of Soil Survey areasymbols (e.g. NC123). After the areasymbols have been collected, an aggregation method (see below) is selected . Tee aggregation method has no affect on interpretations other than how the SSURGO data aggregated. For soil properties, the aggregation method drives what properties can be run. For example, you can't run the weighted average aggregation method on Taxonomic Order. Similarly, for the same soil property, you wouldn't specify a depth range. The point here is the aggregation method affects what parameters need to be supplied for the SQL generation. It is important to note the user can specify any number of areasymbols and any number of interpretations. This is another distinct advantage of these tools. You could collect all of the SSURGO interpretations for every soil survey area (areasymbol) by executing the tool 1 time. This also demonstrates the flexibility SOD has in defining the geographic extent over which information is collected. The only constraint is the extent of soil survey areas selected to run (and these can be discontinuous).As SOD Areasymbol tools execute, 2 lists are collected from the tool dialog, a list of interpretations/properties and a list of areasymbols. As each interpretation/property is run, every areasymbol is run against the interpretation/property requested. For instance, suppose you wanted to collect the weighted average of sand, silt and clay for 5 soil survey areas. The sand property would run for all 5 soil survey areas and built into a table. Next the silt would run for all 5 soil survey areas and built into a table, and so on. In this example a total of 15 web request would have been sent and 3 tables are built. Two VERY IMPORTANT things here...A. All the areasymbol tools do is generate tables. They are not collecting spatial data.B. They are collecting stored information. They are not making calculations(with the exception of the weighted average aggregation method).<2. ExpressThe Express toolset is nearly identical to the Areasymbol toolset, with 2 exceptions.A. The area to collect SSURGO information over is defined by the user. The user digitizes coordinates into a 'feature set' after the tool is open. The points in the feature set are closed (first point is also the last) into a polygon. The polygon is sent to Soil Data Access and the features set points (polygon) are used to clip SSURGO spatial data. The geomotries of the clip operation are returned, along with the mapunit keys (unique identifier). It is best to keep the points in the feature set simple and beware of self intersections as they are fatal.B. Instead of running on a list of areasymbols, the SQL queries on a list of mapunit keys.The properties and interpretations options are identical to what was discussed for the Areasymbol toolset.The Express tools present the user the option of creating layer files (.lyr) where the the resultant interpretation/property are joined to the geometry and saved to disk as a virtual join. Additionally, for soil properties, an option exists to append all of the selected soil properties to a single table. In this case, if the user ran sand, silt, and clay properties, instead of 3 output tables, there is only 1 table with a sand column, a silt column, and a clay column.<Supplemental Information<sAggregation MethodAggregation is the process by which a set of component attribute values is reduced to a single value to represent the map unit as a whole.A map unit is typically composed of one or more "components". A component is either some type of soil or some nonsoil entity, e.g., rock outcrop. The components in the map unit name represent the major soils within a map unit delineation. Minor components make up the balance of the map unit. Great differences in soil properties can occur between map unit components and within short distances. Minor components may be very different from the major components. Such differences could significantly affect use and management of the map unit. Minor components may or may not be documented in the database. The results of aggregation do not reflect the presence or absence of limitations of the components which are not listed in the database. An on-site investigation is required to identify the location of individual map unit components. For queries of soil properties, only major components are considered for Dominant Component (numeric) and Weighted Average aggregation methods (see below). Additionally, the aggregation method selected drives the available properties to be queried. For queries of soil interpretations, all components are condisered.For each of a map unit's components, a corresponding percent composition is recorded. A percent composition of 60 indicates that the corresponding component typically makes up approximately 60% of the map unit. Percent composition is a critical factor in some, but not all, aggregation methods.For the attribute being aggregated, the first step of the aggregation process is to derive one attribute value for each of a map unit's components. From this set of component attributes, the next step of the aggregation process derives a single value that represents the map unit as a whole. Once a single value for each map unit is derived, a thematic map for soil map units can be generated. Aggregation must be done because, on any soil map, map units are delineated but components are not.The aggregation method "Dominant Component" returns the attribute value associated with the component with the highest percent composition in the map unit. If more than one component shares the highest percent composition, the value of the first named component is returned.The aggregation method "Dominant Condition" first groups like attribute values for the components in a map unit. For each group, percent composition is set to the sum of the percent composition of all components participating in that group. These groups now represent "conditions" rather than components. The attribute value associated with the group with the highest cumulative percent composition is returned. If more than one group shares the highest cumulative percent composition, the value of the group having the first named component of the mapunit is returned.The aggregation method "Weighted Average" computes a weighted average value for all components in the map unit. Percent composition is the weighting factor. The result returned by this aggregation method represents a weighted average value of the corresponding attribute throughout the map unit.The aggregation method "Minimum or Maximum" returns either the lowest or highest attribute value among all components of the map unit, depending on the corresponding "tie-break" rule. In this case, the "tie-break" rule indicates whether the lowest or highest value among all components should be returned. For this aggregation method, percent composition ties cannot occur. The result may correspond to a map unit component of very minor extent. This aggregation method is appropriate for either numeric attributes or attributes with a ranked or logically ordered domain.

INFP, CRMD and UCL have developed a framework capable of analyzing the implications of natural hazards on transportation networks, also in a time-dependent manner. This is currently embedded into an ArcGIS toolbox entitled Network-risk, which has been successfully tested for Bucharest, contributing to an insightful evaluation of emergency intervention times for ambulances and firefighters, in the case of an earthquake. The files and the user manual allow a replication of our recent analysis in Toma-Danila et al. (2022) and a download of results (such as affected roads and unaccesible areas in Bucharest), in various formats. Some of the results are also presented in an ArcGIS Online app, called "Riscul seismic al Bucurestiului" (The seismic risk of Bucharest), available at https://tinyurl.com/yt32aeyx. In the files you can find: - the Bucharest road network used in the article; - facilities for Bucharest and Ilfov, such as hospitals, firestations, buildings with seismic risk or tramway lines accesible by emergency vehicles - results of the analysis: unaccesible roads and areas, service areas around facilities, closest facilities for representative points - Excel calculator for Z elevation from OpenStreetMap data - the user manual and a ArcGIS toolbox.

Main citation: - Toma-Danila D., Tiganescu A., D'Ayala D., Armas I., Sun L. (2022) Time-Dependent Framework for Analyzing Emergency Intervention Travel Times and Risk Implications due to Earthquakes. Bucharest Case Study. Frontiers in Earth Science, https://doi.org/10.3389/feart.2022.834052

Previous references: - Toma-Danila D., Armas I., Tiganescu A. (2020) Network-risk: an open GIS toolbox for estimating the implications of transportation network damage due to natural hazards, tested for Bucharest, Romania. Natural Hazards and Earth System Sciences, 20(5): 1421-1439, https://doi.org/10.5194/nhess-20-1421-2020 - Toma-Danila D. (2018) A GIS framework for evaluating the implications of urban road network failure due to earthquakes: Bucharest (Romania) case study. Natural Hazards, 93, 97-111, https://link.springer.com/article/10.1007/s11069-017-3069-y

The DNR bluff mapping tool is intended to help local governments identify bluffs in the administration of shoreland and river-related ordinances that regulate placement of structures, vegetation management and land alteration activities in bluff areas. The tool is intended to show the general locations of bluffs. A field survey is necessary to specifically locate the toe and top of bluffs and bluff impact zones for building purposes.

Technical Requirements
The user will need the following to run this tool:
System Requirements:
- ArcGIS 10.x
- Spatial Analyst
Input Data Requirements:
- LiDAR or similar data that can be used or converted into a DEM for elevation data (You can download 1-meter and 3-meter DEMs from MnTOPO: http://arcgis.dnr.state.mn.us/maps/mntopo )

For step-by-step instructions on how to use the tool, please view MN DNR Bluff Mapping Tool Guidance.pdf

Introduction

Geographical scale, in terms of spatial extent, provide a basis for other branches of science. This dataset contains newly proposed geographical and geological GIS boundaries for the Pan-Tibetan Highlands (new proposed name for the High Mountain Asia), based on geological and geomorphological features. This region comprises the Tibetan Plateau and three adjacent mountain regions: the Himalaya, Hengduan Mountains and Mountains of Central Asia, and boundaries are also given for each subregion individually. The dataset will benefit quantitative spatial analysis by providing a well-defined geographical scale for other branches of research, aiding cross-disciplinary comparisons and synthesis, as well as reproducibility of research results.

The dataset comprises three subsets, and we provide three data formats (.shp, .geojson and .kmz) for each of them. Shapefile format (.shp) was generated in ArcGIS Pro, and the other two were converted from shapefile, the conversion steps refer to 'Data processing' section below. The following is a description of the three subsets:

(1) The GIS boundaries we newly defined of the Pan-Tibetan Highlands and its four constituent sub-regions, i.e. the Tibetan Plateau, Himalaya, Hengduan Mountains and the Mountains of Central Asia. All files are placed in the "Pan-Tibetan Highlands (Liu et al._2022)" folder.

(2) We also provide GIS boundaries that were applied by other studies (cited in Fig. 3 of our work) in the folder "Tibetan Plateau and adjacent mountains (Others’ definitions)". If these data is used, please cite the relevent paper accrodingly. In addition, it is worthy to note that the GIS boundaries of Hengduan Mountains (Li et al. 1987a) and Mountains of Central Asia (Foggin et al. 2021) were newly generated in our study using Georeferencing toolbox in ArcGIS Pro.

(3) Geological assemblages and characters of the Pan-Tibetan Highlands, including Cratons and micro-continental blocks (Fig. S1), plus sutures, faults and thrusts (Fig. 4), are placed in the "Pan-Tibetan Highlands (geological files)" folder.

Note: High Mountain Asia: The name ‘High Mountain Asia’ is the only direct synonym of Pan-Tibetan Highlands, but this term is both grammatically awkward and somewhat misleading, and hence the term ‘Pan-Tibetan Highlands’ is here proposed to replace it. Third Pole: The first use of the term ‘Third Pole’ was in reference to the Himalaya by Kurz & Montandon (1933), but the usage was subsequently broadened to the Tibetan Plateau or the whole of the Pan-Tibetan Highlands. The mainstream scientific literature refer the ‘Third Pole’ to the region encompassing the Tibetan Plateau, Himalaya, Hengduan Mountains, Karakoram, Hindu Kush and Pamir. This definition was surpported by geological strcture (Main Pamir Thrust) in the western part, and generally overlaps with the ‘Tibetan Plateau’ sensu lato defined by some previous studies, but is more specific.

More discussion and reference about names please refer to the paper. The figures (Figs. 3, 4, S1) mentioned above were attached in the end of this document.

Data processing

We provide three data formats. Conversion of shapefile data to kmz format was done in ArcGIS Pro. We used the Layer to KML tool in Conversion Toolbox to convert the shapefile to kmz format. Conversion of shapefile data to geojson format was done in R. We read the data using the shapefile function of the raster package, and wrote it as a geojson file using the geojson_write function in the geojsonio package.

Version

Version 2022.1.

Acknowledgements

This study was supported by the Strategic Priority Research Program of Chinese Academy of Sciences (XDB31010000), the National Natural Science Foundation of China (41971071), the Key Research Program of Frontier Sciences, CAS (ZDBS-LY-7001). We are grateful to our coauthors insightful discussion and comments. We also want to thank professors Jed Kaplan, Yin An, Dai Erfu, Zhang Guoqing, Peter Cawood, Tobias Bolch and Marc Foggin for suggestions and providing GIS files.

Citation

Liu, J., Milne, R. I., Zhu, G. F., Spicer, R. A., Wambulwa, M. C., Wu, Z. Y., Li, D. Z. (2022). Name and scale matters: Clarifying the geography of Tibetan Plateau and adjacent mountain regions. Global and Planetary Change, In revision

Jie Liu & Guangfu Zhu. (2022). Geographical and geological GIS boundaries of the Tibetan Plateau and adjacent mountain regions (Version 2022.1). https://doi.org/10.5281/zenodo.6432940

Contacts

Dr. Jie LIU: E-mail: liujie@mail.kib.ac.cn;

Mr. Guangfu ZHU: zhuguangfu@mail.kib.ac.cn

Institution: Kunming Institute of Botany, Chinese Academy of Sciences

Address: 132# Lanhei Road, Heilongtan, Kunming 650201, Yunnan, China

Copyright

This dataset is available under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0).