We do this in the LevelDB case.

I want to pull the interpolation behavior out of storage and leave that up to you in the rule evaluation zone.

There are a few open questions for the future:

1. If we request a value for a time that does not exist, meaning an inexact match, should we just return the adjacent values in the query-planned world?