Skip to main content
Question

Directory and File Path when reading a zip returns 'wrong' dates

  • December 9, 2016
  • 3 replies
  • 26 views

Forum|alt.badge.img

Prologue: this suggestion puzzled me, but it's right: in 2016.0 (what I'm using) you can't point a Directory and File Reader at a zip file. You can with a FeatureReader though. Now read on!

I'm retrieving the file properties out of a zip file with a FeatureReader with format 'Directory and File Pathnames' and 'retrieve file properties:' set to Yes. Workspace attached, .

The file name and file size comes back correct, but all the dates, path_accessed_date, path_created_date and path_modified_date, get set to now. I think FME should be returning the dates the files have inside the zip.

P.S. It looks like FME is actually unzipping the files to get at the info:

path_windows (string) = d:\\temp\\ea_admin_boundaries.zip_1481293489605_5384\\AREAPF_EA_NE_010K_V1_3.shx

...which explains the dates. Still not the right output to give, though, IMNSHO.

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.

3 replies

redgeographics
Celebrity
Forum|alt.badge.img+59
  • Celebrity
  • 3697 replies
  • December 12, 2016

I think you're right, it's probably a good idea to pass this on to Safe's support (tagging @Mark2AtSafe so he'll see this)


brianatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • 92 replies
  • December 12, 2016

Hi @shepthedog63,

Thanks for posting this and providing the reproduction workspace. I will file a problem report in our system for this. We really appreciate your efforts to make FME better!

Regards,

 

Brian

  • 3 replies
  • August 2, 2017

I think you're right, it's probably a good idea to pass this on to Safe's support (tagging @Mark2AtSafe so he'll see this)

Thanks for logging this @shepthedog63. I've just encountered this issue in 2017.0.1.1 (build 17291). Any chance of a fix for this one? @BrianAtSafe