Trouble with time-zone metadata

Using Bridge 1.0.4 (and also Bridge CS3 Beta 2) on a PC with 1 GB RAM under Windows XP SP2, I have problems with the date-and-time of digital images whenever the camera, at shooting time, was located in a different time zone than the PC is at image-processing time. I already issued a Bridge feature request in the appropriate user-to-user forum months ago, but obviously to no avail yet.
Bridge, or the underlying XMP system, insists to assign the PC's local time-zone information to the image files, no matter if that's appropriate or not. As far as I can see, in Bridge there is no user interface element provided to enable the user to change the images' time zones. In my particular case, I have images shot at e. g. 8:15 AM +1 but they end up being falsely marked as taken at 8:15 AM +2 (I am located in Central Europe). So the metadata item exif:DateTimeOriginal reads "2007-04-08T08:15:40+02:00" while it is supposed to be "2007-04-08T08:15:40+01:00".
So eventually I digged into Brdge scripting and wrote a script that scans through all image file in the current folder, reads their date-and-time information (i. e. exif:DateTimeOriginal and exif:DateTimeDigitized) and changes all "+02:00" substrings to "+01:00". There are more date-and-time entries in the metadata but those refer to modification dates so they can be left the way they happen to be.
This strategy seems to work well ... but only with image files that don't have XMP sidecar files, i. e. JPEG and TIFF files in particular. Strangely, images that store their metadata in XMP sidecar files, i. e. raw image files, won't accept the correction. Or rather, they do accept it but only temporarily. Right after running my "AdjustTimezone" script the time-zone data is correct (+1) but after a while it's magically back to were it was, i. e. +2. I already suspected it might be a cache thing, but resetting and updating the folder's cache immediately after having run the script doesn't help.
What is happening here? How can I store time-zone information in XMP sidecar files reliably and permanently? And is there a more comfortable way to access the time-zone information than through a home-made Bridge script?
-- Olaf
P.S. I also posted this into the Bridge Windows forum.

Olaf,
did you get an answer on the Bridge forum? Otherwise, I'll forward this internally.
Frank

Similar Messages

TIMESTAMP WITH TIME ZONE

Hi Team, will Import into a table I am getting the below error message
Error Message
Record 1: Rejected - Error on table MTN_BUNDLES_EXPIRY_MIG, column EXPIRY_DATE_T.
ORA-01840: input value not long enough for date format
The data client provide in .XLs file
2013-08-31 17:14:56
My Table Structure is
CREATE TABLE tmp_mtnuga_3g_expiry_mig
    MSISDN_V            VARCHAR2 (50),
    expiry_Date_t         TIMESTAMP(6) WITH TIME ZONE
    status_date_t          TIMESTAMP(6) WITH TIME ZONE
    GOT_STARTER_PACK_V NUMBER(10)
