3DNature

3D Landscape Design & Visualization Software published and supported by AlphaPixel

  • 0
    • Menu

    Part 8A. Importing Shapefiles with Attributes

    Getting Started with VNS 3: GIS Basics
    Getting Started with VNS 3: GIS Basics

    Part 8A. Importing Shapefiles with Attributes

    1. Go to the Tutorials\GIS project folder and open GISBasics. Save it as GISBasics8 to avoid overwriting the original file.

    Screenshot of Visual Nature Studio 3D software interface showing terrain maps, option panels, and different ecological elements like atmosphere and geological effects.

    2. Render a Main preview.

    A computer-generated landscape image showing green terrain with scattered trees and hills in the background, displayed within a software interface.

    3. The global Environment is composed of the two Ecosystems we’ve been working with: Grassland and Pine Burn. The Rules-of-Nature work well for rendering convincing landscapes, but reproducing actual land cover usually requires real-world data. We’re going to use vector data in the form of a shapefile to drive Pine Burn Ecosystem placement.

    4. Shapefiles have the advantage of storing database information associated with vectors. Search Queries and Thematic Maps can save production time, and can dynamically update when vectors change.

    5. Open the Database Editor to see the 12 DEMs we have so far.

    A window titled "Database Editor" shows a grid with columns for Name, Enabled, View, Render, Color, Class, and Styl. Each row is a YNP-10m code, all enabled and under the DEM class.

    6. Launch the Import Wizard. Go to the VNS 3 DVD database folder and select the PINE BURN.shp file. The Wizard will correctly identify the file as an Arc Shapefile. Continue to the Next window.

    Dialog box showing an import wizard identifying a file named 'PINE BURN.shp' as an Arc Shapefile, with options to override file type and buttons for "Back," "Next," and "Cancel.

    7. The LOAD AS window will load the shapefile as Vector objects enabled for rendering. Go to the Next window.

    Screenshot of an import wizard window labeled "PINE BURN.shp" with options to load data as DEM, Vector, Control Points, or Image. The DEM option is selected with "Render Enabled" checked.

    8. OUTPUT FILE TYPE AND NAME gives us the option to ReImport when Project Loads. This is for when you expect the input data to change and want it automatically updated when the project is opened. We don’t, so continue to the Next window.

    Screenshot of an Import Wizard with the title "PINE BURN.shp," showing options for output file type and name, with selected output format as "Database Vector." A mouse cursor is clicking "Next.

    9. The COORDINATE SYSTEM SUMMARY will show a Custom Coordinate System using the Geographic NAD 27 projection method and system. Go to the Next window.

    Screenshot of an Import Wizard window titled "PINE BURN.shp" detailing coordinate system summary and asking users to set system parameters before proceeding by clicking "Next.

    10. The Attributes section of the SHAPE OPTIONS page lists all the attributes VNS found in the shapefile. We’re going to Assign DB Names from an Attribute Field and Load Attributes, so make sure they’re checked. VNS will Add File Layer for our convenience. Import the data.

    The image shows an "Import Wizard: PINE BURN.shp" window with various attribute options and checkboxes ticked, including Add File Layer. The Import button is in focus and highlighted.

    11. We’re going to stick with the Coordinate System we have, so decline the offer to change it.

    Pop-up dialog box asking, "Make this new Coordinate System the default for Viewing and Rendering?" with "Yes" and "No" button options; the cursor hovers over "No.

    12. The first Database Fields window is looking for attributes to load. Always double-check what VNS is asking for. The request windows will depend on your choices in the last Import Wizard SHAPE OPTIONS window. We want all attributes so Select All.

    A dialog box titled "Database Fields" showing selectable database field names: SUB_DENSIT, DOM_DENSIT, and ECOS. A cursor hovers over the "Select All" button. Options include OK, Select All, and Cancel.

    13. The next Database Fields window wants a name field to assign to each shapefile object. A unique identifier is best, so let’s use the VectName.

     

    A dialog box labeled "Database Fields" showing a list of fields with "VectName" selected. Available options include SUB_DENSIT, DOM_DENSIT, and ECOS. A cursor points to the "OK" button.

    14. After the data is imported, the realtime Plan view will refresh with the vectors. The Database Editor will show 9 new objects. Save the project.

    A topographic map with color gradient from green to brown and red contour lines indicating elevation changes in a geographic area.
    A database editor window displaying a table with various columns and rows, including checkboxes. Several entries under "Color" are labeled "Vector" with different settings for style and weight.

    15. Go to the Database Editor and turn to the Attribute page. Here we see the subdominant and dominant foliage density values and the ecosystem type.

    Database editor window displaying a table with columns: VectName, SUB_DENSIT, DOM_DEN, and ECOS. Rows list data for entries such as PB01 and YNP-10m.BU. Toolbar with various options at the top.

    16. The Layer page shows that PB01 is a member of two Layers, including PINE BURN. If you can’t read the entire column header, click it. This gives you access to Layer operations, too.

    A screenshot of a database editor interface displaying various layers and checkboxes for viewing and enabling layer members. The menu option "PINE BURN (Layer)" is selected with layer management options visible.

    17. Switch the Main view back to realtime mode. The vectors aren’t visible, so let’s find out why. Back in the Database Editor, Edit Database Object to open the PB01 Vector Editor. Go to the Selected Points page and you’ll see that the Elevation is 0 meters. That means the vectors are underground in the Main view. By design, planimetric views see vectors regardless of their elevation. Close the editor.

    A window titled "Vector Editor" with various options for editing points, including units, coordinates, and elevation. There are buttons labeled Keep, Undo, Restore, and Cancel at the bottom.

    18. Go back to the Database Editor. Select the PINE BURN Layer to select all member objects.

    A screenshot of a database editor showing a list of layer names with checkboxes. A context menu is open, highlighting the option "Select Layer Members.

    19. The Database Editor will show 9 of 21 objects selected.

    Database editor interface showing a table with columns for Name, 10m, PolyLine, and PINE BURN. Various cells are checked or unchecked within the table. Top menu bar includes common icons.

    20. Conform to Terrain.

    Screenshot of a database editor software displaying a table with column headers and rows of entries. A dropdown menu is open showing the option “Terrain” under “Conform to:”.

    21. Confirm the operation. VNS will verify that all 9 vectors have been conformed to the terrain. The Main view will refresh and show the vectors, now that they’re at ground level. Save the project.

    Dialog box with the message "Conform all selected Vectors and Control Points to terrain elevations?" and options to click "OK" or "Cancel." A cursor is pointing at the "OK" button.
    A dialogue box with the title "Conform to Terrain" states that 9 selected Vector and Control Point objects have been conformed to the terrain. An "OK" button is clicked with a mouse cursor.
    A computer-generated 3D terrain image with green, brown, and red colors, indicating different elevations or features, displayed on a software interface.
    Next
    Scroll to top
    Skip to content