decide on standard time format, either timestamp or date string
Closed this issue · 1 comments
RonanHiggins commented
I swapped track over to a unix time stamp format to be consistent with the path function.
Azimuth scan is still on a date format. We should decide on a standard format.
I'm for unix timestamp
nolta commented
I chose date string mostly out of laziness -- the standard golang JSON decoder automatically converts RFC 3339 date strings to time.Time
objects.
Better to define our own Time
type with custom JSON handling.