vSite Admin Portal: LandXML Datasources
LandXML File Upload Process
To add a LandXML data source, go to the Datasources tab and click Add Source (Fig. 1).
- Drag and Drop your file into the Add Datasource popup (Fig. 2).
- Select LandXML from the Type dropdown field and click Next.
- Fill in the mandatory fields then click Create.
You will receive a message at the bottom of your screen notifying you that your data source was created. You should now be able to locate this data source on the Data Sources page.
LandXML Configuration Settings
The content below details all fields needed for this Datasource type and some common configuration settings to help you get started. To go back to the list of available Datasource types, click here.
Remember, to see the fields below, you will need to go to your Datasource and click the Synchronize Structure button.
Root Level
Layer Group
Select one of the predetermined layer groups (made at the team level). By default, all child notes inherit all settings from the parent node - if anything is set at the Root level, all models within the root will be set the same way.
Elevation Type
- Default - Allows the system to recognize if the data set is z-enabled or not. If z-enabled, the base for the elevation calculations will refer to the sea level and its corresponding vertical datum. If not, it will count as Surface offset.
- Surface offset - Refers to the selected digital surface as the base for the elevation calculations.
- Ignore z-value - Ignores z-values within the data set.
Select Color
Select from preset colors or customize your own from the colour palette controls.
Vertical Datum & UoM (Unit of Measure)
Use the drop-down to select a preset datum that closely matches your project specifications. Skipping this step could result in your datasource layers being stacked on a flat surface when viewing in the app (if you don't see the vertical datum you need, open a ticket with vGIS Support to make your request).
Model Level/ Category Level
Disclaimer: Depending on the structure of the original dataset, the following fields can also be applied at the category level (note: any changes made at the model level will apply to all categories within).
Layer Group
Select one of the predetermined layer groups (made at the team level). By default, all child notes inherit all settings from the parent node - if anything is set at the model level, all categories within the model will be set similar way.
Header
This field, while editable, is generally preset with the header from the original dataset. The header can be seen when pointed at using the vSite AR app.
Object Type
This field should remain untouched as it could lead to configuration issues. It can however be used to verify which object type has been uploaded (Point, Line, Area, 3D Model, or Unknown).
Select Color
Select from preset colors or customize your own from the colour palette controls.
Sub-header
When applicable, use this dropdown to add more descriptive content to the selected layer (options; color, id, layer name, and type).
Object Configuration
These fields are normally preset from the original dataset but can be used to modify or configure fine details of a selected layer (Note: unit of measure will be asked for all measurements).
Coordinate System Type
There are three options:
Global: Provide the projection system and vertical datum (with its unit of measure) for admins to match with the original dataset location. Don't forget to use the Check Location button at the top of this section to verify your coordinate system location.
Manual: Enter the vertical datum and unit of measure for the dataset. These additional fields will appear below to complete the manual coordinate process: Altitude, Latitude, Longitude, Pitch, Roll, and Yaw.
Local: No extra fields will appear, instead you are using preferred xyz coordinates that users can apply to a datasource.
EPSG and UoM (Unit of Measure)
Specify the EPSG code that matches the original dataset. The unit of measure drop-down will be on the right and should also match the original location.
Enable Double-Sided Surfaces Switch
This feature is primarily used for datasets with double-sided renderings, such as cut-and-fill profiles. Such surfaces can be viewed from both sides of the surface.
It is advised to disable it unless absolutely necessary. Double-sided surfaces will double the processing requirements on your mobile or holographic device, which may impact performance. To read more, click here.
Enable Model Interactions
This field enables the physics engine within the model and its categories so users can interact with its data. When OFF, the selected model cannot be interacted with (Eg. you wouldn't be able to click on objects within the model or see distance and elevation to a selected point) and can only be viewed in AR or vSite Web. This will relieve processing power for your device if it slows down while operating the mobile app.
Vertical Datum and UoM
Use the drop-down to select a preset datum that closely matches your project specifications. Skipping this step could result in your datasource layers being stacked on a flat surface when viewing in the app (if you don't see the vertical datum you need, open a ticket with vGIS Support to make your request).
Extend Viewing Range switch
The viewing range tells the mobile application how much data should be in-view at one time. When this switch is toggled ON, it will force the model to always be visible up to a max distance of 5km from the user. This should only be used in circumstances where users need to see a far-distance model (like a bridge or far-away building). Enabling this may significantly affect the user's hardware performance.
Additional Details
Subtype Field
This field will only populate with the distinct values within the original dataset.
Label Type
This field will help identify elements with digital markers flags, or floating text (Note: as more labels become visible, the processing demands increase for the device used).
Elevation Type
At the layer folder level, there are four options:
- Use Parent Node Setting - Takes configuration settings made at the Root level (see above).
- Default - Allows the system to recognize if the data set is z-enabled or not. If z-enabled, the base for the elevation calculations will refer to the sea level and its corresponding vertical datum. If not, it will count as Surface offset.
- Surface offset - Refers to the selected digital surface as the base for the elevation calculations.
- Ignore z-value - Ignores z-values within the data set.
"Exclude from processing" Switch
When the same switch is toggled at the Root level (see above), enabling the switch at the model level will open a list with drop-down boxes. Admins can assign the predetermined floors to each layer folder.
Have Questions? Feel free to Submit A Request to speak with a member of the vGIS Support Team.