Troubleshooting

This page gives suggestions to help solve the most commonly encountered issues with GISquirrel. For issues with installation please see the installation guide.

When I enter my licence code I get an error message - what should I do?

On Windows 7 and later operating systems, the GISquirrel licence file is held in a location that can only be edited by administrators. Run ArcMap as Administrator (right-click the shortcut, and "Run as Administrator"), then enter your GISquirrel registration information.

Why can't I see my feature classes in the “Add Data” browser or ArcCatalog?

Feature classes will appear in a folder if all the following conditions are met:

• the folder contains a valid GISquirrel connection file (*.asq);
• the user has read permissions on the folder containing the connection file;
• the connection file authenticates the user with at least read permissions to a database containing a valid ArcSquirrelMetadata table.
• a record in the ArcSquirrelMetadata table correctly defines a feature class;
• the user (as authenticated through the connection file) has read permissions on the table/view underlying the feature class;

Some features become permanently locked to one user - how do I fix this?

In certain unusual circumstances, for example if ArcMap crashes during an editing session, it is possible that features could become remain locked out to a user. These locks can be seen by the presence of a username in the “asq_lockedby” field in the table. There are two simple ways to resolve this. The best method is for the user who is locking the features to start a new editing session (on any features in the dataset). When the user stops their editing session (with or without saving edits), all locks belonging to that user will be removed.

If for any reason this is not possible, for example if the user is not available, the locks can be removed by updating the “asq_lockedby” field to NULL for records where the “asq_lockedby” field contains the username. This can be done using database administrative tools, or through an ODBC client such as Microsoft Access.

Why have some features failed to import into GISquirrel?

The GISquirrel Import Layer tool attempts to create valid geometry from each incoming feature, using a multi-stage stage process. However, this is not always possible. In particular, SQL Server is more particular about topological validity than ESRI shapefiles or geodatabase feature classes, and also has some inconsistencies in how this has been implemented. For example, a polyline feature where two vertices share exactly the same coordinates is not altered by the MakeValid method, but still fails to insert into a Geometry field.

The Import Layer tool will show an information message about each feature that cannot be imported, and this may be sufficient to establish (and remedy) the cause.

The Import Layer tool continues to import despite these errors, simply excluding the problematic features. After completion, there are two approaches to migrating any failed features:

1. Delete the GISquirrel feature class using the Feature Class Admin tool (and delete the new table using database administration tools), fix the source dataset, and run the import again.
2. Start an GISquirrel editing session on the new layer, copy and paste and fix the failed features into the editing session using ArcMap editing tools, then save edits. It will not be possible to save edits back to the new GISquirrel feature class until they are valid geometries.

Why have some features failed to save in an GISquirrel editing session?

When GISquirrel stops an editing session and attempts to save the data back to the source table, it checks and repairs features where necessary, using the same methods as the Import Layer tool. However this is not always possible, for the reasons explained above. An informational message will be displayed if this occurs, the editing session will continue, and the first problematic feature found will be selected to help identify and fix the issue.

Note, for example, that using the “Circle tool” on the ESRI Advanced Editing toolbar to create a circular polyline will always fail against SQL Server 2008, as this creates a polyline with two vertices that share the same coordinates.

I've set a wrong coordinate system on a feature class - how do I correct this?

When creating a new feature class based on an existing table or view, it is possible to set the coordinate system to a value that is not correct for the dataset. Once this has been done, the coordinate system cannot be changed using the GISquirrel user interface (e.g. in the Feature Class Admin > Edit… interface). To allow this would suggest that the data itself would be transformed from the old to the new coordinate system, and this functionality is not provided at present.

If the coordinate system has been set incorrectly by accident, it is likely that the features will not display in the correct location against other datasets. The simplest solution may be to delete and re-create the feature. Alternatively, an existing feature class and table can be corrected using the following procedure.

Edit the arcsquirrelmetadata table (using database management tools or an ODBC client such as MS Access), and change the “srid” value for the feature class record to the required EPSG code. These codes are displayed alongside the name of the coordinate system name in the Import Layer and New Feature Class forms. This change will take effect on re-starting ArcMap or removing and re-adding the feature class to the map.

Alternatively delete and recreate the feature class using the Feature Class Admin tool.

Why do I get an error when I try to export a GISquirrel feature class from ArcCatalog?

Exporting a GISquirrel feature class to shapefile or geodatabase from ArcCatalog gives an error:

000732: <value>: Dataset <value> does not exist or is not supported

It is possible to export the data from ArcMap instead.

Does GISquirrel support custom coordinate systems?

Not yet - Layers that use a custom coordinate system will default to “Unknown” in the Import Layer dialogue, but this can be changed to one of the supported coordinate systems and the data will be re-projected during the import process.