I am using 2 option to import into a table
First option using Toad ---> Import Table -- option here i am getting error like
The format is not matched.
Second option using SQL Loader-->
LOAD DATA
INFILE 'D:\ss\TT-Projects\Customer Apps\Client Dump\3GBundle.csv'
BADFILE 'D:\dd\TT-Projects\Customer Apps\Client Dump\3GBundle.bad'
DISCARDFILE 'D:\dd\TT-Projects\Customer Apps\Client Dump\3GBundle.dsc'
INTO TABLE tmp_mtnuga_3g_expiry_mig
INSERT
(MSISDN_V,
EXPIRY_DATE_T,
STATUS_DATE_T,
GOT_STARTER_PACK_V
Please guide me how solve the TimeStamp

Check Part II SQL*Loader I can't remember when I last used it (being server side I use External Tables), but it should turn out something like
LOAD DATA
INFILE 'D:\ss\TT-Projects\Customer Apps\Client Dump\3GBundle.csv'
BADFILE 'D:\dd\TT-Projects\Customer Apps\Client Dump\3GBundle.bad'
DISCARDFILE 'D:\dd\TT-Projects\Customer Apps\Client Dump\3GBundle.dsc'
INSERT INTO TABLE tmp_mtnuga_3g_expiry_mig
fields terminated by ',' optionally enclosed by '"'
(MSISDN_V,
EXPIRY_DATE_T char "to_timestamp_tz(:EXPIRY_DATE_T,'yyyy-mm-dd hh24:mi:sstzh:tzm')",
STATUS_DATE_T char "to_timestamp_tz(:STATUS_DATE_T,'yyyy-mm-dd hh24:mi:sstzh:tzm')",
GOT_STARTER_PACK_V
you must adjust the mask to match your data
Regards
Etbin

Trouble with Time Machine (runs constantly). Erase and install?

Trouble with Time Machine (runs constantly). Tried re-installation (equivalent of archive install) of Snow Leopard. Time Machine still unable to complete a back-up. Erase and install recommended at Genius Bar. Have backed up data to external HD using Super Duper. Should be a bootable backup. Last successful backup through Time Machine was 6/1/11. Not sure if I can access this back-up if I erase and re-install.
Computer shipped with Tiger (7/2007). Have original disks. Now running Snow Leopard. So: erase HD, install Tiger, then update to Snow Leopard? Start-up from Tiger disks does not appear to work (starting up holding "C" key). Suggestions? Want very much to transfer data to new iMac, but do not want to carry bugs forward. Very nervous about erasing HD. And have the questions above about reinstalling system software.
Advice desired! Thanks.

Well if you can hold option and boot off the Superdupes clone and it works fine then you should be set to do what you need to do to the original boot drive.
Disconnect all drives and c boot off the Snow Leopard install disk, use Disk Utility to Erase > format HFS+ journaled your internal boot drive.
Quit and reinstall OS X Snow Leopard, setup (do not use Setup/Migration Assitant!) and update to 10.6.8
When you setup the new install, use the same hard drive name and user name as you did before.
Now the free iLife that came on the Tiger disks you won't get naturally, but you can pick them off the disk with the shareware program called Pacifist.
install your programs from fresh sources, this way you don't get the "crap" from the older setup.
Once your machine is up and going. Hook up the clone and transfer your user folders over manually. With iTunes just replace the whole folder. Because you kept the same user and boot drive name as before, the playlists should be fine.
Once your all peachy, take the opportunity to clone this new setup to a external drive, label and disconnect.
Make another clone for day to day, or week to week clone updates and your just a hold option boot away for recovery.
You know Superdupes and Carbon Copy Cloner both have auto-scedualing/updating ability, so you can leave them plugged in and it will perform a update so your clone stays fresh and recent.
But you should keep a clone timed back about a couple of weeks back just in case you install something bad and don't learn about it right away.

Trouble with Time Machine/Time Capsule try Backup instead

Trouble with Time Machine preparing to download taking hogging your system followed by errors that don't make any sense even if you look at the console logs to try to figure out. Try Backup instead.
Find the software here:
http://www.apple.com/downloads/macosx/apple/application_updates/backup312.html
It allows you to configure when to do back ups and specific data you want, and includes templates for configurations to make it easy. The only catch is you loose the Time Machine benefits of restoring an individual file easily. For me it gets around the issues w/ Time Machine hogging my system resources (Finder at 98% CPU cycles both cores) while "preparing backup", followed by strange failures that can't figure out, followed by more "preparing backup".

I was running backup instead of time machine until I saw snow leopard had time machine improvements. I'm very happy with the performance so far w/ snow leopard (OS X 10.6) time machine performance.

Trouble with time machine

I am having trouble with Time Machine. I keep getting several messages: 1. Mac OS X can't repair the disk "Mona's I MAC" 2. You haven't selected a location for Time Machine Backups.
When I try to select a location there is nothing there to select and the time machine will not stay on. I have an external back up "my passport" by WD. Could this be full?
Need help.

I was running backup instead of time machine until I saw snow leopard had time machine improvements. I'm very happy with the performance so far w/ snow leopard (OS X 10.6) time machine performance.

Partitioning on a table on the field TIMESTAMP WITH TIME ZONE

Hi I have a very large size table which has grown to a size that we are not able to query it efficiently. We have decided to partition the table. But the issue is the table has a TIMESTAMP WITH TIME ZONE field and not DATE. I have found some links on the web which state this might cause an error. I am planning to create a temp table with the partition rules and at the same time copy data from the original one.
using CREATE TABLE XYZ PARTITION BY RANGE (ABC) ( ---- Partition rules ------) NOLOGGING AS SELECT * FROM XYZ_ACTUAL where 1 = 2;
Then if it works fine, I would rename the table with partitions to the actual name.
Should all this be fine?
The database is very critical. Hence the dilemma.

Have you tried converting the timestamp with time zone to a character string as a partition key, possibly using an edit mask to control the timestamp components used?
Your plan sounds OK to me - if you can get the partitioned table created - but I would test in a development first o see where the lLw of Unintended Consequences might decide to manifest itself.
Edited by: riedelme on Dec 8, 2009 9:13 AM

Having trouble with time capsule, won't find backups

having trouble with time capsule, won't find backups

Usually a simple reboot will work.. Reboot the TC..
If that is not enough.. Restart the whole network from off.
Mountain Lion and to a lesser extent Lion.. have network issues and lose track of the TC.

How to deal with time zone while upgrading the database?

Hi,
How to deal with time zone while upgrading the database?
Thanks
Edited by: user12135020 on Jul 4, 2011 3:06 AM

Hello,
I answered to a Wrong post.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Jul 4, 2011 12:15 PM

Changing date and time is wrong with time zone problem

Okay, searched some of the forums, but didn't get the most correct answer to this:
I just imported all my photos into Aperture from iPhoto (chose to have Aperture manage files as I don't plan on using iPhoto any longer. When I imported the files, I decided to do some organizing by date into folders. no problem.
In some of my projects, I found some files that I imported from scans or got from others who had a film roll and processed it at a lab, and the dates from those files aren't the dates that the event took place. I went into Metadata>Adjust date and time, and changed the date (not so much the time I'm worried about), and checked the "change the masters" little box, too.
After I close out of that box, the picture has the wrong date. I've determined this is because of the time zone support. I currently live in Japan, and I would like my photos here to show up as the date in the place they were taken. I think the date I enter, it thinks is the date I'm currently in (GMT +9), but aperture chooses to convert the date as if I was saying "hey, the picture I took happened on "date" in GMT +0:00)" which then makes it look in the metadata view as if it happened a day earlier.
Any imported photos come in as the correct date and time and correct time zone, as far as I can see. It's just when I change the date and time it thinks I mean to have aperture convert it to GMT + 0:00. (but on a little more of a funny side... older pictures that happened in other time zones back in the states it lists the correct date and time for when the picture was taken, but "says" it's GMT +9:00) (another issue I'll deal with later maybe!)
Hope I've described it in such a way that you can get it.

I changed time and now my MacBook won't work

With Time Zone Support on Calendar no longer automatically adjust to the local timezone.

Apples support forums are riddled with Discussions about problems with being able to dicate a specific time zone for appointments. Many of these postings, as well as their corresponding solutions, are unnecessarily lenghtly when the root cause of all of this is a one very simple mistake by Apple. Right now to be able to assign a specifc timezone for an appointment using the Calendar app on the iPhone you have to have "Time Zone Support" turned on in Settings. The problem is that when you turn on this feature the Calendar app stops automatically updating the calendar to reflect the local time zone you are in. These are simply two seperate items that have no reason to be tied together. Apple could easily correct almost all of the issues people are having with this topic if it simply split this into two seperate options that users can turn on/off seprately:
1.) Enter time zone for each appointment. YES/NO
2.) Adjust Calendar to the local timezone. YES/NO
It is virturally incomprehensible that Apple has not fixed this. It was clearly a mistake.

