views:

2254

answers:

5

Hello,

I need the ability to convert a NSDate value to a GMT Date.

How can I go about converting a NSDate value to a GMT formatted NSDate value, independent of what ever date locale settings the iphone is using.

Kind Regards

+7  A: 

Working with time in Cocoa can be complicated. When you get an NSDate object, it's in the local time zone. [[NSTimeZone defaultTimeZone] secondsFromGMT] gives you the offset of the current time zone from GMT. Then you can do this:

NSDate *localDate = // get the date
NSTimeInterval timeZoneOffset = [[NSTimeZone defaultTimeZone] secondsFromGMT]; // You could also use the systemTimeZone method
NSTimeInterval gmtTimeInterval = [localDate timeIntervalSinceReferenceDate] - timeZoneOffset;
NSDate *gmtDate = [NSDate dateWithTimeIntervalSinceReferenceDate:gmtTimeInterval];

Now gmtDate should have the correct date in GMT for you. In order to display it, look at NSDateFormatter, specifically the setDateStyle and setTimeStyle methods. You create an NSDateFormatter, configure it the way you want, and then call stringFromDate: to get a nicely formatted string.

Alex
While this seems good at first, I want to strongly advice against using this method, which can lead to a lot of confusion. A date represents a single point in time. The issue is that you want different *representations* of this date. The same point in time has different "names" in Delhi and in New York, etc. Therefore, think hard about what your context is. You can set the calendar.timeZone property on UIDatePickers to make them use another time zone, and as Howard shows, you can customize date formatters to work with different zones.
Felixyz
An NSDate object represents a point in time, independent of time zone etc... you never need to convert an NSDate to another... it is only when you serialize (convert to and from strings) that the time zone/locale, whether GMT or other comes into account. Howards answer is correct.
Akusete
+3  A: 

Have you tried looking at the documentation for NSDateFormatter?

NSDateFormatter

NSDateFormatter appears to have some methods for playing with TimeZones, particularly

-setTimeZone:

I haven't tested it myself, but I imagine that if you set GMT as the timezone on a date that is originally represented in another timezone, it will display the date with the correct adjustments to match the new timezone.

Jasarien
+8  A: 
    NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];
    dateFormatter.dateFormat = @"yyyy-MM-dd'T'HH:mm";

    NSTimeZone *gmt = [NSTimeZone timeZoneWithAbbreviation:@"GMT"];
    [dateFormatter setTimeZone:gmt];
    NSString *timeStamp = [dateFormatter stringFromDate:[NSDate date]];
    [dateFormatter release];
Howard
Does the DateFormatter work with both "%d" type codes... and just "d" type codes?
Donna
@Donna: The latest NSDateFormatter uses the UTS#35 standard. http://unicode.org/reports/tr35/tr35-6.html#Date_Format_Patterns . It will not work with the C style %d syntax.
Akusete
A: 

While Alex's answer was a good start, it didn't deal with DST (daylight savings time) and added an unnecessary conversion to/from the reference date. The following works for me:

To convert from a localDate to GMT, taking DST into account:

NSDate *localDate = <<your local date>>
NSTimeInterval timeZoneOffset = [[NSTimeZone systemTimeZone] secondsFromGMTForDate:localDate];
NSDate *gmtDate = [localDate dateByAddingTimeInterval:-timeZoneOffset]; // NOTE the "-" sign!

To convert from a GMT date to a localDate, taking DST into account:

NSDate *gmtDate  = <<your gmt date>>
NSTimeInterval timeZoneOffset = [[NSTimeZone systemTimeZone] secondsFromGMTForDate:gmtDate];
NSDate *localDate = [gmtDate dateByAddingTimeInterval:timeZoneOffset];

One small note: I used dateByAddingTimeInterval, which is iOS 4 only. If you are on OS 3 or earlier, use addTimerInterval.

thevoid
This is also a less than ideal solution. As Felixyz pointed out in his response to Alex, you do not want to be messing with the NSDate itself but rather its representation. Howard's answer will give a "localized" representation of the NSDate.
Marcus S. Zarra
An NSDate represents a point in time, independant of a time zone. Your object localDate represents the same point as gmtDate. When you go to convert it to a string you would still need to use a DateFormatter on both, and get the same results.
Akusete
+1  A: 

Howard's Answer is correct and please vote it up and accept it.

For reference I think it is useful to explain the difference between date objects and localised date representations are.

In many programming languages date objects are used to represent unique points in time. Ignoring Relativistic arguments it can be assumed that at any instance we can define a point in time which is equal universally for every one, regardless of how we measure time.

If for each point in time we could construct a unique label, that label could be passed around and referenced unambiguously. The purpose of date objects is to act as a unique universal label for a given point in time.

One could come up with any number of techniques to construct such a labelling scheme and how each date object chooses to do so is immaterial to anyone using them.

An example may be to use a numeric offset from a universal event (X seconds since the sun exploded).

It is only when we wish to take a time point and serialize it into a human readable string that we must deal with the complexities of time zones, locales, etc...

(Local Date String) + (Date Formatter) => Time Point

Time Point + (Date Formatter) => (Local Date String)

Every time point is universal... there is no such thing as a new york time point, or gmt time point, only once you convert a time point to a local string (using a date formatter) does any association to a time zone appear.

Note: I'm sure there are many blogs/articles on this very issue, but my google foo is failing me at this hour. If anyone has the enthusiasm to expand on this issue please feel free to do so.

Akusete