Context Navigation

Changes between Version 2 and Version 3 of Ticket #12314, comment 1

v2	v3
1	1	In non-cartesian coordinate systems the edges of Polygons are also shortest lines between points so e.g. the edge: `(0 89, 180 89)` intersects the north pole. In the case of the edge `(180 0, 0 0)` I'm not sure what the algorithm assumes but this edge is invalid. The reason for that is that there is infinite number of possible edges connecting these points in spherical and 2 possible edges in geographic (going through north or south pole). Either way I presume this is not what you had in mind.
2	2
3		You could fix the invalidity by adding additional point between the invalid edge, so: `POLYGON((0 89, 180 89, 180 0, 90 0, 0 0, 0 89 ))` but this is not what you wanted to do either.
	3	You could fix the invalidity by adding additional point between the endpoints of the invalid edge, so: `POLYGON((0 89, 180 89, 180 0, 90 0, 0 0, 0 89 ))` but this is not what you wanted to do either.
4	4
5	5	AFAIU what you wanted to do is to create a "rectangular" region (in spherical/geographic having edges being parallels and meridians) and that you should use your own rectangle representation adapted to Boost.Geometry Box concept or `bg::model::box` for this: