GPS-Sport ForenRun.GPS SoftwarePicture modifed vs time-taken date/time
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von1>Letzte Seite
Tom 02.09.2008 14:59:12 UTC



The Windows Mobile file system behaves strangely sometimes. For instance, it is possible to have creation time greater than modification time which should be impossible. If you upload from the training directory, any picture in the directory is uploaded. The geo-coding is then performed directly on the server, using a Windows Server 2003 file system. Therefore the difference.

I think it's a good idea to put external photos to the training directory.

Slogfester 02.09.2008 12:34:36 UTC geändert am 02.09.2008 12:34:49 UTC



Perhaps its just me, but this feature keeps mystifying me!

How come in some cases pictures with the correct modified date/time do not get uploaded using 'scan multimedia files', but when you place them in the appropraite training subdirectory they appear correctly geo-coded?
Is uploading WITHOUT scanning reading the modified date/time, while uploading WITH scanning looking for some other date/time stamp?

Yours, totally confused by this part of run.gps!
Slogfester 08.08.2008 13:26:06 UTC geändert am 08.08.2008 13:27:10 UTC

Exactly what date/time is run.gps using?

No other feature wastes more of my time than mucking around with the date/time stamps of other peoples photos/vids to try and get them geo-coded correctly and hence uploaded from run.gps to gps-sport :(

I use a a simple/free program called SetFileDate v2.0 to correct the created/modified/accessed date/time stamp. Sometimes, it evidently does not change the accessed date/time. Anyone know a better (but still simple) one?

I recently copied (directly) a picture back to my storage card for auto-scan and upload, and discovered that run.gps was reading the accessed date/time stamp first rather than the created/modified, and hence in this case the picture was not uploaded? The manual says created/modified is used?

So which is it?
robert 20.06.2008 17:57:31 UTC



Hi Slogfester,

yes, but if you have 300 pictures in that one dedicated directory, it will also take ages to check the EXIF fields. To do that, one must open, read and interpret all of those files :-( Just checking the file timestamps is much faster.

Nevertheless we'll keep this issue in mind.

Best regards

Robert
Slogfester 19.06.2008 11:02:41 UTC



Hi Robert, again my understanding is that 9 times out of 10, pictures are stored in a specific sub-directory on PDAs. On mine (HTC Touch Cruise using WM6) its called \DCIM\100Media (which I presume is MS's way of making things 'intuitive and user friendly' I guess!! [used to be My Pictures]), but whatever it is, perhaps to speed up the process, the user could specific in configuration where pictures are usually stored? Then a simple check box give the option to search the whole device only if required, but with a warning that it will take a long time? Just a suggestion- I'll leave the technical stuff to you technical guys :)
robert 19.06.2008 09:56:38 UTC



This would be feasible, but only for those pictures written into the training directory. For the other pictures that are searched throughout the entire device, it would simply take to long to open and read the EXIF info for all of them.

We'll think about how and when to do this.
Theo 18.06.2008 23:21:41 UTC



Hi there,

I think you mean: use EXIF.
Well, this should be the better way...
Slogfester 17.06.2008 13:49:14 UTC



This has popped up before, but I can't find the thread using search?

My understanding is that Run.GPS uses modified date/time of a picture to locate the place on the track where the picture was taken? However, as many of us know this gets altered by Activesync (MS rubbish!) and by emailing/copying etc. So I find myself manually altering the modified date/time a lot and bypassing Activesync by using a card reader (time consuming). But my understanding is that the 'time-taken' date/time stamp on most digital cameras does not get altered when exchanging? If so, would it not be better to use it for locating the place on the track?
Erste Seite<Seite1von1>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung