milktrader

So you want to compress 48 observations into one. ``` julia function compress{T,N,D}(ta::TimeArray{T,N,D}, interval::Int , timestamp::Function, value::Function=timestamp) ``` Just to clarify, this is the current API with `interval::Int` replacing `period::Function`....

NOTE: previous posted code has been debugged but only 1-dimensional arrays supported. Try this out and tell me what you think ``` julia function compress{T,N,D}(ta::TimeArray{T,N,D}, interval::Int, position::Function=last, value::Function=position) len =...

By all means, you're welcome to PR some experimental branches to this repo. This keeps it isolated while also allowing others to view what is being worked on. Looking forward...

Where I was going with changing the type of row indices was that you could do things like `mydf[date(1980,1,1):days(4):date(1980,12,1)]` and other similar `getindex` operations. I'm not proposing it gets implemented...

Yes, I think your indexing syntax is more Julian. Would the new type be something along the lines of what the TimeData package implements? ``` julia type Timedata{T}

The reason I went with `Any` is because though `Dict` seems a natural fit, there are cases (that I had explored) where you might want it to be a custom...

Good points.

@JeffreySarnoff says There is a long history of timeseries data files becoming estranged from their original context and utilization I completely agree. You mention you are will to do this...

As far as a PR, since this is your project call it whatever you want. You create one locally with `git checkout -b my_cool_name`.

To update your experimental branch, @ararslan provides the [git-fu here](https://github.com/JuliaStats/TimeSeries.jl/issues/300#issuecomment-287117201)