Skip to main content
Solved

Using GridinquestIIreprojector transformer to project to lat lng

  • November 6, 2017
  • 2 replies
  • 20 views

When using the GridInquest11Reprojector to project data from irish grid to ETRS89 Geodetic the following fatal error occurs "Source coordinate system 'Irish Grid' cannot reproject to destination coordinate system 'ETRS89 Geodetic', either 'Out of Area' coordinates or invalid coordinate system parameters Reprojector: Reprojection failed" This doesn't happen when reprojecting the same data set using the GridInquestReprojector. Only the first pair of co-ordinates appears to be projected when using the GridInquest11Reprojector as per the extract from the error log below.

Geometry Type: IFMELine

Number of Coordinates: 78 -- Coordinate Dimension: 2

(-6.5027536642668426,53.275450616997503)(299914.2325,226047.6043)(299912.3574,226060.10490000062)(299909.2323,226072.6055)(299909.8573,226083.8561)

(299911.1074,226098.23169999942)(299920.4828,226106.9821000006)(300232.9973,226190.1109)(300303.6255,226166.9849)(300321.7513,226161.9846)

...Skipping coordinates...

Is this expected behaviour??

Best answer by mark2atsafe

Are you using FME2017.0 or earlier? If so, can you try in FME2017.1? There were a few updates around out of area coordinates for that release. I'm hoping it will have fixed whatever the issue is here. If not, then please let us know and I can investigate further.

This thread also might provide some background information.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

mark2atsafe
Safer
Forum|alt.badge.img+56
  • Safer
  • 2554 replies
  • Best Answer
  • November 6, 2017

Are you using FME2017.0 or earlier? If so, can you try in FME2017.1? There were a few updates around out of area coordinates for that release. I'm hoping it will have fixed whatever the issue is here. If not, then please let us know and I can investigate further.

This thread also might provide some background information.


  • Author
  • 1 reply
  • November 7, 2017

Are you using FME2017.0 or earlier? If so, can you try in FME2017.1? There were a few updates around out of area coordinates for that release. I'm hoping it will have fixed whatever the issue is here. If not, then please let us know and I can investigate further.

This thread also might provide some background information.

Thanks Mark 2017.1 worked like a charm