STAC Asset Reader

Hello ​@jlw_tyrens, so there are two different levels of authentication that may be used for STAC. One at the dataset level and the other at the asset level. I believe authentication support has been implemented by service, meaning we can only read protected STAC datasets from the named services you see in the STAC Type parameter.  Can you let me know which STAC assets you are trying to read? Happy to help, Kailin. 

Hello Kailin! I’m trying to read STAC Assets from https://api.lantmateriet.se/stac-vektor/v1/, it is open data from the Swedish mapping, cadastral and land registration authority. I can consume the data in a stac browser

Hello ​@jlw_tyrens, thank you for sharing the URL. I think this is a case where authentication has been enrolled at the asset level, meaning you can search and query through the dataset without authenticating, but you require authentication to access or retrieve the actual assets themselves. The same can be seen in browser, can query through collections/items, but prompted to sign in at https://dl1.lanmateriet.se when entering the asset zip/download URL. I have filed an issue with our development team for further investigation: FMEENGINE-86391. Let me know if you have any questions! Happy to help, Kailin.

Hello ​@jlw_tyrens, thanks for your patience! We took some time to investigate this issue and there turns out to be a few things to discuss. We would appreciate any feedback you can share!

Firstly, the asset type is application/zip, which is not supported by the reader at this time. Because we cannot determine the underlying content(s) of the zip file until runtime, there is no way for FME to read and produce features from it. 

Secondly, this asset requires a type of authentication that is not supported in FME Form. 

Since the STAC asset in question is a Geopackage, an ideal scenario would be to use the STAC Metadata Reader to query for the zip asset URL and HTTPCaller/FeatureReader to consume the data. 

For this to work successfully, we would first need to look into adding the appropriate authentication support. In order to support your authentication type, we would need access to account (username/password) credentials for development. If this is something you would like to work with us on, please submit a support case. Happy to help, Kailin.