Why do I get Warning and "Assumed Default" when Translating from GDA94 to GDA2020

Does this help? https://li360.pitneybowes.com/s/question/0D58000003ugyOvCAI/gda2020-datum-support-for-australia I note V17 is due this month.

FME added full support for GDA2020 in version 2018 (released 14th March this year)

Hey Mark,

I have just installed FME2018 and run the same reprojection function for the GDA94 to GDA2020 and still receive the error "

MapInfo does not support datum/ellipsoid `GDA2020' -- assuming default of WGS84". Why is there reference to MapInfo? Also, after you mentioned if my

MAPINFOW.PRJ file contains the code as seen in the link you posted, being:

https://li360.pitneybowes.com/s/question/0D58000003ugyOvCAI/gda2020-datum-support-for-australia

Regards,

Tony Jordan

OK, so this is where I am at with this issue.

I am running FME2018 also have 32bit V15 and 64 bit V17 MapInfo Professional installed with both versions having the GDA2020 datum within the source projection file and been tested to work. Using FME2018 I have tried reprojecting MapInfo tab files from GDA94 to GDA2020 and while the says it is 'successful' when I open the tab file in MapInfo I notice that MapInfo says the file is in WGS84 datum. The baffling thing is even though that the data has had the correct shift applied where the data is moved approx 1.7metres in a NNE direction, just that the file datum is incorrect.

I am still getting the below warning in FME when doing the translation, the pain is that while the data has made the correct shift the actual datum of the file is still incorrect.. HELP!!!

WARN |MapInfo does not support datum/ellipsoid `GDA2020' -- assuming default of WGS84

I can confirm that this is still an issue in the latest version of FME (2018.1.0.3 b18567). Support have (23rd Nov) raised a problem report.

So it turns out you can write to MIF or TAB (via our MITAB writer) and all will be well, even in FME 2018.1.

The issue is that the official libraries we have for both MapInfo Extended and MFAL TAB don't know of the new datum yet.

We're in touch with PB and our idea is that when we get new libraries we'll backport to 2018.1 unless there is some huge issue, and of course, FME 2019 would have the fix. We don't have an ETA for the new libs but will keep folks posted via this question when we have updates.

Thanks for the feedback Dale.

I have just checked my writer ensuring it is set to MITAB, which it is, then re-run the re-projection with the Parameters as seen in the attached screenshot. I still receive the message " WARN |MapInfo does not support datum/ellipsoid `GDA2020' -- assuming default of WGS84". I just don't understand what is wrong..

We are running the FME version 2018.0.0.1 (20180328 - Build 18295 WIN64)

Regards,

Tony Jordan

Currently having the same level of luck as you with the MITAB Reader/Writer. I've resurrected the following thread on the official GDA2020 forum and asked for a working example. http://gda2020.invisionzone.com/topic/15-fme-transformers/#comment-154

Short answer: GDA2020 support for MapInfo requires FME 2018.1. FME 2018.0 did not include this aspect.

@markdmclean: I've attached my working example, both as an image and a zip with everything inside, including output. I understand this must be frustrating, and I'd be willing to do a call or screenshare with you if we and our Experts team (@AndreaAtSafe) can find a mutually workable time.

mitab_gda2020_zone_54.zip

Some success!

To date I have been testing in FME version 2018.0.0.1 (20180328 Build 18295 WIN64). This morning I downloaded and run the same Re-Projection tasks in version FME(R) 2018.1.1.0 (20181107 - Build 18567 - WIN64).

I believe the previous version was causing the headaches, would this be correct? While the previous/older version mentioned above still had the GDA2020 to select from it appears the code behind the scenes was not correct!?!

I have tested overlaying our vector and raster data with the new GDA2020 datum in both 64bit MapInfo and (32bit MapInfo with updated .prj file) and all is sweet! Honestly this had me snagged..

Should the guys at Pitney Bowes be informed?

Thanks for your work and patients.

Regards,

Tony Jordan

@tonyjordan: Yes, as per my message yesterday, FME's MapInfo support for GDA2020 was added only in FME 2018.1. What I'm only figuring out now is that this issue is likely the crux of the confusion. We'll make sure to alert Pitney Bowes today.

To be clear: To successfully write GDA2020 to MapInfo TAB, you have to do two things: (1) Use FME 2018.1.0.0 or newer, and (2) Use the MITAB writer (and not the MAPINFO or MAPINFO_EXTENDED ones). We expect to address (2) shortly, and will report back, but those fixes will require an even more recent version of FME (yet to be produced).

Good news! I gather the official release of 2019 isn't too far away so I'll wait for that. Thanks for the update.

I have added a comment on the issue on the official GDA2020 forum - http://gda2020.invisionzone.com/topic/15-fme-transformers/#comment-164

Hi Andrea,

Will there be any licensing implications if I remove my current version of FME Professional Edition build 18567 and install the 2019 beta?

Regards,

Tony Jordan

Hi @tonyjordan,

I would recommend to keep your current official release as FME Betas are not intended for use in a production environment. It is possible to have multiple versions of FME installed on the same computer with no problem.

To try out the new functionality, I would suggest installing FME 2019 beta alongside the official release. To do this, you'll want to install the beta in a different directory. For more information, please see this article about installing multiple versions of FME.

- Andrea

Hi there,

I was wondering if anyone could please tell me if there has been any progress with the MapInfo TAB (MAPINFO) writer and it’s ability to write to the GDA2020 datum? If so, approximately when will this be released?

I have just installed FME 2019.2 (build 19801) and tried the MapInfo TAB (MAPINFO) writer for GDA2020, but it still reprojects to UTM Zone 55, Southern Hemisphere (WGS84). MITAB, MapInfo Extended and MIF/MID reproject to GDA2020 successfully. I only ask to help us decide whether or not to change our MapInfo writers to MITAB in our FME Workbenches or wait for a new release.

Regards,

Sonya

Hi @sonya,

Unfortunately, we are unable to upgrade the "MAPINFO" format due to third party library limitations. I apologize for the inconvenience and I hope the transition to one of the other MapInfo formats (eg. MITAB) for your transformations is smooth.

- Andrea

Thank you @andreaatsafe for getting back to me. Here is to a smooth transition!

Regards,

Sonya

Hi @andreaatsafe

I note Sonya's question above (or below!!) regarding MapInfo formats that support the GDA2020 datum. I was just wondering whether there had been any update on the other mapinfo formats, or is the mapinfo_extended the only one that to support the conversion from gda94 to gda2020?

Thanks very much

Jamie

Hi all,

I'm pleased to let you know that the latest FME 2019.2 and newer (Windows 64-bit only) has added GDA2020 support to the MAPINFO format.

I've also created an article that details what version of FME supports GDA2020 and MapInfo TAB format, which you can find here.

- Andrea