Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extents #42

Open
gordonwoodhull opened this issue Nov 12, 2015 · 2 comments
Open

extents #42

gordonwoodhull opened this issue Nov 12, 2015 · 2 comments

Comments

@gordonwoodhull
Copy link

How does one retrieve the extents of different dimensions?

In particular, the time dimensions have the lower bound specified in the tbin metadata, but is there an upper bound? Are bounds known for the spatial dimensions?

@laurolins
Copy link
Owner

There is no service for that. In practice we run a few queries (O(log(largest-timestamp)) queries to figure it out (anchored-dives a few levels at a time repeating the process from the previous result extreme nodes that contained data to get a finer and finer time resolution for the bounds). The rational for not adding another core API call for this at the time we thought about adding one, was that it wasn’t totally clear the level of generality we should put (e.g. what if we needed the range for some constrained time range - extremes when categorical dimension “device” is “iPhone” instead of all the data)… instead of adding more service to the core API we settled on the idea that it should be simple enough to derive these services from the core one. I guess having a javascript (or any other language) wrapper extending the current core API of NC should give us more insight on what we could push into the core API...

On Nov 12, 2015, at 12:54 PM, Gordon Woodhull [email protected] wrote:

How does one retrieve the extents of different dimensions?

In particular, the time dimensions have the lower bound specified in the tbin metadata, but is there an upper bound? Are bounds known for the spatial dimensions?


Reply to this email directly or view it on GitHub #42.

@salivian
Copy link
Collaborator

https://github.com/laurolins/nanocube/blob/master/extra/nc_web_viewer/nanocube3.js

getTbinInfo perform a binary search for the effective timerange.

The python script on config generation searches the spatial dimensions.

Horace

On Thu, Nov 12, 2015 at 2:49 PM, Lauro Lins [email protected]
wrote:

There is no service for that. In practice we run a few queries
(O(log(largest-timestamp)) queries to figure it out (anchored-dives a few
levels at a time repeating the process from the previous result extreme
nodes that contained data to get a finer and finer time resolution for the
bounds). The rational for not adding another core API call for this at the
time we thought about adding one, was that it wasn’t totally clear the
level of generality we should put (e.g. what if we needed the range for
some constrained time range - extremes when categorical dimension “device”
is “iPhone” instead of all the data)… instead of adding more service to the
core API we settled on the idea that it should be simple enough to derive
these services from the core one. I guess having a javascript (or any other
language) wrapper extending the current core API of NC should give us more
insight on what we could push into the core API...

On Nov 12, 2015, at 12:54 PM, Gordon Woodhull [email protected]
wrote:

How does one retrieve the extents of different dimensions?

In particular, the time dimensions have the lower bound specified in the
tbin metadata, but is there an upper bound? Are bounds known for the
spatial dimensions?


Reply to this email directly or view it on GitHub <
https://github.com/laurolins/nanocube/issues/42>.


Reply to this email directly or view it on GitHub
#42 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants