Trim precision in numbers of test geometries in WKB files

[Mateusz Łoskot]

Currently, OGR tests fail under Windows because of FP arithmetic and precision instability. Here are some examples:

TEST: wkbwkt_geom: 3 ... fail
    WKT from WKB (GEOMETRYCOLLECTION (POINT (5.001213489449583 9.99853131378768),POINT (5.001213488867506 7.998531316843582),LINESTRING (3.001213508250658 8.998531263452605,4.001213498995639 9.99853128765244,5.001213489158545 8.998531314733555,4.001213498297148 7.99853129083931),POLYGON ((4.001213498297148 7.99853129083931,4.001213498646393 8.998531289384118,3.001213508250658 8.998531263452605,2.001213517622091 8.99853123696812,2.001213517331053 7.998531238554278)))) does not match clean WKT (GEOMETRYCOLLECTION (POINT (5.001213489449583 9.99853131378768),POINT (5.001213488867506 7.998531316843582),LINESTRING (3.001213508250657 8.998531263452605,4.001213498995639 9.99853128765244,5.001213489158545 8.998531314733555,4.001213498297147 7.99853129083931),POLYGON ((4.001213498297147 7.99853129083931,4.001213498646393 8.998531289384118,3.001213508250657 8.998531263452605,2.001213517622091 8.99853123696812,2.001213517331053 7.998531238554278)))).

and

TEST: wkbwkt_geom: 8 ... fail
    WKT from WKB (POINT (2.001213516748976 5.998531240940793)) does not match clean WKT (POINT (2.001213516748976 5.998531240940792)).

The proposed fix is to trimming the precision in the .wkb files causing problems. The OGR code should ideally stay untouched.

[Mateusz Łoskot]

Norman suggested to try some compilation flags /Op or /fp:precision on Visual C++ and -ffloat-store on GCC.

[Mateusz Łoskot]

The test data has been fixed and now all tests pass under Windows.