Hi @r_huesken​,

Thanks for your question! I don't have an answer on this one at the moment, but if the data is proprietary it might be worth reaching out to your FME Reseller for more help on it.

Hi,

Thanks for the reply. I accidentally copied the wrong error message. The error only occurs when reading the TIN, the constraints and the points work well. The actual message for the TIN is:

'No geometry mapping entry found for 'wkb_multi_surface_xyz'

I'll check with the owner of the data if it is ok to share, or contact my reseller instead.

The geopackage causing the problem is included in this file. I hope somebody at Safe is able to assess the problem.

When using the OGC Geopackage reader, and selecting the following layer (see reader parameters dialog screenshot), I get the abovementioned error.

I'm using FME(R) 2020.1.0.1 (20200710 - Build 20596 - WIN64) and the OGC Geopackage

Hi @r_huesken​, I see your comments and I'll be taking a closer look into this very soon, sorry for the delay, there's a bit of catch up from the holidays. You had mentioned that the data was proprietary, would you like me to remove the post with the file download for you?

​Hi @r_huesken​,

It doesn't look like we support TINs in the Geopackage reader just yet but my colleagues were able to find a workaround using the SQLite reader and then replacing the geometry with well known binary to suceessfully read the TIN (thanks to Mark S and Jake!).

I've attached the workspace template here, please give me a shout if the data needs to be removed from the template. I've wrapped up Jake's workflow in a custom transformer so you should be able to just run it and the AttributeFilter will filter out your feature types to TIN, Point, and Constraint. Right click > Edit on the custom transformer if you're interested to see what's inside, but you should be able to work with the TIN without having to make any changes to the custom transformer.

Hi @jovitaatsafe​ 

Sorry for the late reply, I had to look after some other issues .

Thanks very much for both the explanation and the work around. This is not a straightforward solution, and it will save me a lot of time transforming the data for our client.

I'd appreciate if you could remove the data from the template, since I guess this solution may be useful for other FME customers as well.

Richard.