I have this problem too and am frustrated - it's not solving no matter what i do. And now Siri is totally bonkers too on this new software update - can't even pull from my contacts when I ask her to look someone up. What the heck is going on at Apple software? Have they been hiring a bunch of arrogant, crap programmers? I am seriously thinking of not buying an iPhone again after having one for 5 years. So disappointed!!

HT4576 I want to set up appointment times for an overseas trip before I go, and see those local times in the places I visit, but also be able to set new appointments while I am traveling, in the local times. Can I do this with Time Zone Support? If not,

I want to set up appointment times for an overseas trip on my iPhone 4S before I go, and have them appear as I put them in (for the local time) when visiting other countries. I also want to be able to adjust times and set up new appointments when I am overseas for the local time. Can I do this using the Time Zone Support or any other way?
Basically I want to do what I can do with a piece of paper - write down the time for when I will be there, and have it viewable when I am there, but also be able to put down new times while there.

Hi.
Regarding your question about reverting back- yes, I think you can. If you make a backup of your current configuration in Server Admin (by dragging the configuration file to your desktop- cool, no?) then you can load that one back in should your configuration not work. If you have the manual from Apple it should describe this process.
Network speed post-op? I don't think you will need to worry. Even using home directories stored on our OS X Server there is no network slowdown (that you can notice or that impacts the wider LAN in any case). It shouldn't slow down access to files, applications (which still come from the local drive anyway) or individual internet connections (even with filtering).
In our experience some of these things have actually got faster- but a lot of that is user perception. Same goes for people who will know you have configured the server and that they are now accessing files through your network from the server, and who really think it is slower. File coming from your local hard drive will always be quicker- but network access isn't that bad that it will make you barf and run in the opposite direction.
Something to look at: connection speed between clients and switching technology in your office. In other words, what kinds of switches are you using, what line speed have you got (100MB/s?) and is the connection from your server to the switch gigabit? Make sure it is.
Enjoy
Paul
MacBook Pro 2.16GHz Mac OS X (10.4.8)

