Skip to main content
I use the reprojector to transform a MapInfo table from WGS84 to EPSG:3857 to perform some area calculation in meters and then I wrote the table in WGS84 using the writer coordinate system option.

 

 

When I copied some features from a backup table that was created before the preceding process into that output table, I see that some nodes are not snapped anymore, just like if nodes were moved very slightly.

 

 

I suspect the reprojection could maybe round the coordinates. Is it something someone have already experienced?

 

 

Well,

 

 

If  the original data has fixed length coordinates(how can it else..lol) , say 6 or 9 decimals after comma) reprojector might indeed have introduced (very slight) translation

 

 as fme internaly does not limit itself to said fixed decimals. (more to machine limits)

 

 

It is highly improbalbe that all or any coordinates are complient to any numbertheoretic formal system...

 

 

Actually any matrixtransformation might introduce such.

 

 

You can test it with an arc, famous for such occurences.

 

Create an arc using the transformer, add a random angle.

 

 

Coerce to lines and then try to reattach them..mostly it will refuse latter.

 

 

You can increase the snapping tolerance of course.
Hi,

 

 

depending on the formula used for the reprojection your coordinates could certainly shift or drift somewhat. If you're only reprojecting to calculate areas, you might be better off by doing something like this:

 

  1. GeometryExtractor to store original geometry in an attribute
  2. Reproject
  3. Calculate area
  4. GeometryReplacer to revert to orginal geometry
On a general note: Safe recommends using the CSMapReprojector rather than the Reprojector if precision is important. It has a few more options to control how the reprojection is done for certain transformations.

 

 

David

Reply