> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/integrations-and-plug-ins/overview/plan-and-export-to-geodin.md). # Plan and Export to GeoDin This first step of the integration workflow plans borehole locations as a point feature class in ArcGIS Pro, exports them to Excel, and imports them into GeoDin - so the investigation starts from one consistent, georeferenced set of locations. The walkthrough uses the demo dataset: 12 boreholes named like `BH12/CPT12`, EPSG 2232 (NAD83 / Colorado Central ftUS). {% embed url="" %} > **Video chapters:** 0:00 Create a Project and Feature Class in ArcGIS Pro | 0:16 Add Points to the Map | 0:35 Review Attributes of Points | 1:04 Export Data to Excel | 1:17 Import Data into GeoDin | 1:46 Verify Imported Data ## Requirements * ArcGIS Pro with a file geodatabase (GDB) for the project. * GeoDin with the target database and project already created - the import step needs an existing project to receive the records. ### Step 1: Create a project, geodatabase, and point feature class in ArcGIS Pro Create a new ArcGIS Pro project. In the **Catalog** pane under **Databases**, the project geodatabase is created with it. Right-click the geodatabase and choose **New > Feature Class**, set the geometry type to **Point**, and name it for the investigation (for example, `Investigation_Plan`).

The project geodatabase and point feature class in the Catalog pane

### Step 2: Add borehole points to the map On the **Edit** ribbon, choose **Create**, pick the feature template for the point feature class, and click each planned borehole location on the map. **Save** the edits when done.

Creating the planned borehole points on the map

### Step 3: Populate and review point attributes Open the attribute table and complete the fields each record needs before export: * **Full location name** - the borehole name (for example, `BH12/CPT12`). * **Easting / Longitude** and **Northing / Latitude** - the coordinates. * **EPSG-code** - the coordinate reference system (for example, 2232). * **Status** - the investigation status. Missing fields can be added with **Field: Add** in the attribute table before populating them.

The attribute table with names, coordinates, and EPSG codes completed

> ⚠️ **Export gotcha:** ArcGIS Pro doubles underscores in field names on export (`Easting__Longitude`). Keep this in mind when mapping columns during the GeoDin import - the content is unchanged, only the header differs. ### Step 4: Export the point data to Excel Right-click the layer and export the attribute data to Excel. Confirm the export completes and the file opens without errors.

The export dialog with the output Excel file

### Step 5: Configure the import in GeoDin In GeoDin, select the project's **Objects** node and start the **Import general data** method: * On the **Data source** tab, select the exported Excel file, pick the worksheet, and enable **First row contains column names**. Check the preview. * On the **Parameter links** tab, set **Object type** to **Location** and link the spreadsheet columns to GeoDin parameters - or use **Load configuration** to reuse a saved mapping.

The project's Objects node - starting point for the import

Data source tab with the Excel worksheet and preview

Parameter links tab with Object type set to Location

For the full reference on import options, see [CSV and Excel Import](/importing-data/csv-and-excel-import.md). ### Step 6: Run and verify the import On the **Import** tab, review the preview and check that the **Summary** shows the expected count (for example, "New data records: 12"). Click **Perform import** and confirm with **Yes**.

Import preview with the record count in the summary

### Step 7: Verify the imported borehole records Open an imported borehole in GeoDin and confirm the name, coordinates, and EPSG code match the planned values from ArcGIS Pro.

The imported borehole with its location on the map panel

## Optional settings * **Load configuration / save configuration** - after the first import, save the column mapping in GeoDin; repeat imports become a two-click operation. * **EPSG consistency** - keep one EPSG code across all records of an investigation; mixed codes place points in different systems. *** **Next step:** [Export the collected field data back to ArcGIS Pro](/integrations-and-plug-ins/overview/export-to-arcgis-pro.md) once the investigation has been carried out in GeoDin. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.geodin.com/integrations-and-plug-ins/overview/plan-and-export-to-geodin.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.