Class GeometryIntersection

Namespace: EncDotNet.S100.Datasets.Pipelines.Geometry

Assembly: EncDotNet.S100.Datasets.Pipelines.dll

True (full-geometry) intersection between a GeoQuery and an IS100Feature's geometry — the precise complement to the bounding-box test in Intersects(IS100Feature, GeoQuery).

public static class GeometryIntersection

Inheritance: object

GeometryIntersection

Inherited Members: object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.MemberwiseClone()

object.ReferenceEquals(object, object)

object.ToString()

Remarks

Where the bounding-box test answers "could these overlap?", this answers "do they actually overlap?" — point-in-polygon containment for area features (interior-ring holes honoured) and genuine segment crossing for the route-leg question "which features does this leg cross?". All maths is planar in lat/lon space, matching the precision used elsewhere in the tools surface; it is intended for ranking and membership tests over the span of a single dataset, not survey-grade geodesy.

The predicate is conservative: for the genuinely degenerate combination it cannot decide (a point query against a curve or point feature) it returns true so a precise pass never drops a bounding-box match it cannot prove disjoint. Surface geometry takes precedence over curve, which takes precedence over point, matching the rest of the tools surface.

Methods

Intersects(IS100Feature, GeoQuery)

Returns true when feature's geometry truly intersects query. Features without geometry never match.

public static bool Intersects(IS100Feature feature, GeoQuery query)

Parameters

feature IS100Feature
query GeoQuery

Returns