Create a geodatabase project

At its most basic level, the geodatabase is a container for storing spatial and attribute data and the relationships that exist among them. In a geodatabase, features and their associated attributes can be structured to work together as an integrated system using rules, relationships, and topological associations. In other words, the geodatabase allows you to model the real world in a simple or complex manner as needs dictate.

Create an ArcGIS Pro project for a geodatabase

The organization and structure of a geodatabase are generally referred to as its schema. Before developing a geodatabase schema for use by Salzburg tourism agencies, it would be useful to investigate a generic basemap schema that may be deployed by organizations and agencies when requirements call for them to manage a specific collection of base or source data.

While there are several methods for creating a geodatabase, for this lesson, you'll start by creating an ArcGIS Pro project from a template that includes a geodatabase. When you create a new project, a new file geodatabase is automatically created and set as the default geodatabase. This geodatabase will store the data used by the Salzburg tourism agencies to support their mapping efforts.

Note:

The current trend is for cities, organizations, and agencies to maintain their own unique or proprietary data and supplement it by leveraging the use of published and publicly available basemaps, map services, and other authoritative data sources like those available in ArcGIS Living Atlas of the World.

  1. Go to the Get Started with Geodatabases group.

    Get Started with Geodatabases group

  2. Scroll down until you see the Sample Basemap GDB Schema thumbnail. Click Download to download the zip file.

    Sample Basemap GDB Schema

  3. Click the SalzburgData thumbnail to download it.

    SalzburgData thumbnail

  4. Extract the contents of the files to a location of your choice (for example, C:\Salzburg).
  5. Open ArcGIS Pro.
    Note:

    If you don't have ArcGIS Pro or an ArcGIS account, you can sign up for an ArcGIS free trial.

    ArcGIS Pro opens to the splash screen.

  6. Click Settings and choose Options.

    The Options pane appears.

  7. In the Options pane, click Metadata.
  8. For Metadata style, choose FGDC CSDGM Metadata.

    Metadata style option

    The ArcGIS platform defaults to a basic metadata style known as Item Description, but you may update and modify the style to one of various additional styles. One such style is the FGDC CSDGM Metadata style that allows you to view and edit full metadata and is a well-known metadata content standard that has been used in North America and around the world for many years.

  9. Click OK.
  10. Click the Back button to return to or open your project.
  11. If necessary, sign in using your licensed ArcGIS account.
  12. Under New, click Catalog.

    Catalog template

    ArcGIS Pro provides a few blank project templates to help you get started.

    • To build a 2D map, select the Map template.
    • To create a 3D global scene, select the Global Scene template.
    • To start with a 3D local scene, select the Local Scene template.
    • To start with the Catalog view, select the Catalog template.

    If data management is your primary focus, consider pinning this project to the start page or opening it automatically when you start ArcGIS Pro. Since your primary focus for this lesson will be on data management, the Catalog template is a good choice.

  13. For Name, type SalzburgGeodatabase.
  14. For Location, browse to and select the location of your downloaded project content (for example, C:\Salzburg).

    It is often helpful to create a dedicated folder for your project. Each new project includes a project file (.aprx), a default geodatabase, and a toolbox. Organizing these together in a single folder makes it easier to find, share, and store your project and data.

  15. Ensure that Create a new folder for this project is checked and click OK.

    Create a New Project window

    The project opens and displays a Contents pane and the Catalog view.

    The Contents pane and the Catalog view

    The Catalog view allows you to access all items associated with a specific project in one place, whether they are available from a local or network computer, ArcGIS Online, or an ArcGIS Enterprise portal, as you build your project by adding maps, scenes, layouts, connections to folders, and geodatabases. From the ribbon, you can open several Catalog views and use them to compare the contents of databases or folders, compare metadata for two items, copy style items from one style to another, and so on.

  16. On the ribbon, on the View tab, in the Windows group, click Catalog Pane.

    The Catalog pane appears.

    Catalog Pane button

    Note:

    The Catalog pane and the Catalog view are similar but designed for different tasks. Both the Catalog pane and the Catalog view can be open at the same time, but they operate independently. In both the pane and the view, you can manage and browse data. As you generate new items, they are categorized by type and appear on the project tab in the Catalog pane as well as in the project collection in the Catalog view.

    Think of the Catalog pane as a light version of the Catalog view that offers access to project-related components via tabs for portal, favorites, and history.

    Catalog view and Catalog pane comparison

    If the Catalog pane is good for quick access, the Catalog view is better for more in-depth data management tasks and has associated ribbon tabs with management functionality. In addition, the Catalog view displays item details in columns and gives access to metadata.

    In the next lessons, you'll focus on using the Catalog view and its associated Contents pane.

  17. Close the Catalog pane.
  18. In the Contents pane, click and expand Databases.

    SalzburgGeodatabase.gdb was already created with the project. Before you explore the Catalog view, you'll create a folder connection to easily access your lesson resources.

  19. In the Contents pane, click Folders.
  20. On the ribbon, on the Catalog tab, in the Create group, click Add and choose Add Folder Connection.

    Add button

  21. In the Add Folder Connection pane, locate your extracted data folder (for example, C:\Salzburg) and click OK.

    A folder connection is a shortcut to locating important data and project-related materials.

  22. Save the project.

In this lesson, you generated a project to support populating a geodatabase and modified the project default metadata style from Item Description to the FGDC CSDGM Metadata style. Next, you'll evaluate various data sources for inclusion in your geodatabase.


Evaluate data sources

In this lesson, you'll evaluate potential data sources that will be migrated to your Salzburg geodatabase. Typical data quality criteria to note when evaluating a data source are relevance for usage; geographic extent; projection; currency; data and metadata standards; data lineage; spatial operations performed on data, including sampling, processing, modeling and analysis, accuracy, and completeness; and relevant attributes.

Evaluate data sources

Next, you'll evaluate potential data sources that will be migrated to the Salzburg geodatabase. These data sources include shapefiles and KMZ files.

  1. If necessary, open your project.
  2. In the Contents pane, for the Folders connection, expand the City_of_Salzburg subfolder.

    The Catalog view updates to display the collection of shapefiles representing data for the city of Salzburg. Additional details about these shapefiles are listed in the Name, Type, and Date columns. To sort content within any of these columns, select the column header. In addition to item details, the Catalog view also gives direct access to information that describes an item, known as metadata.

    Item details

    The City_of_Salzburg folder contains 29 shapefiles that would be useful to tourism agencies to add as layers to use in updating maps and within new apps. Before deciding which data sources to keep or which to replace with data from other sources, you should access and review each potential data source.

  3. In the Catalog view, click BicyclePaths.shp.

    The item type is displayed and the Metadata tab updates to display detailed information for the shapefile.

    Shapefile metadata

    The metadata includes information about use limitations, credits, and the spatial reference.

    Review limitations and spatial referencing.

    The spatial reference is defined as follows:

    • Geographic coordinate reference—GCS_MGI
    • Projection—MGI_Austria_GK_M31

    Metadata is vital and important in accessing the usefulness and relevance of a data source when developing a geodatabase. Read more about viewing and editing metadata.

  4. Click the Geography tab to display and review the spatial features contained in the shapefile. If necessary, pan and zoom the map.

    Geography tab

  5. Click the Table tab to display the attribute fields and values for bicycle path features.

    Table tab

    While reviewing the metadata for the Bicycle Paths shapefile, it is obvious that metadata forms an important part in documenting your content and the project items you create and use. These may include maps, projects, geoprocessing models, and geodatabase datasets.

    Note:

    Metadata is saved with the item it describes, in the geodatabase for geodatabase items, in the project for project items, on the file system for file-based items, and so on. Once created, metadata is copied, moved, and deleted with the item when it's managed by ArcGIS.

  6. Review the Metadata, Geography, and Table tabs for Museums.shp.

    These are locations that are often visited by tourists, and this layer is important to maintain and keep up to date. The spatial reference for this data source is defined as follows:

    • Geographic coordinate reference—GCS_MGI
    • Projection—MGI_Austria_GK_M31

    The table for this data source contains attribute fields that include the location name and address, which will both be useful in tourism applications.

  7. Review the metadata for ReligiousMonuments.shp.

    This metadata appears to be fairly complete, but notice when you review the geography and the table that the shapefile contains no features. As a result, this data source may be rejected and not used.

  8. In the Contents pane, under Folders, click the kmz-files subfolder.

    The folder contains three KMZ files that would be useful for tourism agencies. A KMZ file is a compressed Keyhole Markup Language (KML) file that can be displayed by any KML client, including ArcGIS Pro.

    Folder for KMZ files

    Your folder structure may vary based on the location where you unzipped your downloaded data.

    Note:

    KML is a common format for sharing geographic data with non-GIS users as it can be easily delivered on the internet and viewed in a number of free applications. KML files have an XML-based format and can have either a .kml or .kmz (for compressed or zipped KML files) file extension. You can use either extension in ArcGIS Pro.

  9. In the Catalog view, click Kunstwerke_mit_Audiotext.kmz.

    The features in this KML file represent the location of several significant open-air and indoor art installations that may be searched and visited by tourists interested in the work of specific artists.

    Note:

    A single KML file can be composed of point, line, polygon features, and raster imagery, or a combination of these. KML can also contain related content such as graphics, pictures, attributes, and HTML, whereas datasets in ArcGIS are typically seen as separate and homogeneous elements (for example, point feature classes can only contain points; rasters can only contain cells or pixels and not features).

  10. Review the metadata for Kunstwerke_mit_Audiotext.kmz.

    KMZ metadata

    In this case, the KMZ has no useful metadata; however, by default, KMZ files are intended to be used via web applications and thus use WGS84 as their coordinate system, so some information is known about the data source.

  11. Review the geography for Kunstwerke_mit_Audiotext.kmz.

    KMZ file content

    The features displayed do not scale well and appear faded as you zoom in and out on the map. This is because the KMZ file includes its symbology and other layer properties (such as pop-up information) in the file.

  12. Review the table for Kunstwerke_mit_Audiotext.kmz.

    Because you are currently displaying and exploring the unconverted KMZ content as a layer, you will not be able to access any tabular information associated to points. In fact, KMZ uses a tag-based structure with nested elements and attributes and is based on the XML standard. To edit and modify the data, you would need to translate the KMZ file into a feature class inside a geodatabase to access the attributes.

  13. In the Contents pane, under Folders, expand the OpenStreetMap_Salzburg subfolder.

    This folder contains a collection of free OpenStreetMap data for Salzburg in shapefile format that would be useful for building tourism maps and apps. The data is collected and built by volunteers and released with an Open Content License. The OpenStreetMap License allows free access to map images and all underlying map data, and the project aims to promote new and interesting uses of the data. Review the following topic for a description of OSM Map Features.

  14. In the Catalog view, click OSM_Salzburg_Amenities.shp. On the Metadata tab, review the spatial reference information.

    Amenities spatial referencing information

    This data source has comprehensive metadata that makes it useful for your purposes. However, the spatial references has its geographic coordinate reference set to GCS_WGS_1984 and its projection defined as WGS_1984_Web_Mercator_Auxiliary_Sphere. This is not a desirable projection if you want to accurately determine distances, measure areas, and compare shapes.

  15. On your own, explore and review several additional OpenStreetMap data sources. Be sure to check if these sources have the same spatial referencing.
  16. Save the project.

Next, you'll import the geodatabase schema for a generic basemap using an XML Interchange file. Using the basemap, you'll explore geodatabase objects before updating the metadata for your Salzburg geodatabase in preparation for migrating data sources from their current format and spatial reference into a suitable spatial reference for use in tourism maps and apps.


Create a geodatabase schema

The geodatabase storage model is based on a series of relational database concepts and uses an underlying database management system (DBMS). The DBMS provides the storage structure, indexing, backup and rollback mechanisms and security model. DBMS tables and well-defined attribute types are used to store the schema, rule base, and spatial attribute data for each geographic dataset. This approach provides a formal model for storing and working with your data.

Review geodatabase objects

In this lesson, you'll start by reviewing the schema for a generic basemap to gain insight into geodatabase components such as feature classes, feature datasets, and stand-alone tables that are used to organize and manage data. Then, you'll convert and import various datasets to create and update the schema of your Salzburg geodatabase. See What is a geodatabase? and Fundamentals of the geodatabase to learn more.

You'll start by importing the schema of a basemap geodatabase from an XML Interchange file.

  1. If necessary, open your project.
  2. In the Contents pane, click Databases.

    You already have the default SalzburgGeodatabase.gdb generated from when you created the project. You'll populate this database with your Salzburg source data. In the next step, however, you'll create an additional geodatabase to explore geodatabase components.

  3. On the ribbon, on the Databases tab, in the Project group, click New File Geodatabase.

    New File Geodatabase button

  4. In the New File Geodatabase pane, for Name, type SampleBaseMapGDB.gdb. Ensure you create the geodatabase in the SalzburgGeodatabase folder.

    New File Geodatabase window

    Next, you'll import a basemap geodatabase schema from an XML document into SampleBaseMapGDB.gdb. This is not always necessary, but in this case you need to review a common geodatabase design and geodatabase objects and also explore how XML workspace documents can be used to share your own geodatabase schemas in the future.

  5. In the Contents pane, click SampleBaseMapGDB.gdb.
  6. On the ribbon, on the Catalog tab, in the Create group, click Import and choose XML Workspace Document.

    XML Workspace Document option

  7. In the Import XML Workspace Document geoprocessing tool, for Import File, click the Browse button.
  8. In the Import File pane, browse to and select SampleBasemapGDB.xml and click OK.

    Import File window

  9. In the Import XML Workspace Document geoprocessing tool, for Import Options, choose Import schema only and click Run.

    Import XML Workspace Document tool parameters

  10. In the Contents pane, right-click SampleBaseMapGDB.gdb and click Refresh.
  11. In the Catalog view, review the SampleBaseMapGDB.gdb contents.

    Geodatabases are made up of a collection of system tables plus user data. User data can be stored in the following types of datasets:

    • Feature class
    • Feature dataset
    • Mosaic dataset
    • Raster dataset
    • Table (nonspatial)

    In addition, feature classes and tables can include subtypes and have domains associated to them. You may also notice attachments and relationship classes in the geodatabase.

    Imported geodatabase objects

    In this geodatabase, feature classes are organized into feature datasets that group feature classes thematically, such as Administrative and Transportation. This geodatabase also includes a geoprocessing toolbox that may be used to organize a series of user-created geoprocessing tools, scripts, and models.

    Feature datasets can contain feature classes as well as the following types of datasets:

    • Geometric networks (read-only in ArcGIS Pro)
    • Network datasets (requires ArcGIS Network Analyst extension)
    • Terrains (requires ArcGIS 3D Analyst extension)
    • Topologies

  12. Expand and review the feature classes organized in the Administrative feature dataset.

    Since this is a basemap geodatabase schema, the Administrative feature dataset contains several line and polygon feature classes designed to store and maintain boundary lines and polygons for administrative areas.

    Administrative feature dataset

  13. In the Contents pane, click SampleBaseMapGDB.gdb.

    The Catalog pane contains the PointsOfInterest feature class, which is a stand-alone feature class that is not organized and maintained in a feature dataset.

    PointsOfInterest feature class

    The PointsOfInterest feature class is noteworthy because it has an associated attachment table, PointsOfInterest__ATTACH, capable of containing images and related documents and links for each point in the feature class. Attachment functionality provides a powerful way to associate nongeographic data with your geographic information using, in this case, a relationship class named PointsOfInterest__ATTACHREL to maintain a persistent link between the points and their related attachments. You can learn more about attachments.

  14. In SampleBaseMapGDB.gdb, review Slopemap and OrthoPhotos.

    Both of these geodatabase objects represent raster data storage and management methods.

    Geodatabase rasters

    The Slopemap object represents a raster dataset that is a single raster or image data layer. Typically, a raster dataset refers to any raster format supported by ArcGIS Pro that can be stored in a geodatabase. The Orthophoto object represents a mosaic dataset used to manage, display, serve, and share a collection of raster data.

  15. In SampleBaseMapGDB.gdb, locate HistoricSitesDescriptions.

    This object represents a nonspatial geodatabase table that can contain descriptions, codes, and other related data that can be associated to spatial features as needed.

    Note:

    You imported the XML workspace document into SampleBaseMapGDB.gdb to explore and review a typical basemap design. You'll not be using this geodatabase again in the lesson.

  16. In the Contents pane, expand Databases and click SampleBaseMapGDB.gdb.
  17. On the ribbon, on the Catalog tab, in the Organize group, click Remove.
    Note:

    Removing the geodatabase only removes the selected item from the project. All project references to the item are removed, but the item remains on disk.

    Now that you have reviewed the sample basemap geodatabase schema, you are ready to proceed with populating your own tourism geodatabase.

