Sylvain,
>
> Indeed, the problem arises when I try to transform data (not just from
> PostGIS) with ogr2ogr. Transformation shapefile to MIF / MID or TAB
> poses the same problems: loss of precision on the coordinates.
Looking very quicly to the MIF driver, I see for example that a point is
wri
Hello and thanks for the answer.
I juste achieve some tests regarding to my question.
"Actually, it might not be a rounding effect at display time. Paul Ramsey
identified that when inserting data into a Postgis instance, we used the WKT
representation, thus introducing rounding problem effects.
Selon Sylvain MAFFREN :
> Hello and thank you for that answer.
>
> I think if it was a rounding effect that appears at display time when
> ogrinfo outputs the WKT representation, I should have the same results
> on several data but this is notthe case.
>
> Indeed,by querying topology between the s
Hello and thank you for that answer.
I think if it was a rounding effect that appears at display time when
ogrinfo outputs the WKT representation, I should have the same results
on several data but this is notthe case.
Indeed,by querying topology between the source layer and output layer
(ch
Le lundi 20 juin 2011 23:49:18, Sylvain Maffren a écrit :
This might be just a rounding effect that appears at display time when ogrinfo
outputs the WKT representation, but not affect the output data itself. Likely
993366.058 and 993366 are 2 decimal representations for the same
binary
Hi !
I apologize in advance for my english which I not very fluent. I have
some questions about the tool ogr2ogr (and also about gdalwarp and
gdal_translate) and the rounding of coordinates.
Let me explain:
Some databases (particularly IGN -- France databases) have coordinates
rounded to t