Problem in converting the String to Date with time zone GMT

Hi,
When I tried to convert the string 12/05/2009 to Date, the time zone is set to BST.On the other hand, for the date 12/12/2009, the time zone is set to GMT. What should I do to get the time zone as GMT all the time.?
SimpleDateFormat formatter = new SimpleDateFormat("dd/MM/yyyy");
String dateString = "12/05/2009";
System.out.println(myDate.toString());

I think you are all missing the point. java.util.Date objects always alway always store the date as the number of milliseconds since 1/1/1970 UTC so the only TimeZone they have its the implicit UTC. When you use the Date.toString() method the toString() method gets the default time zone from your environment and formats the data accordingly. This means that the same Date object will, by default, produce a different result for France and Australia and the US.
So, if you have the date "12/5/2009" as a String then to convert it to a java.util.Date you must specify what TimeZone is implied. If it is your system time zone then you can just create a SimpleDateFormat object with the correct format and then use the parse() method to create the java.util.Date object and this will automatically be converted to UTC. If the date String represents some other time zone then you must explicitly set the time zone of the SimpleDateFormat object before parsing the string.
The same approach applies when converting a java.util.Date object to a String. If you want anything other than your system time zone then you must explicitly tell the SimpleDateFormat what time zone you want the result formatted for.

Help with time zone setting not working in my treo 750

When I set my home time zone in the time setting option and I confirm the change, it does not take the change. The home time zone is always set to Pacific Standard Time. Does anybody knows how to fix this bug?
Post relates to: None

rcury4 wrote:
"Time machine couldn't coplete the backup to Rick's backup disk". "Unable to complete backup. an error occurred while creating the backup folder".
See #C10 in Time Machine - Troubleshooting
"Time Machine couldn't complete the backup to "Rick's Backup Disk". An error occurred while copying files. The problem may be temporary. If the problem persists, use disk utility to repair your backup disk."
Not one of Apple's more informative messages.
There's a problem with a file on your system. See #C3 in the above link. It will show you how to locate the message(s) that describe the problem, then help you fix it. If that doesn't help, post back with details, including all the messages, what you've done, and the results.

Problem with Time Zones

Hi to all,
I am having some general Question regarding Time Zone
If a User has Time Zone in SU01 as TZ1 and System Time Zone as TZ2.
When that particular user execute an IDOC or SM37 job or Executing any Sales orders or any thing in SAP system.
Which time zone will appear in SAP tables after processing his work? is that TZ1 or TZ2 ?
Thanks
Tony

data is stored in tables with system time.
M.

TimeStamp with time zone vs java Date

In the developer's preview release notes, I read about the extended support on Oracle TimeStamp. We are currently planning to migrate current TIMESTAMP columns to TIMESTAMP WITH TIMEZONE to keep the user time zone with the typed date. Here is my question: Which time zone is persisted using a direct to field mapping between a java.util.Date and a TIMESTAMPTZ column? As the java.util.Date contains no time zone (in opposition to java.util.Calendar), does TopLink uses the JVM time zone? WHat is the best to data structure to keep date/time & time zone in our entities? Thanks, Yannick.

I believe it would be the local timezone of the session. If you map a Date to the TIMESTAMP TZ then the SQL written out will not include a TZ value.
Typically if you wish to map to a TIMESTAMPTZ field you would want to use an object in the model that can hold both the Timestamp and TZ values. This is most commonly a Calendar.
Doug

Trouble with time-zone metadata

Similar Messages

Maybe you are looking for