Document and prepare the Salzburg geodatabase

In preparation for populating the Salzburg geodatabase, you'll edit and update your geodatabase metadata.

  1. In the Contents pane, right-click SalzburgGeodatabase.gdb and choose Edit Metadata.

    Edit Metadata option

    The metadata content displays in the details pane in the Catalog view. The Contents pane updates to display metadata categories. For SalzburgGeodatabase.gdb, three metadata groups are defined: Overview, Metadata, and Resources. You can learn more about editing metadata.

    Metadata groups

    In the Catalog view, metadata is displayed in a details pane.

    Geodatabase metadata

    Next, you'll populate the item description for overview items.

  2. In the Catalog view, in the details pane, update the following information:

    • For Title, type Salzburg Tourism Geodatabase.
    • For Tags, type Salzburg, Austria, Visitor map, Tourism, Tourist, Visitor guide, Food, Activities, Attendees, Places to visit, Places to eat, Bike Routes, Ski Resorts, Museums, Art, Castles, Cathedrals.
    • For Summary, type Collection of data for the city and surrounding areas of Salzburg Austria.
    • For Description (Abstract), type Geodatabase to store and manage a collection of spatial and attribute data that can be used by tourism agencies in the city of Salzburg, Austria to develop updated web maps and apps.

  3. For Credits, type the following information:

    • STADT: SALZBURG https://maps.stadt-salzburg.at/
    • National Mapping Agency - Federal Office for Metrology and Surveying (BEV) https://www.bev.gv.at
    • Austrian Map online
    • Land Salzburg - Open Government Data (OGD) - https://service.salzburg.gv.at/ogd/client/ and https://www.salzburg.gv.at/sagis/
    • Austrian OGD basemap https://www.basemap.at/index_en.html

  4. Set Appropriate Scale Range to 1:50,000 to 1:5,000.

    Scale range

  5. Click the add button to display and update the Bounding Box information. Add the following information:

    West

    12.058153

    East

    14.008495

    South

    46.938376

    North

    48.042424

    Bounding box values are useful for published layers and maps, as web applications display at the box extent and not the whole world.

    Note:

    When you author or update metadata content for an ArcGIS item, record the information that is important for your organization to know about that item. This might include how accurate and recent the item is, restrictions on using and sharing the item, important processes in its life cycle such as generalizing features, and so on.

  6. On the ribbon, on the Metadata tab, in the Manage Metadata group, click Save.
  7. Close the metadata editor pane.
  8. In the Contents pane, right-click SalzburgGeodatabase.gdb and choose View Metadata.

    The Catalog view displays the updated metadata for your Salzburg Tourism geodatabase.

    Geodatabase metadata

    Note:

    When care is taken to provide good descriptive information, you can find items with a search and evaluate which item in your search results is the correct one to use. You can improve communication and have confidence in making decisions based on an item's geospatial information. You can archive projects knowing they can be recovered, used, and evaluated in the future.

  9. Save the project.

