Skip to main content

What is the process for ensuring that a custom coordinate system defined using the recipe from ​@daveatsafe below is reliably used by all members of a team using FME Desktop and also Server?

(better yet: implement Update all available Coordinate Systems with EPSG Codes so it’s not necessary)

 

You can set up a shared network folder to store the custom coordinate system definitions, then attach it to all your FME installations:

  • In Workbench, choose Utilities - FME Options
  • Pick Default Paths
  • Add the shared network folder to Shared FME Folders
  • Do this for all the computers running FME

Once this is set up, any custom coordinate system added to the network folder will be available to all FME users.


Thanks Dave. What about Server?

Edit: and what is the precedence order if custom possibly conflicting or overwriting each other coordinate systems exist in both user profile and the shared folder?


Hi ​@mattwilkie, I can help with your first question. When publishing a workspace, coordinate systems or other resources can be included in the upload:

Coordinate systems can also be uploaded to Resources/Engine/CoordinateSystems, which will make them available to all workspaces on the server. This docs page has more info.


Hi ​@mattwilkie, I can help with your first question. When publishing a workspace, coordinate systems or other resources can be included in the upload (...) Coordinate systems can also be uploaded to Resources/Engine/CoordinateSystems, which will make them available to all workspaces on the server. This docs page has more info.

 

Thanks ​@zoe.forbes! Once I sort out once and for all the our workstation projection issues I will try that out.