You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
during topological operations (overlap, intersect, etc) it is in general necessary to "segmentise" polygons, i.e. increasing the density of points that define the outline of the polygon.
For example:
A square in some local projection is defined by 4 points. In the local projection, this points are correctly connected by straigth lines.
When this square is warped to another projection, only the 4 points are projected -- the lines between the points will be drawn again just as straigt lines -- although the should be curved to represent the area and extent of the polygon correctly.
this troubles then the correct execution of topological operations
the remedy for this is to "densify" or "segmentise" the lines by adding additional points along the lines in 1) (libraries can do this already), and project all the points. These are then connected in a new projection with (wrong) straight lines, but as they are much shorter, the error is much less crucial
question is: how to control the correct segmentation length? user defined? related to the pixel raster size of a RasterGeometry()?
The text was updated successfully, but these errors were encountered:
during topological operations (overlap, intersect, etc) it is in general necessary to "segmentise" polygons, i.e. increasing the density of points that define the outline of the polygon.
For example:
the remedy for this is to "densify" or "segmentise" the lines by adding additional points along the lines in 1) (libraries can do this already), and project all the points. These are then connected in a new projection with (wrong) straight lines, but as they are much shorter, the error is much less crucial
question is: how to control the correct segmentation length? user defined? related to the pixel raster size of a RasterGeometry()?
The text was updated successfully, but these errors were encountered: