EOMeasyExporting surfaces from Vulcan
EOMeasy prepares a folder, a macro runs inside your own Vulcan session, and EOMeasy assigns the results. There is no add-in to install and nothing to set up: Vulcan already has everything the macro needs.
eom_export_maptek.py from Python Scripts, then click Auto-assign from folder and watch the three paths fill themselves in.Step 1: Prepare the export folder (in EOMeasy)
Open the period and click Prepare export folder, with the package set to Maptek (Vulcan / PointStudio). One macro serves both. EOMeasy drops two files into the folder you pick:
eom-export-manifest.json: the list of volumes and the slug (key) for eacheom_export_maptek.py: the export macro, self-contained in one file
Step 2: Name your surfaces and boundaries (in Vulcan)
Name each triangulation for the volume it belongs to, followed by its role: Stage 4 West start and Stage 4 West end, or PIT1-START and PIT1-END. Both work. Matching ignores case, spaces and the separator, so you can name them however your site already does. Load them into the session before running the macro.
Boundaries match on either the string's own name or the name of the layer holding it, so a closed string in a layer called PIT1-BDY works as well as a string named that. <KEY>, <KEY>-BDY and <KEY>-BOUNDARY all match.
Step 3: Run the macro (in Vulcan)
Run eom_export_maptek.py from your Vulcan session. It reads the loaded triangulations and layers, writes <key>__start.obj, <key>__end.obj and <key>__boundary.dxf next to the manifest, prints which objects it read, and reports anything it could not fill.
A large triangulation takes a while to write. That is the surface size, not a stall.
Step 4: Auto-assign (back in EOMeasy)
Return to EOMeasy and click Auto-assign from folder. It fills in each volume's start surface, end surface and boundary. You are ready to run the period.
If something did not match
If a volume is left unassigned, a surface or boundary name probably did not match the volume and role, or the surface was not loaded in the session. The macro prints MISSING <key> <role> along with the objects whose names contain that key, so a near miss is visible in the output. A boundary string cannot fill a surface role, or the other way round, however it is named. See Troubleshooting for the full list.