WEBVTT Kind: captions Language: en 00:00:07.200 --> 00:00:11.666 In this video we will go through all parts of the geologic map GIS template 00:00:11.666 --> 00:00:13.532 provided by Astrogeology 00:00:13.533 --> 00:00:18.199 to NASA funded mappers producing USGS Scientific Investigation Maps, 00:00:18.200 --> 00:00:25.500 known as some series maps provided brief explanation of how they work together to support the entire mapping process. 00:00:25.500 --> 00:00:29.200 The actual contents of each project are based on the specifications 00:00:29.200 --> 00:00:36.000 of the Mapping Coordinators letter of support for that map, but a generic version of the package is a also available for download 00:00:36.000 --> 00:00:42.166 at the Planetary Geologic Mapping program Guidelines website. 00:00:42.166 --> 00:00:47.599 The ReadMe is a text file stored in the root of the project directory the details all the information 00:00:47.600 --> 00:00:52.300 contained in that project and should be the first place mappers look for clarification. 00:00:52.300 --> 00:01:01.066 It also includes basic guidelines for using the data and contact information for technical support. 00:01:01.066 --> 00:01:08.099 The first folder labeled "CoordinateSystems" contains one or more projection files that define the spatial reference of the project. 00:01:08.100 --> 00:01:15.033 A projection file is simply a text file with a *.PRJ extension that defines a spatial domain (or 00:01:15.033 --> 00:01:18.766 body), projection type, and parameters of the projection. 00:01:18.766 --> 00:01:26.432 These coordinate systems are already saved in the map document and written to all spatial data in the 00:01:26.433 --> 00:01:32.499 project, but can be used for recreating the map or sharing with collaborators. 00:01:32.500 --> 00:01:37.566 Layer files are used to save the symbology of a layer outside of the map document. 00:01:37.566 --> 00:01:39.832 They do not contain any of the source data 00:01:39.833 --> 00:01:43.233 and only work with ArcMap MXDs. 00:01:43.233 --> 00:01:50.966 The layer files provided in the template are used to set the symbology of the empty feature classes, which include geologic contacts, 00:01:50.966 --> 00:01:54.899 linear features, location features, and surface features 00:01:54.900 --> 00:02:00.400 based on FGDC standard symbology. 00:02:00.400 --> 00:02:04.433 The Rasters folder contains all base maps and key supplemental data 00:02:04.433 --> 00:02:07.099 approved for use in the mapping process. 00:02:07.100 --> 00:02:11.633 They are clipped tothe map boundary and projected in the map coordinate system. This 00:02:11.633 --> 00:02:26.333 folder also includes the ancillary files that contain the spatial reference, statistics, overviews and metadata associated with each image. 00:02:26.333 --> 00:02:36.399 The Working folder is where all mapping data are stored and we recommend keeping this as the repository for all in-progress work, notes and 00:02:36.400 --> 00:02:43.933 graphics related to the GIS. It is important to keep this workspace as well organized as possible since 00:02:43.933 --> 00:02:48.699 intermediate and derivative files can quickly become cluttered. 00:02:48.700 --> 00:02:51.900 The Shapefiles folder is not included in the generic template, 00:02:51.900 --> 00:03:00.766 but is included for prepared projects, and typically just contains a shapefile of the map boundary, 00:03:00.766 --> 00:03:06.066 which can be useful for sharing, clipping in re-creating maps. 00:03:06.066 --> 00:03:11.066 The geodatabase contains all mapped features, and mosaic dataset if there is one. 00:03:11.066 --> 00:03:17.799 Geodatabases allow users to leverage the most capability in a GIS environment, some of which will be covered here. 00:03:17.800 --> 00:03:32.200 For more information on using a file geodatabase see our other tutorials or visit Esri's website for detailed documentation and exercises. 00:03:32.200 --> 00:03:40.500 Within the geodatabase is a feature dataset which acts like a sub-folder for all data that share a common spatial reference and tolerance. 00:03:40.500 --> 00:03:50.366 This means that any feature class imported or exported from the feature dataset will automatically be projected to that coordinate 00:03:50.366 --> 00:03:56.699 system, which can be accessed or modified through the feature dataset properties window. 00:03:56.700 --> 00:04:01.566 Stored in that feature dataset are the feature classes which store the actual mapping data. 00:04:01.566 --> 00:04:05.299 We recommend that you output derivative layers to the same space, 00:04:05.300 --> 00:04:13.066 and using naming convention that supports version control. 00:04:13.066 --> 00:04:21.199 As mentioned, there a number of advantages to managing your spatial data in a geodatabase, and one of the most helpful is the attribute domain. 00:04:21.200 --> 00:04:23.800 Attribute domains are predefined values 00:04:23.800 --> 00:04:30.233 which can be text, numeric ranges or dates, that are available as drop-down field attributes. 00:04:30.233 --> 00:04:40.866 The template geodatabase comes pre-populated with coded domains for all feature types used by the layer files and feature classes, greatly 00:04:40.866 --> 00:04:46.299 reducing the number of errors and overall time when entering attributes. 00:04:46.300 --> 00:04:53.100 All prepared projects include MXDs saved in versions 10.1, 0.3 and 10.4. 00:04:53.100 --> 00:04:57.333 In the event the map is corrupted it may be recovered from an earlier version 00:04:57.333 --> 00:05:03.299 or rebuilt using the elements covered here. 00:05:03.300 --> 00:05:14.100 Thank you for viewing; we hope this video has been helpful. For more videos as well as tools and resources for planetary GIS visit the MRCTR 00:05:14.100 --> 00:05:19.966 GIS Lab hosted by the USGS Astrogeology Science Center in Flagstaff, Arizona.