Skip to content

Troubleshooting

Quick fixes for the snags you're most likely to hit.

  • Data Manager, Datum, or Process are greyed out. You haven't set the project location yet — the GNSS workflow needs it. Go to Project Information and place the site / draw the boundary. See the location gate. The Modeler tabs, Orbiter, and your reports don't need it: a photos-only project runs on the camera GPS.
  • Export DXF is greyed out. The DXF is written in the project's Grid coordinate system, so the project needs one. Set it under Project Information → Coordinate system.
  • My elevations look like the wrong height. Check Project Information → Coordinate system and confirm you chose ellipsoidal vs orthometric correctly for what your client expects.
  • My imported GNSS logs aren't showing. On Data Manager, open the UBX scan settings and check the discovery options.
  • A cloud build is taking longer than expected / re-sending photos. A rare processing-machine hiccup can cause InTerra to re-send your imagery to a fresh dedicated machine rather than keep a stored copy — a deliberate part of the data-protection design (see Zero Persistence Computing).
  • My report shows InTerra branding instead of mine. Set your company logo and details under Settings → Branding…; they apply to every report you generate afterward.
  • What version am I running / is my license OK? Help → About shows the version, license key and type, credits, and days remaining.
  • A layer I expect isn't showing on the map. Most overlays start hidden so a project opens clean — contours especially. Open the layer legend in the map's top-right corner and tick the layer on. If it isn't listed there at all, either that tab doesn't carry it or the build didn't produce it — check Build Model → Outputs for what you asked the run to make. See Map legend.
  • A cloud upload looks stuck. On a slow uplink a single large photo can take minutes to send. InTerra allows up to 15 minutes per photo, retries a photo up to three times if the connection drops mid-transfer, and eases off how many it sends at once when the link is thin. Leave it running — it recovers on its own. It gives up only if the whole transfer stops making progress for 20 minutes.
  • The Coordinate Transformation tool won't accept my latitude/longitude. It takes decimal degrees (40.4462), space-separated degrees-minutes-seconds (40 26 46), and a cardinal suffix (40 26 46 N), in either field. If a value can't be read, the tool now tells you which field is at fault instead of quietly doing nothing.