Skip to main content
  • EN

I have a user parameter configured as follows:

temp3My user selects about 200MB worth of JPG photos to upload and have processed. In doing so, he gets the following error:

temp4 

This is a user that is working in the field and likely has poor connection quality. However, there is a lot of data to upload. If I attempt an upload with OneDrive or a similar service, it will typically recover/resume an upload as connection issues occur. I do not know if connection issues are what is happening here because the error tells him nothing.

 

Is there a way to dig deeper into the reason behind this issue? Because the workspace never gets a chance to run, I don't know how to diagnose this or develop around it.

 

If my assumption that poor connection quality coupled with a high amount of data is the issue... Do you have any suggestions as to how to go about solving it? Besides the obvious "wait for a better connection", or "use smaller batches".

 

Thank you

For clarification:

There are many uploads that do work fine, and the workspace will run.

Also it often uploads many files before the error occurs.

Large uploads over poor connections can be difficult to handle, unless both the server and the client is equipped to handle resuming partial uploads, which is not always the case. The easiest is perhaps to build something on top of something that already has this functionality, such as a modern FTP server. So a possibility could be to set up an FTP server for the upload, and then perhaps use something like the FTP Watch Publisher on the server to trigger whenever a new file arrives on the server: https://docs.safe.com/fme/html/FME_Server_Documentation/ReferenceManual/FTP_Watch_Publisher.htm

Large uploads over poor connections can be difficult to handle, unless both the server and the client is equipped to handle resuming partial uploads, which is not always the case. The easiest is perhaps to build something on top of something that already has this functionality, such as a modern FTP server. So a possibility could be to set up an FTP server for the upload, and then perhaps use something like the FTP Watch Publisher on the server to trigger whenever a new file arrives on the server: https://docs.safe.com/fme/html/FME_Server_Documentation/ReferenceManual/FTP_Watch_Publisher.htm

Thanks for the reply.

I was thinking along these lines as well but there is a complication. This solution is good when I just need the photo, but I require them to enter custom metadata along with the photo.

 

The easiest way to retrieve custom data is to use a web app with additional user parameters. Otherwise I have to come up with another submission method altogether that can associate custom data with a particular batch of photos. That might be tough to implement with an FTP server.

Reply


Community Stats

30,002
Posts
113,963
Replies
37,624
Members
Terms & ConditionsCookie settings