Crs.IntersectLineSegments Methods

Returns the points where two line segment intersect.

Overload List

IntersectLineSegments(PointCollection line1, LineType line1Type, PointCollection line2, LineType line2Type)

public PointCollection IntersectLineSegments (
    PointCollection line1,
    LineType line1Type,
    PointCollection line2,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (GreatCircle or RhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are GreatCircle and RhumbLine (the GreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by UnprojectToLongLat and ProjectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

IntersectLineSegments(Point line1Start, Point line1End, LineType line1Type, Point line2Start, Point line2End, LineType line2Type)

public PointCollection IntersectLineSegments (
    Point line1Start,
    Point line1End,
    LineType line1Type,
    Point line2Start,
    Point line2End,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (GreatCircle or RhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are GreatCircle and RhumbLine (the GreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by UnprojectToLongLat and ProjectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

IntersectLineSegments(IEnumerable< Point > line1, LineType line1Type, IEnumerable< Point > line2, LineType line2Type)

public PointCollection IntersectLineSegments (
    IEnumerable< Point > line1,
    LineType line1Type,
    IEnumerable< Point > line2,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (GreatCircle or RhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are GreatCircle and RhumbLine (the GreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by UnprojectToLongLat and ProjectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

Platforms

Windows, Linux, Android

Crs::intersectLineSegments Methods

Returns the points where two line segment intersect.

Overload List

intersectLineSegments(const PointCollectionPtr& line1, LineType line1Type, const PointCollectionPtr& line2, LineType line2Type)

public:
PointCollectionPtr intersectLineSegments (
    const PointCollectionPtr& line1,
    LineType line1Type,
    const PointCollectionPtr& line2,
    LineType line2Type
) const

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (LineTypeGreatCircle or LineTypeRhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are LineTypeGreatCircle and LineTypeRhumbLine (the LineTypeGreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

intersectLineSegments(const Iter& line1First, const Iter& line1Last, LineType line1Type, const Iter& line2First, const Iter& line2Last, LineType line2Type)

public:
template< class Iter >
PointCollectionPtr intersectLineSegments (
    const Iter& line1First,
    const Iter& line1Last,
    LineType line1Type,
    const Iter& line2First,
    const Iter& line2Last,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (LineTypeGreatCircle or LineTypeRhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are LineTypeGreatCircle and LineTypeRhumbLine (the LineTypeGreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

intersectLineSegments(const Point& line1Start, const Point& line1End, LineType line1Type, const Point& line2Start, const Point& line2End, LineType line2Type)

public:
PointCollectionPtr intersectLineSegments (
    const Point& line1Start,
    const Point& line1End,
    LineType line1Type,
    const Point& line2Start,
    const Point& line2End,
    LineType line2Type
) const

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (LineTypeGreatCircle or LineTypeRhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are LineTypeGreatCircle and LineTypeRhumbLine (the LineTypeGreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

Platforms

Windows, Linux, Android

Crs.intersectLineSegments Methods

Returns the points where two line segment intersect.

Overload List

intersectLineSegments(PointCollection line1, LineType line1Type, PointCollection line2, LineType line2Type)

public final PointCollection intersectLineSegments (
    PointCollection line1,
    LineType line1Type,
    PointCollection line2,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (GREATCIRCLE or RHUMBLINE). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are GREATCIRCLE and RHUMBLINE (the GREATCIRCLEAPPROX is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

intersectLineSegments(Point line1Start, Point line1End, LineType line1Type, Point line2Start, Point line2End, LineType line2Type)

public final PointCollection intersectLineSegments (
    Point line1Start,
    Point line1End,
    LineType line1Type,
    Point line2Start,
    Point line2End,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (GREATCIRCLE or RHUMBLINE). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are GREATCIRCLE and RHUMBLINE (the GREATCIRCLEAPPROX is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

intersectLineSegments(java.util.Collection< Point > line1, LineType line1Type, java.util.Collection< Point > line2, LineType line2Type)

public final PointCollection intersectLineSegments (
    java.util.Collection< Point > line1,
    LineType line1Type,
    java.util.Collection< Point > line2,
    LineType line2Type
)

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (GREATCIRCLE or RHUMBLINE). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are GREATCIRCLE and RHUMBLINE (the GREATCIRCLEAPPROX is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

Platforms

Windows, Linux, Android

Crs.intersectLineSegments Methods

Returns the points where two line segment intersect.

Overload List

intersectLineSegments(line1, line1Type, line2, line2Type)

PointCollection intersectLineSegments ( line1, line1Type, line2, line2Type )

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (LineType.GreatCircle or LineType.RhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are LineType.GreatCircle and LineType.RhumbLine (the LineType.GreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

intersectLineSegments(line1Start, line1End, line1Type, line2Start, line2End, line2Type)

PointCollection intersectLineSegments ( line1Start, line1End, line1Type, line2Start, line2End, line2Type )

Parameters

Return Value

Remarks

Two lines are given, each with exactly two points, together with their types (LineType.GreatCircle or LineType.RhumbLine). The returned list of points will contain the points where the lines intersect. If the lines are of the same type, they can intersect at most once. However, a great circle can intersect a rhumb line up to three times (even if the segments are short); see the map below.

Line type and accuracy

The possible line types are LineType.GreatCircle and LineType.RhumbLine (the LineType.GreatCircleApprox is not implemented). However, if the projection is non-georeferenced, then the line segments are regarded as a straight lines in the plane, giving unknown accuracy on Earth. Otherwise, the line segments are unprojected to LongLat, then the intersections are computed in LongLat, and they are finally projected. Disregarding the errors that may be caused by unprojectToLongLat and projectFromLongLat, the intersections are found with submillimeter accuracy. However, before the calculations are done, both line segments are extended by 1 millimeter at both ends. This should ensure that the method will not overlook a valid intersection that is very close to one end of an original segment, although it may report a spurious intersection that really occurs slightly beyond one end of an original segment. This slight overreporting of intersections is usually better than possibly overlooking a valid intersection.

Intersection angle and error propagation

The z value of each intersection point does not mean altitude: it is the angle of intersection in degrees, in the range 0° to 90°. A small intersection angle means that small errors in the input coordinates can cause large errors in the intersection points. If the input coordinates may have an error err, then a point where the lines intersect with the angle alpha may have an error of err/tan(alpha/2). For example, if err is 1 meter and the alpha is 5°, then the intersection point may have an error of 1/tan(2.5°) = 23 meters.

Intersection points and intersection angles, computed by the intersection methods of the Crs class.

Platforms

Windows, Linux, Android