Hello, I am creating a workspace that will export photo (.jpg) and video (.mov) attachments from a FGDB. The FGDB contains a related table holding the attachments in blob format. Per the suggestion found here https://knowledge.safe.com/questions/58775/exporting-geodatabase-attachments-to-jpeg.html , I was able to use a FeatureMerger, RasterReplacer, and a JPEG Writer to successfully pull the photos out. I have isolated the "video attachment" records after merging the data with the related table via a Tester, but I am unsure how to proceed. Is it possible to write .mov or other video files from FME? I have not seen a writer for video formats (similar to the JPEG writer used to write the photos to file). Thanks!
Solved
Extracting video attachments from FGDB
Best answer by david_r
When using the AttributeFileWriter to write a binary file (such as jpeg or mov files), make sure that you're setting the target file encoding to "fme-binary":
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.
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.
Have you tried using the AttributeFileWriter to write the contents of the blob to disk?
I had not. I have it loaded up now, but am unsure what to attach to the Output port of the AttributeFileWriter. Any thoughts?
Hello all,
At a client I often fail to connect to their ESRI Portal, due to failing to verify SSL (see loggin below) on both FME Server and desktop.
Proxy settings in FME don't change the behaviour (always uses proxy). The Chrome browser thinks the certificate is o.k.
I can't disable ssl-verification in the Portal Reader, as suggested in the log, like it is possible to do in the HTTPCaller.. (see my idea for that).
Inspired by this reported problem I exported the certificate from Chrome, and imported it in $FME_HOME\jre\lib\security\cacerts on desktop.. (analogue to these instructions for server, section .pfx certificate, as the problematic server has a .pfx certificate).
This did not resolve the problem...
Does anyone have any suggestions???
Kind regards,
Martin
ArcGIS Portal Feature Service Reader: Using proxy http://proxy.####.intern:8080/
ArcGIS Portal Feature Service Reader: Using authentication type 'NTLM'
ArcGIS Portal Feature Service Reader: Logging into 'https://geoportaal.####.intern/portal/' as user '####\####'
ArcGIS Portal Feature Service Reader: Using proxy http://proxy.####.intern:8080/
ArcGIS Portal Feature Service Reader: SSL certificate verification failed for host 'geoportaal.####.intern'. HTTPS connections may not be secure. Disabling verification of SSL certificates. Message: HTTPSConnectionPool(host='geoportaal.####.intern', port=443): Max retries exceeded with url: /portal/sharing/rest/generateToken (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1125)')))
ArcGIS Portal Feature Service Reader: The server at 'https://geoportaal.####.intern/portal/sharing/rest/generateToken' does not appear to be an ArcGIS Portal instance. Verify that the host is a valid ArcGIS Portal
You don't need to attach anything to the output port, unless you have anything else you need the incoming features for.
- Best Answer
When using the AttributeFileWriter to write a binary file (such as jpeg or mov files), make sure that you're setting the target file encoding to "fme-binary":
When using the AttributeFileWriter to write a binary file (such as jpeg or mov files), make sure that you're setting the target file encoding to "fme-binary":
Thank you so much!
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.