Skip to main content
  • EN

Using generic feature reader to access a JPEG via a URL, that is an attachment for an ArcGIS Portal feature layer and requires authentication: this works well when explicitly stating the URL as the Dataset as the reader has the option to network authenticate in this mode. However, when the URL is supplied within an attribute, the reader has no authentication option and so the self same JPEG as above will fail with the message :

 

2022-06-29 16:47:51| 0.1| 0.0|ERROR |JPEG reader: `\\AppData\\Local\\Temp\\1\\wbrun_1656380366772_18540\\fmetmp_4\\TempFS_1656478070812_2916\\4' exists but could not be opened. File contents may be invalid, or the file format may not be supported

2022-06-29 16:47:51| 0.1| 0.0|ERROR |JPEG reader: Failed to open the dataset '\\AppData\\Local\\Temp\\1\\wbrun_1656380366772_18540\\fmetmp_4\\TempFS_1656478070812_2916\\4'. Please ensure source data is valid and correct reader is selected

2022-06-29 16:47:51| 0.1| 0.0|ERROR |A fatal error has occurred. Check the logfile above for details

 

Can also recreate this sequence by explicitly stating the URL, and switching off authentication - failure is the same.

 

Is the missing authentication switch a bug, or oversight? Can it be made available when supplying Dataset value within an attribute?

 

I am using Desktop version: FME(R) 2021.0.0.0 (20210305 - Build 21302 - WIN64)

Hi @ridleyj​ thanks for bringing this to our attention. I wouldn't say this is a bug as this isn't something we've implemented in FME before, but definitely something I think we should enabled for our users.

I've opened an enhancement request for this to get this functionality added to the JPEG Reader. The issue number is FMEENGINE-74093 for your reference. If a change is released in a new version of FME, we'll notify you here!

Following up on this @danminneyatsaf - I can force the authentication switch to be available by first deconstructing the URL attribute value to remove the ‘https://’ prefix, then when setting up the reader, I use a concatenation in the dataset parameter as in <fixed value><attribute value>: e.g.

‘https://’<URL_remaining_suffix>

So, then the dynamic portion is pulled in along with the https prefix, thereby enabling the authentication as FME now “recognizes” that there is a web resource to read..

Cheers

@ridleyj great to hear you have a workaround in place! If you’re able to upgrade to a newer version of FME, it looks like this functionality was also added in FME 2023.0 - Build 23109.

 

Reply


Community Stats

30,352
Posts
115,344
Replies
38,087
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.