id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
10868	Intersecting integer polygons produces incorrect or self-intersecting result	starinshak1@…	Barend Gehrels	"I've noticed several instances of Boost.Geometry returning incorrect or self-intersecting polygons when working in integers (32 and 64 bit).

EXAMPLE:
Polygon A has vertices
(42817136,-3774506), (43029074,-3929862), (31446819,18947953), (30772384,19615678), (30101303,19612322), (30114725,16928001), (33520458,6878575), (35332375,2413654), (35725796,2024148), (42817136,-3774506)

Polygon B has vertices
(-33386239,-33721784), (33721785,-33386239), (33386240,33721785), (-33721784,33386240)

Intersecting Polygon A and Polygon B returns:

A correct but self-intersecting polygon using Boost 1.55

An incorrect polygon using Boost 1.57 and int64_t coordinates

An incorrect and self-intersecting polygon using Boost 1.57 and int32_t coordinates.

For both Boost 1.57 tests, I enabled BOOST_GEOMETRY_NO_ROBUSTNESS to avoid floating point rescaling."	Bugs	new	To Be Determined	geometry	Boost 1.57.0	Problem			barend@…