Maptek Vulcan
Clara Vanliere
.maptekobj is the Maptek object file. The purpose of this generic file format is to allow the operator to transfer objects between other projects, or any arbitrary groups of objects excluding external referenced files. All data can be stored in one file, which makes it easier to email than Maptek projects. Otherwise, objects can be saved to individual files.
Newly acquired scans will be exported in their entirety. Data reduction (to reduce file storage requirements) will be performed on scans whose visibility has been manipulated. This process will crop invisible or invalid points from the edges of the scan.
Ensure the preview columns displaying the output format are assigned to the correct value. If they are not correct, change the assigned columns by clicking on the column header and choosing the appropriate variable from the drop down list.
Image files can be imported and exported in association with surfaces and scans. The images can be draped over the entire target object or placed on a specific patch. Appropriate options will be available dependent on the target object for the image.
On the Home ribbon tab navigate to the Data group and click Export.
You should be able to select the JPEG image file format for exporting the image. Specify path and or separate file options if appropriate.
Click OK or Apply to continue.
Q. How has the external beta test program improved?
A. At the suggestion of one of our customers we created a beta release walk-through document that expands on the release notes. This outlines the major features of the Vulcan 8.2 release and also includes sample data and steps to allow users to easily work with the new features. We also added a Vulcan Downloader tool that allows customers to download Vulcan after validating their licenses.
Q. Tell us more about the Vulcan Downloader tool.
A. Our clients have been asking us to make full releases of the software available to download. The Vulcan Downloader tool allows clients with valid licenses to obtain a full release of our software after the license has been validated, while protecting Maptek intellectual property. This tool has worked well for many of our clients.
Q. Why should people feel better about upgrading each time there is a new Vulcan release?
A. Vulcan improves with every release. Each version is well-tested and the number of automated assets increases every time. The new walk-through product release guides are helpful for introducing users to the new features in the release, making for smooth transition. Lately, we have been rolling out more frequent releases to get new functionality into users hands quickly. We encourage customers to take advantage of the new tools and features by upgrading their Vulcan version at each release.
For additional information about Maptek, including use of the Maptek logo, product images and reproduction of case studies, please direct inquiries to Global Marketing Communications Manager jane...@maptek.com.au
The sister package maptekomf.vulcan provides support for inter-operability withthe Open Mining Format (OMF) and Maptek Vulcan which does not share the sameunderlying infrastructure of Maptek's other applications.
The recommended version of mapteksdk to use this with is 1.6.Version 1.4 and 1.5 of the mapteksdk are supported, but it recommended toupgrade where you can, and to use newer applications you will often need touse the newer SDK.
This OMF importer/exporter implementation has the following behaviour thatmay be different to how other implementations, scripts and applications handlea given OMF project file. This is done in places where the OMF specificationdoes not specify how such cases should be handled, especially in caseswhere data can't be represented natively in the data format.
As a result, during import if a duplicate name is detected a numerical suffix,will be added. When adding this suffix, if there is an object in the OMFproject with that name, it will be skipped even if that element/object won't beimported. For example, if an OMF file contained three objects, two called"point_set" and a third called "point_set 2" then the first will be named"point_set", the second will be named "point set 3" so that it does not clashwith "point_set 2" and the last will be called "point_set 2". The name"point_set 1" will not be used when selecting a unique name; "point_set" isconsidered the first object.
When importing, the "point colours" attribute will be recognised and read inas a colour array. Maptek applications only support one set of colours perprimitive (primitive being point, edge, cell or facet). Multiple colour arrayattributes are not supported.
The Maptek object type GridSurface has the concept of point visibility, whichis a way to hide cells that are not relevant. For example, they may falloutside the data range (i.e. the area that was measured/recorded). This isachieved by saving it as an attribute for vertices called "visibility" in OMFand recognising the attribute in the importer.