In reports, geometries are used to construct spatial queries such as finding all the trees within a 10m of a span.

In order to run network reports and export geo data such as GeoJSON and shapefiles, the schema needs a specified geometry field. This geometry field associates a report row (including the object and it's report fields) to a geographical location. Most schemas have a built-in geometry field.

In other cases, you can specify a custom geometry field

In Neara, there are two types of geometries. The most common one is Coordinate Distance Geometry which corresponds to GeoJSON geometries:

The coordinates for these types are not exposed. As a result, these types are not directly modifiable or manipulatable. Instead, vector arithmetic can be performed by constructing vectors using vec2, vec3.

normalize(vec)

Returns a vector with the same direction as the specified vector and a magnitude of 1.

Vectors can be turned into geoJSON with these functions:

New geometries can be created using these functions:

The following functions let you use geometries to do spatial and other measurement queries.

Catenaries are another type of geometries exposed in Neara. You can manipulate them using:

Body functions are used for more complex geometries such as 3D meshes specified in OBJ file formats.

To upload your KML, DXF or OBJ file into Neara, click the (+) button at the right hand end of the tabs in any section of the workspace, and select Data File under the Tools section in the popup.

Once you have imported your file, a Body can be created with the function load_bodies(). The required argument is the Data File that should be parsed. Other optional arguments are available for further customisation. See in-app documentation for more information.

To position the Body within your network, use transform_body(). This function takes in the loaded bodies, and returns a copy that has been translated and rotated according to the specified arguments.

Bodies can be visualised and used to as inputs to perform measurement calculations.

The function returns a list of Body objects, derived from the source using the provided parameters. The source is either a (DXF or KML) data file or a blob ref.

There exists a hard limit on the size of each body, being 65,536 unique vertices. If any of the constructed bodies exceeds this limit, no bodies will be created.

Makes an uncapped radial body around the given cables or catenaries

Returns a copy of the body, with its geometry transformed according to the provided arguments.

The translation argument provides the ability to shift the body by any arbitrary amount. This will default to no translation if not specified.

The localX, localY and localZ arguments perform a change of basis before the translation is applied, allowing any transform to be applied.

For convenience, logical defaults are selected when only a subset of the three vectors are specified. This includes:

Upload a Data File with the name “test.obj”.

In a custom field on the Model, add the following function:

To shift the mesh to the top of the pole, we add the following custom field on the Pole:

or

Generates a 2D vector, given compatible-dimension components or a 3D vector. If built from a 3D vector it drops the Z component. The vector can have dimensional units and participates in dimensional analysis, much like scalars.

Example 1: 2D distance

Example 2: Absolute position

or

Generates a 3D vector, given compatible-dimension components. A 2D vector can be substituted for x and y.

Example 1: 3D distance

Example 2: Absolute position

Returns the normalized vector (dimensionless, length 1) unless the input is a zero vector in which case a zero vector is returned.

or

Generates a 3D polyline. All the components must have absolute-coordinate dimensionality.

Finds the closest points between the two objects and returns a distance measurement object.

The distance measurement object can be queried for a number of distance components and visualized.

If either a or b are lists, then returns the closest distance between anything in a to anything in b.

Example:

In a custom field on a Span, measure_distance(pole1, pole2) returns a distance measurement object between the two pole(s) of a span.

The distance object then has a number of useful fields, such as:

Note that these last two are NOT necessarily the smallest such values, i.e. horizontal_distance is the horizontal component of the closest 3D distance, it is not the closest possible horizontal distance.

make_outline(geometries, [concavity_radius: 20m, buffer: 10m])

Constructs an outline of the given geometries with buffer.

Extends the given catenary outwards from the closest endpoint so that it reaches the specified 2D location.

reproject(coord_data, [from_srid: srid, to_srid: srid])

Reprojects data between spatial references.

Example 1: Reproject a pole to WGS84 using implicit "from" SRID: reproject(pole.location, to: "4326")

Example 2: Reproject a pole to WGS84 using explicit "from" SRID: reproject(pole.location, from: model().srid, to: "4326")

Returns a grid of square polygons of the given size (world-aligned). Specify cover_model or cover_point_cloud to select the grid size.

Example:

Create a 100m world-aligned grid ensuring that every model object and every point is covered by a grid cell: make_grid(cell_size: 100m, cover_model: true, cover_point_cloud: true)

Creates a line string or multi line string, each item should be a list(vec2) or list(vec3).

Example 1: Create a LineString geometry on a Span:

Example 2: Create a MultiLineString on a StrainSection:

Example 3: Create a LineString geometry directly:

Example 4: Create a MultiLineString geometry directly:

Creates a polygon or multi polygon, each item is one polygon and should be a list(list(vec2)).

Example 1: Create a Polygon geometry with no hole:

Example 2: Create a Polygon geometry with one hole:

Returns the centroid of the given object/geometry.

Returns true if geom1 and geom2 intersect/overlap.

Returns a list of location vectors along the outline of the geometry at the given interval. \Point and MultiPoint are simply expanded into points.

Example:

returns a list of location vectors.

Queries a collection of geometric objects returning those that are within some distance of the given geometry, in order of closest to furthest.

The second argument can either be a geometry or a type that has a geometry field.

For example, using pole is equivalent to using pole.geometry.

Example: Find all poles within 10m of the given pole using: geo_query(model().Poles, pole, 10m)

Get the catenaries corresponding to the portions of the original catenaries within the specified ratio interval.

If start_ratio or end_ratio are outside the range [0.0, 1.0], the slices will be extended in to meet the specified ratio along their respective curves.

Examples:

Slices line in equal parts. Limited to 100 slices.

Returns the area of the convex hull of the given geometry

Creates wedge-shaped volumes pointing either downward (if downward = true) or upward using the endpoints (instead of the curves) of catenaries, where the angle between the two sides of each wedge is [angle] and the triangular face of each wedge is [height] tall.

Example on a span:

Returns the coordinate origin as a Vector3 of absolute distance values.

Example: origin().z + 100m returns 100m of altitude as an absolute value.