I assume you mean UTC plus the latitude and longitude
isn't UTC alone is enough?
isn't UTC alone is enough?
For example when planning meeting times, the reason local time comes up is ultimately some determinant about when it's going to be day or night - that's the actual metric that meeting planning generally tries to take into account.
Strictly speaking I would say this also applies for storing data about machine to machine events which might be normally considered to be purely sequence based. If we're storing times to determine processing order for example, then there'd be value in storing the lat/lon of the machines generating them, because it's an extra datum which can resolve expected ordering (i.e. based back-calculating latency windows).
Personally when I'm arranging a meeting I want to know the local cultural context, and I want to know the relative times I'm asking for things there.
Getting stuff done 2 hours later may or may not be possible based on the local time of day, calendar day, and time of year.