Next, you'll start to migrate several data sources from the City_of_Salzburg, KMZ files, and OpenStreetMap_Salzburg folders into SalzburgGeodatabase.gdb.


Populate the geodatabase

Researching current tourism maps and online information for the city of Salzburg gives a good indication of which data themes various tourism agencies and private companies need to best serve visitors. These offer you a good guideline for what data to assimilate into your geodatabase, keeping in mind that most of the feature classes you build and later symbolize will most likely be displayed on current basemap layers published in ArcGIS Living Atlas of the World and other sources. Your feature classes will complement and supplement existing base data and serve to add value to the interactive web maps and apps that agencies may generate and publish.

The most popular maps and data used for Salzburg tourism include the following items:

  • Detailed city map showing streets, pedestrian areas, and buildings
  • Sightseeing map with tourist highlights
  • Map with locations for markets and exhibitions
  • Bus and rail stops and routes
  • Creative walks—Architecture, museums, art, galleries, churches
  • Foot and cycling paths
  • Beer routesIncluding breweries and taverns
  • City and nature hiking trails
  • Hotel maps

Create feature datasets

While working with your geodatabase, you can create empty feature datasets directly from the geodatabase.You'll start by creating feature datasets for the following four data themes:

  • City_Attractions
  • Transportation
  • Scenic_Attractions
  • Trails

  1. If necessary, open your project.
  2. In the Contents pane, right-click SalzburgGeodatabase.gdb, point to New, and click Feature Dataset.

    The geoprocessing tool corresponding to the dataset type you have selected opens.

    Feature Dataset option

  3. In the Create Feature Dataset geoprocessing tool, for Feature Dataset Name, type City_Attractions.
  4. For Coordinate Systems, click the Select Coordinate System button.

    One of the simplest ways to define the coordinate system for a geodatabase object is to import or clone it from a current data source that has the coordinate system correctly defined.

  5. In the Coordinate System pane, click the Add Coordinate System button and choose Import Coordinate System.

    Import Coordinate System option

  6. In the Import coordinate system pane, browse to the City_of_Salzburg folder. Select BicyclePaths.shp and click OK.

    Import coordinate system window

  7. In the XY Coordinate Systems Available list, confirm MGI Austria GK M31 is selected and click OK.

    Coordinate System window

  8. In the Create Feature Dataset tool, verify the parameters and click Run.

    Create Feature Dataset tool parameters

    Note:

    In Austria, the official projected coordinate system used for cadastral data is MGI Austria GK Central, which is a Transverse Mercator projection. However, individual Austrian states such as the one that includes the city of Salzburg apply a shift (false easting) to avoid negative values and therefore use a custom coordinate system known as MGI Austria GK M31.

  9. In the Catalog view, right-click City_Attractions and choose Edit Metadata.
  10. In the Details pane, in the Catalog view, make the following updates to the metadata:

    • For Title, type Salzburg City Attractions.
    • For Tags, type Salzburg, Austria, City Attractions.
    • For Summary, type Collection of Salzburg visitor attractions.
    • For Description (Abstract), type Location of various city sites commonly visited by tourists in Salzburg Austria.
    • For Credits, type the following information:
      • STADT: SALZBURG https://maps.stadt-salzburg.at/
      • National Mapping Agency - Federal Office for Metrology and Surveying (BEV) https://www.bev.gv.at
      • Austrian Map online
      • Land Salzburg - Open Government Data (OGD) - https://service.salzburg.gv.at/ogd/client/ and https://www.salzburg.gv.at/sagis/
      • Austrian OGD basemap https://www.basemap.at/index_en.html
    • Set Appropriate Scale Range to City (1:50,000) to Buildings (1:5,000).
    • For Bounding Box, set the following values:

      West

      12.058153

      East

      14.008495

      South

      46.938376

      North

      48.042424

  11. On the ribbon, on the Metadata tab, in the Manage Metadata group, click Save.
  12. In the Catalog view, close the City_Attractions tab.
  13. In the Contents pane, right-click City_Attractions and choose View Metadata.

    Feature dataset metadata

  14. In the Contents pane, click SalzburgGeodatabase.gdb.
  15. On the ribbon, on the Catalog tab, in the Create group, click New and choose Feature Dataset.

    New feature dataset

  16. In the Create Feature Dataset geoprocessing tool, set the following parameters:

    • For Output Geodatabase, choose C:\Salzburg\SalzburgGeodatabase\SalzburgGeodatabase.gdb.
    • For Feature Dataset Name, type Scenic_Attractions.
    • For Coordinate System, choose MGI Austria GK M31.

  17. Using the same workflow and parameters, create additional feature datasets for the following data types:

    • Transportation
    • Trails

  18. In the Contents pane, expand SalzburgGeodatabase.gdb and verify the creation of the four feature datasets.
    Feature datasets
  19. Optionally, update the metadata for the additional feature datasets.

