Troubleshooting FAQs in GIS Software

The list below includes helpers for common troubleshooting questions we receive from students.
(It will forever be a list-in-progress.)

BUT FIRST, if you’re experiencing inexplicable troubles: No spaces in your file names, your folder names, or anywhere in your paths!

Interface & Organization

  • If your data is moved from its original location (i.e., the path no longer leads to the same data set), then your data link is said to be “broken.”

  • When in doubt, right-click. You can generally find what you’re seeking in the menu that pops up. Also, see All About Layer Properties in ArcGIS Pro.

ArcGIS Pro Settings

Tables & Table Joins

  • Regardless of your software, try these:

    • Check the data types of the fields in each table upon which your join is based. Table joins require those fields to be of the same data type.

    • Convert both tables to a GIS-native file type. Attribute tables within feature classes, shapefiles, etc, are GIS-native. As are standalone tables within geodatabases and geopackages. CSVs and Excel sheets, however, are not.

    • Check for “leading spaces” or other invisible characters in your join fields. Trim these as needed.

    • Last resort (but it often works): Open a brand new, clean project file. Add your tables, then join.

  • The short version: Whether you’re using field values as a basis for a join or for other purposes, best practices include

    • Adding a clean table into your GIS software. By “clean” we mean “without Excel formulas” as cell values.

    • Preferably, adding a standalone table as a CSV, then export it as a GIS-native table type.

    • If you add an Excel sheet to a map project, it should definitely be devoid of any formulas and definitely export it as a GIS-native table type.

    A little bit more information: We know that numeric characters can look like number values while being stored as text strings. Excel does the same by populating cells with numeric values but those values are stored as formulas.

PopUps & Warnings

Something Else Seems to Be Wrong…

  • If you are trying to calculate geometry attributes with unprojected input features, you will not see all of the geometry property options until you specify the CRS for the calculation. (For example, you’ll see the option to calculate geodesic area, but the option to calculate area.) This is because the default CRS for geometry calculations is that of the input feature class. Once you specify a projected CRS for the calculation, the other options will be available.

Working More Efficiently