> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/version/v2.0.0/curate/import-geospatial-data/import-a-shapefile.md).
# Import a Shapefile
{% hint style="info" %}
Registry Administrators and Registry Maintainers can import the lists and spatial data of the Geo-Object Types under the curation mandate of their organization
{% endhint %}
Spatial data is imported into Geoprism Registry through shapefiles.
To be able to smoothly import shapefiles into Geoprism Registry, these basic requirements must be followed:
* The spatial data must be in [shapefile](https://support.esri.com/en/white-paper/279) format.
* As a shapefile consists of multiple files that collectively make up a shapefile, these files must be compressed into a zipped (.zip) file before importing.
* The shapefile must include data only for a single Geo-Object Type.
* The shapefile must be unprojected ([World Geodetic System 1984; EPSG:4326](https://epsg.io/4326)). Otherwise, Geoprism Registry will give an error message and the import will not take place.
Shapefiles are imported as follows:
1. Navigate to the *Import* *Geospatial Data page in the sidebar.*
2. Click on the **Import Shapefile** tab.
3. Fill out the following fields for the shapefile you would like to import:
| Field | Description | Required |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- |
| Hierarchy | Optional. The hierarchy the Geo-Object Type belongs to. Choosing one narrows the Geo-Object Type list to the types in that hierarchy and adds a **Hierarchy matching** step, where you link each Geo-Object to its parents. If the Geo-Object Type is part of several hierarchies, import the parent information separately for each hierarchy. | |
| Geo-Object Type | The Geo-Object Type of the shapefile you would like to import. The dropdown list of Geo-Object Types will depend on the hierarchy selected in the *Hierarchy* field. | Required |
| Import Strategy |
The import strategy for the shapefile being imported:
New and update: This will import the Geo-Objects in the shapefile that are not yet in Geoprism Registry as well as overwrite the attributes of Geo-Objects from the shapefile that are already in Geoprism Registry.
New only: This will import only the Geo-Objects from the shapefile that are not yet in Geoprism Registry. If the imported file contains Geo-Objects that are already in Geoprism Registry (same unique identifier and/or label depending on what is selected during matching) then the import will fail to avoid creating duplicates.
Update only: This will overwrite the attributes of the Geo-Objects from the list that are already in Geoprism Registry. If the imported file contains Geo-Objects that are not yet in Geoprism Registry, these will not be imported.
| Required |
| Start Date | The start of the date of validity of the Geo-Objects in the shapefile. All the Geo-Objects in the shapefile being imported, whether new or for update, should have the same start date of validity. | Required |
| End Date | The end of the date of validity of the Geo-Objects in the shapefile. All the Geo-Objects in the shapefile being imported, whether new or for update, should have the same end date of validity. If the shapefile is still valid on the date it is being imported in Geoprism Registry, click the **Set as most current** button. | Required |
| Data Source | The [Data Source](/version/v2.0.0/configure/data-sources/add-a-data-source.md) the data comes from. | |
| Description | An optional description of this import. | |
| Import blank cells | Selecting this option ensures that if there are empty cells in the list being imported, they are imported as empty attribute values (overwrite). This option gives more control to ensure that updates will either only update cells with values or to overwrite existing values with *null* values. | |
4. Click the **Choose file** button and select the zipped shapefile you'd like to import.
5. Click **Submit**.
6. The *Attribute Matching* window opens containing the attributes for the Geo-Object Type. The number of attributes that appears depends on the number of attributes created for the Geo-Object Type for which the shapefile is being imported. In the dropdown option for each field, choose the attribute from the shapefile being imported that matches the created attribute of the Geo-Object Type. If the Geo-Object Type has a Concept Set, match the column that holds each Geo-Object's classification to the **classification** attribute. Click the **Next** button.
\
*Note:* When the shapefile is formatted correctly and completely, you should be able to match all of its attributes to the Geo-Object Type for which it is being imported. Otherwise, some of the attributes will be left blank.
7. The **Alternative Id Mappings** window opens. It only appears if Source Authorities exist in the system. Optionally, click **Add Id mapping**, select a Source Authority and the shapefile column that holds its IDs, then click **Next**.
8. If you chose a Hierarchy, the *Hierarchy Matching* window opens listing the Geo-Object Types above (parent) the Geo-Object Type for which the shapefile is being imported. The number of Geo-Object Types listed depends on the position in the hierarchy of the Geo-Object Type for which the shapefile is being imported. Fill out the following fields for each parent Geo-Object Type:
| Field | Description |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Source file parent column | The attribute from the shapefile being imported that corresponds to the parent Geo-Object Type (unique identifier or name) |
| Match Strategy |
How the values in the column are matched to parent Geo-Objects:
Code, label, and synonyms
Code only (fastest)
Alternative ID: the column holds alternative IDs. Choose the Source Authority that issued them.
|
*Note:* The hierarchy matching is optional. This could be completed if you have added the hierarchy information to the shapefile you are importing.
9. Click **Ok**.
10. The import will start processing. Click the **Go to jobs** button to view the progress. This will direct you to the *Scheduled Jobs* page.
```
```
## Fixing problems found during import
When you click **Ok**, Geoprism Registry checks your data before importing it. If it finds values it can't match, a window opens so you can fix them:
* **Parent Location Problems** lists parent locations from your file that don't match a Geo-Object in the hierarchy. For each one, either search for the correct location and create a synonym, so this name always maps to that location, or exclude the data at that location from this import.
* **Term Problems** lists values that don't match an option of a term or classification attribute. For each one, create a synonym for an existing option, create a new option with that name, or exclude the data with that value from this import.
You can undo a fix before continuing. **Ok** stays disabled until every problem is resolved.
