Example_Shapes

Builds an absolute shape.

Builds a box shape.

Builds a checkerboard shape.

Builds a circle shape.

Builds a cubemap shape.

Builds a shape from a file.

Builds a shape that is transformed from one coordinate system to another.

Builds a graph shape.

Builds a group shape.

Builds an inverted shape.

Builds a shape that is transformed by a matrix.

Builds a shape with an aggregated distance field that uses maximum distance values.

Builds a triangle mesh shape.

Builds a shape with an aggregated distance field that uses maximum distance values.

Builds a shape with a distance field offset.

Builds a point soup shape.

Builds a complex polygon shape with a hole.

The internal representation of complex polygon shapes uses indexed geometry and a spatial acceleration structure.

Builds a simple polygon shape without holes and a large number of vertices.

The internal representation of simple polygon shapes with many vertices uses non-indexed geometry and a spatial acceleration structure.

Builds a simple polygon shape without holes and a small number of vertices.

The internal representation of simple polygon shapes with few vertices uses non-indexed geometry and no spatial acceleration structure.

Generates some vector shapes to illustrate how spatial distortions relate to the coordinate system that is used by shapes.

Centered at the given coordinates, some heightmap shapes and pixel pyramid shapes are generated using scene ⁱⁿ and added to shapes ⁱⁿ:

The recommended way for putting shapes onto the terrain in an accurate way is via the RED and GREEN approaches, using any appropriate map projection for the task at hand (for example IScene.Topocentric).

The BLUE approach is not recommended, as it suffers from distortions that are inherent to the cubemap projection and thus cannot be avoided: for example, circles becoming ovals and line thickness varying by up to 50%.

The YELLOW approach should only be used if the distortion of the distance field is not of relevance: for example, when using distance offsets for visual shape styles for which varying line thickness (see BLUE) is not a concern.

The CYAN and MAGENTA approaches should only be used for use-cases where high accuracy is not required. For non-equator locations, the axes of a geographic coordinate system will have different scales in the geocentric frame, so circles will become ovals and line thickness may vary.

_2 overloads

Writes all example shapes to the given directory.

This method will call BuildFile and pass a path to a file named polygon.shp, which must be present in the given directory ⁱⁿ. Any shapefile will do, but the original reference shapefile may be downloaded from here:
https://github.com/paleolimbot/shp/blob/master/inst/shp/polygon.shp

Writes all example shapes to the given directory.