Skip to main content
  • EN

Prior in FME Server 2016.1, CANA83-10TM115-EAP is recognized by FME SVR.

Predefined coordinate system `CANA83-10TM115-EAP' (Alberta NAD83; 115 deg West, positive easting coordinates) matches dataset coordinate system

 Now in FME Server 2019.1,  here is the log:

Predefined coordinate system `10TMAEPFOREST_83' () matches dataset coordinate syst

Which is not the one set in the submitted gdb. 

This is specific to FME Server, when running locally, CANA83-10TM115-EAP is set correctly within FME properties.

 

 

This is not a custom coordinate system so it should not be added to the Engine/CoordinateSystems repository according to the documentation

 

 

Any thoughts anyone? tks

Hi @philll,

FME reads the Esri WKT coordinate system from the GDB and maps it to an FME coordinate system upon reading the data. It appears that your FME Server may have a user coordinate system defined that maps to the same WKT, using an .db exception file. In this case, FME will use the user coordinate system over the standard ones.

Please check your FME Server Resources/Engine/CoordinateSystemExceptions folder for any .db files that might map the GDB coordinate system to 10TMAEPFOREST_83.

Hi @daveatsafe

 

thanks for your answer!

 

 

Your answer makes sense because this coordinate system 10TMAEPFOREST_83 is not listed in the FME coordinate system gallery (either FME 2016 or 2019 (we are upgrading solution from 2016 to 2019))

 

 

However there is no .db files under CoordinateSystemExceptions or under others Engine sub-folders neither in FME Server 2016

 

 

Do you see any other way FME would use a .db file or via other exceptions file?

 

we are using Microsoft SQL Server 2016.

 

 

 

Reply


Community Stats

30,177
Posts
114,555
Replies
37,843
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.