2009
Table Of Contents
- Autodesk NavisWorks Simulate 2009
- Contents
- Part 1. Welcome to Autodesk NavisWorks Simulate 2009
- Part 2. Installation
- Chapter 3. Quick Start to Stand-Alone Installation
- Chapter 4. Move to NavisWorks from a Previous Release
- Chapter 5. Install NavisWorks for an Individual User
- Chapter 6. Install NavisWorks for Multiple Users
- Quick Start to Network Installation
- System Requirements for a Deployment
- Creating Network Deployments
- Preliminary Tasks for a Network Deployment
- Use the Installation Wizard to Set Up a Deployment
- Start the Deployment Process
- Create a Deployment
- Enter Product and User Information
- Specify Log File Locations
- What Is Silent Mode?
- Customer Involvement Program (CIP)
- Select a License Type (optional)
- Select the Installation Type (optional)
- Final Review and Complete Setup
- Register the Product
- Modify a Deployment (optional)
- Point Users to the Administrative Image
- Uninstall the Program
- Chapter 7. Installation Troubleshooting
- What are the minimum system requirements?
- How can I check my graphics card driver to see if it needs to be updated?
- What is the difference between a stand-alone license and a network license?
- What is the benefit to using a network licensed version of the software?
- When performing a Typical installation, what gets installed?
- Where are my product manuals?
- Deployment Issues
- Networking Issues
- Maintenance Issues
- Part 3. Basic NavisWorks Functionality
- Chapter 8. Overview
- Chapter 9. File Management
- Chapter 10. Converting Files
- File Readers
- NWF Files
- NWD Files
- NWC Files
- DWG and DXF Files
- DWF Files
- Bentley AutoPLANT Files
- 3DS Files
- DGN and PRP Files
- MAN Files
- PDS Files
- IGES Files
- STEP Files
- Inventor Files
- VRML world files
- Riegl Scan Files
- Faro Scan Files
- Leica Scan Files
- Z+F Scan Files
- ASCII Laser Scan Files
- STL Stereolithography files
- AVEVA Review RVM and RVS files
- IFC files
- Sketchup SKP files
- File Exporters
- CAD Previewing
- File Readers
- Chapter 11. Publishing
- Chapter 12. Navigating
- Chapter 13. Selecting Items
- Chapter 14. Finding
- Chapter 15. Editing
- Chapter 16. Display Modes
- Chapter 17. Viewpoints
- Chapter 18. Sectioning
- Chapter 19. Animation
- Chapter 20. Reviewing
- Chapter 21. Object Manipulation
- Chapter 22. Interface
- Chapter 23. Tools
- Chapter 24. Options
- Chapter 25. DataTools
- Chapter 26. Getting Help
- Part 4. Using Presenter
- Part 5. Object Animation
- Part 6. Using TimeLiner
- Glossary
- Index
When positioning a model relative to sea level, the height of the Google Earth reference points
must also be measured relative to sea level. When positioning a model relative to the ground, the
Google Earth reference points must be measured relative to the ground.
Google Earth always places new placemarks at an altitude of zero, irrespective of whether that is
relative or absolute.
3. Collapse on export allows different levels of collapsing parts of the model hierarchy in the exported
file.
• None ensures the whole heirarchy is exported
• All objects collapses everything into one node
• Files collapses each file into one node
• Layers collapses each layer into one node
4. Limit number of Polygons should be enabled to restrict the amount of geometry exported into the
output file. Geometry is selected on the basis of taking the most obvious objects in preference to the
fine detail. If the exported file is too large for Google Earth to display, try enabling this and reducing
the number of polygons. View, Scene Statistics in NavisWorks shows the number of triangles
and/or lines in the current project. By setting a polygon limit you are choosing to export only some of
these items.
Note:
Google Earth's ability to handle large numbers of polygons is far more limited than NavisWorks.
Hence it is worth noting that currently Google Earth will consider 1,000,000 polygons as being a
big model.
5. The Origin position values are the first pair of reference points on the Google Earth surface, and
must always be defined. The NavisWorks reference point will always be positioned to exactly overlay
the Google Earth reference point.
Second and Third reference points can be used, and if enabled then the position and orientation of
the model can be more accurately defined.
6. Use the Import buttons to read-in saved placemark locations from KML files exported from Google
Earth.
The Origin Import button differs slightly from the other two; if the KML file contains multiple
placemarks, this button will offer the user the choice of importing second and third reference points if
available. The other two buttons will only import a single reference point.
7. The Pick buttons allow the reference point locations to be selected in the main 3D view.
These points must be visible in the main 3D view prior to exporting, as once the KML Options dialog
box is open you will not be able to navigate before picking.
Note:
You may wish to use View, Split to split the main 3D view enabling you to have separate views of
each reference point.
File Management
70