Import a single shapefile

You can add data to a geodatabase by importing and converting from source data formats into feature classes. First, you'll look at migrating shapefiles into the geodatabase. A shapefile is a legacy data format that is still popular in the GIS community, but it has several limitations that hinder its use as an efficient data storage type. It is similar to a feature class and therefore directly maps to the geodatabase as a single feature class when you migrate it to the geodatabase.

  1. In the Catalog pane, for SalzburgGeodatabase.gdb, right-click the City_Attractions feature dataset, point to Import, and choose Feature Class.

    Import feature class option

    You can also use the Import Feature Class tool located on the ribbon on the Catalog tab, in the Create group.

    Import feature class option from the Catalog tab

    The Feature Class to Feature Class geoprocessing tool opens. This tool allows you to select a single data source to import into the geodatabase. In addition, you can rename the output feature class and choose which source attribute fields to retain or remove from the source data.

  2. In the Feature Class to Feature Class geoprocessing tool, for Input Features, browse to the OpenStreetMap_Salzburg folder and choose OSM_Salzburg_HistoricSites.shp.
  3. Confirm that Output Location is set to City_Attractions.
  4. For Output Feature Class, type HistoricSites.
    Note:

    In the Field Map section, the Output Fields parameter displays a list of attribute fields that will be copied to the output dataset. To delete a field, select the field and choose Remove. To remove multiple fields, press Shift+Ctrl to select the fields and choose Remove.

  5. In the Output Fields list, keep the following fields: HISTORIC, NAME, ADDR_HOUSE, ADDR_HOU00, ADDR_STREE, ADDR_CITY, ADDR_STATE, ADDR_POSTC and ADDR_PLACE. Remove all the others.
  6. Verify the parameters and click Run.

    Feature Class to Feature Class tool parameters

    You are not required to define the spatial referencing for the HistoricSites feature class. The source shapefile has WGS_1984_Web_Mercator_Auxiliary_Sphere defined as its coordinate system. Because you already defined the coordinate system of the target feature dataset, the source data is automatically reprojected to match the coordinate system of the target feature dataset.

  7. In the Contents pane, right-click City_Attractions and choose Refresh.
  8. In the Catalog view, click HistoricSites.

    The Metadata tab appears. The original shapefile metadata has been copied to your geodatabase feature class.

    Note:

    If the Catalog view does not display your feature classes, click Show/Hide Details button in the upper right corner of the Catalog view.

    Feature class metadata

  9. In the Catalog view, right-click HistoricSites and choose Edit Metadata.

    Edit Metadata option

  10. In the metadata editor pane, update the following information:

    • For Title, type Salzburg Historic Sites.
    • For Tags, type Salzburg, Austria, Historic sites.
    • For Summary, type Point features of historic sites in Salzburg Austria.
    • For Credits and Use Limitation, leave the default text, as these fields are populated from source metadata.
    • For Description (Abstract), type Location of historic sites in Salzburg Austria.
    • Set Appropriate Scale Range City (1:50,000) to Buildings (1:5,000).

    Edited feature class metadata

  11. On the ribbon, on the Metadata tab, in the Manage Metadata group, click Save.
  12. Close the metadata editor pane.

Export or import multiple feature classes to a geodatabase

