Rhino.Inside for ArcGIS Pro
User guide · 1.3.0

User guide

A link pairs one ArcGIS feature layer with one Rhino layer. Its profile controls attributes; Preview shows the next exchange.

First, confirm where the model belongs.

The earth anchor connects Rhino's local model coordinates to geographic coordinates. Confirm the GIS layer's coordinate reference system and Rhino's units, then set or review the anchor using the dockpane's earth-anchor controls.

Use a known feature to check position and elevation before applying edits. Changing or clearing the anchor changes how later geometry is located. Do not reset it casually after linking data.

The anchor is a WGS84 latitude and longitude. Each link is placed in its own layer's coordinate system: a Rhino metre becomes a metre of ground whatever the projection (Web Mercator's stretch, State Plane feet and scale factor, grid convergence), and layers on another datum such as NAD83 or NAD83(2011) go through the datum transformation ArcGIS selects for the area. A sync warns if a layer's datum has no transformation available.

Every vertex is placed individually through ArcGIS's own geodesy, so accuracy does not fall off across a large site. Any Rhino unit system works, from microns to miles, including custom units. A document with no anchor is anchored at the map centre on its first pull or push. Heights pass through unchanged; vertical datums are not converted.

Rhino documents synced before this exact placement existed keep their original placement, so nothing already linked moves. New documents use the exact placement automatically.

Start with GIS context.

  1. Launch the embedded Rhino host and activate your ArcGIS map.
  2. In Link, pair the source GIS layer with a Rhino layer.
  3. Choose the intended direction. Two-way permits exchange in both directions; Pull-only permits updates toward Rhino; Push-only permits updates toward ArcGIS.
  4. In Profile, review field inclusion and ownership. Save the profile.
  5. Use Pull once to create the initial tracked Rhino objects. For a subset, select the GIS features and use selection-only pull.
  6. Open Sync and run Preview. An unchanged initial pair should be clean.
  7. Edit, preview again, then apply the changes you intend.

Pull skips features already in Rhino, so repeating it only restores objects deleted in Rhino. Use Preview and Apply for subsequent exchanges. Save the Rhino document: links and sync baselines are stored in it.

Start with a Rhino design.

  1. Put the source geometry on a Rhino layer. Add user-text keys for attributes you want to publish.
  2. In Link, use New ArcGIS layer from Rhino layer.
  3. Choose the source Rhino layer and a valid destination name. Review the inferred geometry and fields.
  4. Select Create and push. This creates a Z-enabled feature class in the project's default file geodatabase, adds GlobalIDs, adds it to the map, saves the link and pushes the initial objects.
  5. Run Preview to check the result, then review the saved profile.

Points, curves, planar regions and meshes map to the supported GIS types. Supported 3D Breps, surfaces and extrusions are meshed for Multipatch. The majority supported type selects the destination class; incompatible objects are skipped and reported. Split mixed geometry into separate Rhino layers when you need separate GIS classes.

An empty layer cannot infer a destination type. Add supported geometry first.

If the objects are already linked to another ArcGIS layer, you choose what happens. Copy publishes a copy from a new Rhino layer, and the existing link is untouched. Move ends the old link and links the objects to the new layer. This is how you bring a design into a different map, coordinate system or project.

Decide who owns each field.

Select the pair, open Profile, include the needed fields and map each GIS field to a Rhino user-text key. Choose an owner and select Save profile.

OwnerEffect
Rhino ownsRhino edits can push. ArcGIS-only edits do not overwrite Rhino.
ArcGIS ownsGIS edits can pull. Rhino edits do not overwrite GIS.
SharedEither side can edit; simultaneous edits create a conflict.
Rhino only / ArcGIS onlyThe value stays on its own side.
Derived / LockedGeometry metrics and ArcGIS-managed fields remain protected.

The global Let Rhino edit attributes option is a fallback for pairs without a custom profile. A saved per-link profile is authoritative.

Optional validation

Mappings can carry units and validators: non_empty, positive_number, non_negative_number and range:[minimum,maximum]. Separate multiple rules with semicolons. Invalid rules stop the profile from saving; invalid values stop the affected write.

Restore defaults removes the custom profile and restores safe defaults. It does not delete geometry or the link.

Read the preview before applying.

Preview compares both sides with their last synchronized baseline and writes neither model. An uninitialized Rhino document first needs a Pull or explicit initialization through an authorized write; Preview does not set its earth anchor or georeferencing mode. Inspect the roll-up and filter the detail list to see changed, conflicting, held or failed rows.

  • New or modified: check the target and side before Apply.
  • Conflict: both sides changed. Manual holds the conflict. Prefer Rhino or Prefer ArcGIS chooses that side according to the active policy.
  • Held: a direction, ownership or deletion rule prevented the exchange.
  • Warning: inspect the message, including any changed source path.
  • Failed: correct the cause and preview again before retrying.

Double-click a row to select and zoom to its object in Rhino and its feature in ArcGIS. If either side changes after a preview, a notice marks the rows as out of date.

Apply recomputes the current plan using the active direction, profile and conflict policy. Run Preview again afterward to verify the expected clean baseline.

Per-object conflict decisions are not available in the current review table. Keep Manual selected until a broader preference is appropriate for the active operation.

Detected deletions are held rather than automatically mirrored. Removing a link removes its pairing metadata, not either side's geometry.

Save both sides.

Save the Rhino document as a .3dm to retain links, profiles, identities and baselines. Save the ArcGIS project and any pending GIS edits as appropriate. Reopen the matching project and Rhino document, refresh the layers, and Preview before continuing.

The dockpane shows a banner while the Rhino document has unsaved changes. When you close ArcGIS Pro with unsaved Rhino work, it asks whether to save it. Rhino then shuts down cleanly, so the next start does not offer to recover files.

Layer pairings do not embed the GIS datasets into the Rhino file. Collaborators need access to the corresponding GIS data.

What this release does not cover.

  • Extent, query, delta, geometry-only and attribute-only advanced pull filters.
  • Dedicated Rhino commands, Grasshopper components and direct Grasshopper preview in ArcGIS.
  • Per-object conflict choices in the review list.
  • Exact NURBS, materials or analytic-surface round trips through Multipatch.
  • Multipatch ring groups containing holes. Tessellate them to triangle patches in ArcGIS before exchange.
  • Vertical datum transformation. Heights are exchanged as they are.

Read the release notes for the validation scope of the installer you are using.

Optional MCP control.

The source candidate includes tools to inspect the embedded Rhino host, saved links, profiles and changes, and to launch, pull, apply and save after local review in ArcGIS Pro. The stdio gateway requires Node.js 22 or later and explicit host-PID selection. It works alongside the separate ArcGISPro.MCP gateway; it does not add operations to that gateway's registry.

Embedded-host and coexistence acceptance are pending. See setup, tool reference and validation status. Author new links and profiles in the dockpane.