This tutorial contains GIF images.
If they fail to load please visit the help center via web browser.
You can zoom this page with Ctrl+.

In order for PVcase to successfully evaluate terrain data, it has to work with clearly distinguished objects that indicate topographical height information.

Some of the topographical surveys have many different indicators clustered together on the same layer which can cause errors in terrain recognition.

Before generating a layout it is best to create a Topography mesh by selecting terrain data that will be used for layout generation. To investigate the mesh and PVcase's estimation of the terrain - use the 3DORBIT command of AutoCAD.

Let's review an example terrain survey that has some issues. As you can see in the example below, once the mesh is generated, some steep and unrealistic undulations are indicated and must be regarded as false.

As I check these areas I can identify issues that can cause such extremities. Here are some of the sample ones that usually come up:

Solution: Manually change by hand or use the FIND command to change the decimal comma into a dot. 

Solution: Manually change the layer of tree height measurements.

Solution: Manually put the indicative numbers on another layer.

After these issues are resolved do not forget to reselect terrain data and then we can generate the Topography mesh again and evaluate the results.

Another common issue with contour line topographical surveys is that some of contour lines are missing elevation data and in result rendering whole topography unusable. If terrain mesh shows extremities or even the selection of topography cannot be done (example below), then contour lines needs to be fixed.

Once again, the best option is to assess the topography in 3D view by isolating topography and rotating in with 3DORBIT function. Most of the time some contour lines will be visually seen as faulty. 

Simply placing these polylines on another layer or giving elevation data to it will fix the issue.