Exporting or importing a single shapefile is useful if you need to convert only selected features and choose specific attribute fields to be copied to the output feature class. Sometimes it is necessary to batch convert multiple sources for quick conversion and spend time later removing unnecessary attribute fields.

  1. In the Contents pane, click the City_of_Salzburg folder.
  2. In the Catalog view, click Castles.shp, press Ctrl, and select Museums.shp and ReligiousMonuments.shp.
  3. Right-click Castles.shp, point to Export, and choose Feature Class(es) To Geodatabase.

    Feature Class(es) To Geodatabase option

  4. In the Feature Class To Geodatabase geoprocessing tool, for Output Geodatabase, browse to and choose the City_Attractions feature dataset in SalzburgGeodatabase.gdb.
  5. Click Run.

    Feature Class To Geodatabase tool parameters

  6. Verify that the City_Attractions feature dataset in SalzburgGeodatabase.gdb contains four feature classes.

    Imported feature classes

  7. In the Contents pane, under SalzburgGeodatabase.gdb, right-click the Scenic_Attractions feature dataset, click Import, and choose Feature_Class(es).

    Import Feature Classes tool

  8. In the Feature Class To Geodatabase geoprocessing tool, for Input Features, add the following shapefiles:

    Source folder Source shapefile

    City_of_Salzburg

    NatureReserves.shp

    NaturalParks.shp

    Skilifts.shp

    SkiSlopes.shp

    SwimmingHoles.shp

    Waterbodies.shp

    Waterwheels.shp

    OpenStreetMap_Salzburg

    OSM_Salzburg_CableCar.shp

    OSM_Salzburg_CableCarStations.shp

    OSM_Salzburg_NaturalFeatureBoundaries.shp

    OSM_Salzburg_NaturalFeatures.shp

    OSM_Salzburg_ReceationSiteBoundaries.shp

    OSM_Salzburg_RecreationSites.shp

    OSM_Salzburg_Streams.shp

    Feature Class To Geodatabase tool parameters

  9. Click Run.
  10. In the Catalog view, rename the following feature classes.

    Original nameNew name

    OSM_Salzburg_CableCar.shp

    CableCar

    OSM_Salzburg_CableCarStations.shp

    CableCarStations

    OSM_Salzburg_NaturalFeatureBoundaries.shp

    NaturalFeatureBoundaries

    OSM_Salzburg_NaturalFeatures.shp

    NaturalFeatures

    OSM_Salzburg_ReceationSiteBoundaries.shp

    ReceationSiteBoundaries

    OSM_Salzburg_RecreationSites.shp

    RecreationSites

    OSM_Salzburg_Streams.shp

    Streams

  11. Verify the Scenic_Attractions feature dataset contains 14 feature classes.

    Renamed imported feature classes

  12. Optionally, update metadata for Scenic_Attactions.
  13. Import and rename the following shapefiles in the Transportation feature dataset.

    Source folder Source shapefile Output feature class name

    City_of_Salzburg

    BicyclePaths.shp

    BicyclePaths

    BusLanes.shp

    BusLanes

    OneWayStreets.shp

    OneWayStreets

    Pavement.shp

    Pavement

    RoadNetwork.shp

    RoadNetwork

    Sidewalks.shp

    Sidewalks

    Tunnels.shp

    Tunnels

    OpenStreetMap_Salzburg

    OSM_Salzburg_Airports.shp

    Airports

    OSM_Salzburg_PublicTransportStations.shp

    PublicTransportStations

    OSM_Salzburg_Railroads.shp

    Railroads

    OSM_Salzburg_RailroadStations.shp

    RailroadStations

    Feature Class To Geodatabase tool parameters

  14. Verify the Transportation feature dataset contains 11 feature classes.

    Transportation feature classes

  15. Optionally, update metadata for your Transportation feature classes.

Import KML files

Several useful tourism-themed data sources are only available as KML files. You'll use the KML To Layer tool to convert a .kmz file to a file geodatabase.

  1. In the Folder connection, click the kmz_files subfolder.

    In the Catalog view, there are three .kmz files. These are compressed KML files.

    KMZ files

    Because you already have a museums layer in your geodatabase, you'll only convert the Burgen_und_Schloesser.kmz and Kunstwerke_mit_Audiotext.kmz files. These are features representing castles and palaces and the location of art installations by recognized artists.

  2. On the ribbon, on the Analysis tab, in the Geoprocessing group, click Tools.
  3. In the Geoprocessing pane, search for kml. Choose the KML To Layer conversion tool.

    KML To Layer tool

    The KML To Layer tool converts a KML file with its features, which are XML based, into a unique geodatabase specific to the KML file being converted. The features, such as points and polygons, are then added as separate feature classes to a Placemarks feature dataset within this geodatabase. After performing this conversion, you can use the geographic data in these feature classes from your KML file in the same ways you would any other GIS data.

  4. In the KML To Layer tool, set the following parameters:

    • For Input KML File, select C:\Salzburg\kmz-files\Burgen_und_Schloesser.kmz.
    • For Output Location, specify your data folder, for example, C:\Salzburg.
    • For Output Data Name, type Castle_Palace.

    KML To Layer tool parameters for castles and palaces

  5. Click Run.

    The tool creates an output layer file named Castle_Palace.lyr and an output file geodatabase named Castle_Palace.gdb, located in your output folder location (for example, C:\Salzburg).

  6. Execute the KML To Layer tool a second time with the following parameters:

    • For Input KML File, select C:\Salzburg\kmz-files\ Kunstwerke_mit_Audiotext.kmz.
    • For Output Location, specify your data folder, for example, C:\Salzburg.
    • For Output Data Name, type Art_Installations.

    KML To Layer tool parameters for art

  7. Click Run.

    The tool creates an output layer file named Art_Installations.lyr and an output file geodatabase named Art_Installations.gdb, located in your output folder location (for example, C:\Salzburg).

  8. In the Contents pane, expand the Salzburg folder and confirm that Art_Installations.gdb and Castle_Palace.gdb have been successfully created.

    New geodatabases

  9. In the Catalog view, locate and expand the Art_Installations.gdb.

    The geodatabase created by the KML to Layer tool contains a feature dataset named Placemarks.

  10. Expand the Placemarks feature dataset.

    Within the feature datasets, the tool has added a point feature class containing the converted KML point features.

  11. Right-click the Points feature class, choose Rename, and type Art_Installations.
  12. In the Catalog view, locate and expand Castle_Palace.gdb.
  13. Expand the Placemarks feature dataset and rename Points to Castle_Palace.
  14. In the Catalog view, right-click the Art_Installations feature class and choose Copy.

    Copy option

    Copying feature classes between geodatabases is a simple and fast way to move or create copies of feature classes since you are not converting between different data formats.

  15. In the Contents pane, under SalzburgGeodatabase.gdb, right-click the City_Attractions feature dataset and choose Paste.

    Paste option

    The paste fails and the error message reports that the source feature class and target feature dataset have mismatched coordinate systems.

    Failure to paste feature class

    The original KML file, and thus the converted feature class containing points, has a geographic coordinate system set to GCS_WGS_1984. The target City_Attractions feature dataset has the MGI_Austria_GK_M31 projection as its coordinate system. For this reason, copying the source feature class to the target feature dataset failed. However, importing the source feature class into the target feature dataset will reproject source features into the same coordinate system as the target feature dataset.

  16. In the Catalog view, right-click the Art_Installations feature class, point to Export, and choose Feature Class(es) To Geodatabase.

    Export to geodatabase tool

  17. In the Feature Class(es) To Geodatabase tool, set the following parameters:

    • For Input Features, browse to and add the Castle_Palace feature class.
    • For Output Geodatabase, browse to and select the City_Attractions feature dataset.

    Feature Class To Geodatabase tool parameters

  18. Click Run.

    This time, the feature classes are successfully added to the City_Attractions feature dataset because the source features have been reprojected to match the City_Attractions coordinate system.

  19. In the Catalog view, for City_Attractions, confirm that the feature classes have successfully been imported.

    New feature classes

  20. Optionally, update your Art_Installations and Castle_Palace feature class metadata.

    Your SalzburgGeodatabase.gdb now has several feature classes organized into thematic feature datasets that will be useful for tourist agencies to maintain and update to generate new and improved maps and apps for tourists visiting the city of Salzburg.

    At this stage, you may want to share your geodatabase with the stakeholders for feedback before adding additional features and refining attributes to make the data more efficient and useful by applying attribute validation. Before sharing, you may want to do a little geodatabase management.

