Skip to main content

Hi there,


Depending upon their source Coordinate Systems in FME may or may not have EPSG codes matched to them.


For example if our user picks NZGD2K.MountEden from the list I can use the CoordinateSystemDescriptionConverter transformer to extract the EPSG code and use it in the workspace. However if they choose MOUNT_EDEN_2000 then there is no EPSG code associated with it and the CoordinateSystemDescriptionConverter returns nothing.


Would it be possible to sync the various coordinate systems so that all available information is available to FME no mater which CS version they choose? I am not able to limit the end users choice in the Server app as I need to cater for all possible coordinate systems.


I understand the different coordinate systems have different "metadata" with them, depending upon their source, however this can lead to an inconsistent experience for the end user.


Regards,

Marc

Awhile ago ​@daveatsafe suggested I use the PROJReprojector, and today I’ve finally come back around to this issue and confirmed: it works with all EPSG codes I need. Reading through it’s doc page, the transformer should work for most anyone else too since it’s using PROJ Library 9.5.0, which is up to Sept 2024.

 


Awhile ago ​@daveatsafe suggested I use the PROJReprojector, and today I’ve finally come back around to this issue and confirmed: it works with all EPSG codes I need. Reading through it’s doc page, the transformer should work for most anyone else too since it’s using PROJ Library 9.5.0, which is up to Sept 2024.

 

Warning: there’s a serious bug in some versions of PROJReprojector in FME Desktop (Form) - trying to type in the [destination coordinate system] field instead of using the drop down picker will induce a freeze and rapid memory leak, leading to a hard FME crash.

Update your FME to FME 2024.1.1.1 or higher to remove the problem. You can download the latest FME from safe.com/download.