Prepare the geodatabase for review and distribution

A file geodatabase is stored as a folder of binary files on disk. When you first add data to a file geodatabase, the records within each file are in order and are accessed efficiently by the file system. However, as you delete and add records over time, the records within each file become unordered, and unused space develops as records are removed and new ones are added elsewhere in the file. This causes the file system to perform more record-seeking operations within each file, slowing the rate at which records are accessed. Since you were adding feature datasets and feature classes by importing various source datasets into your geodatabase, you were in essence editing the geodatabase and thereby impacting geodatabase performance.

Next, you'll reorder records and remove unused space to make your geodatabase more efficient.

  1. In the Contents pane, right-click SalzburgGeodatabase.gdb, point to Manage, and choose Compact.

    The process executes when you click Compact and automatically reorders records and removes unused space to make the geodatabase more efficient and reduce wasted space. Compacting a frequently edited geodatabase cleans up storage and unused space while also reducing the size of each file. If you frequently add and delete data, you should compact your file geodatabase on a monthly basis. You should also compact a geodatabase after any large-scale change.

    Compact option

    In addition to compacting a geodatabase, you may also apply compression. A compressed dataset, when distributed, is read-only and therefore cannot be edited or modified in any way except for changing its name and modifying attribute indexes and metadata. Compression is ideal for datasets that do not require further editing, and this may be a suitable way to deliver your initial geodatabase to stakeholders for review without giving them the ability to modify source data features.

    There are several alternatives to consider for sharing your geodatabase with stakeholders. These include creating an XML workspace document; using the Copy or Clip tool to extract subsets of the data; or using the Package toolset to consolidate, package, and share layers, map documents, and results.

    In the following optional steps, you will generate a XML workspace document to share both the data and the schema for your SalzburgGeodatabase.gdb.

  2. In the Contents pane, right-click SalzburgGeodatabase.gdb, point to Export, and choose Geodatabase to XML Workspace Document.

    Geodatabase To XML Workspace Document option

  3. In the Export XML Workspace Document tool, set the following parameters:
    • For Input Data, browse to C:\Salzburg\SalzburgGeodatabase\SalzburgGeodatabase.gdb.
    • For Output File, type SalzburgGeodatabase_ExportXML.xml.
    • For Export Options, choose Data.
    • For Storage Type, confirm that Binary is selected.
    • Check Export Metadata.

    Export XML Workspace Document tool

  4. Click Run.

    You may now distribute and share your output XML workspace document with stakeholders for review and comments.

  5. Save the project.

In this lesson, you created an ArcGIS Pro project to support the creation of a geodatabase. You used the Catalog view to interact with project components and manage the geodatabase, and you created several feature datasets and imported various feature classes. You explored the addition of metadata to geodatabase components and finished by applying compression to make the geodatabase more efficient.

You can find more lessons in the Learn ArcGIS Lesson Gallery.