Open andy-esch opened 8 years ago
TBH I don't really think obs_search
in its current form is particularly maintainable. I prefer the approach of OBS_GetAvailableNumerators. You could use that function as is, but do a bit of post-filtering based off of name
and valid_geom
to obtain the same results as OBS_Search
.
I could imagine rewriting OBS_Search
to make those filters just part of the API. Do you think this would be worthwhile? Do we ever really see anybody but power users using this feature? If not, I think eventually OBS_Search
should just be deprecated.
Also, do answer the second question... those were planned for sprint but weren't reflected in the issues, so I've opened some: https://github.com/CartoDB/bigmetadata/issues/111 https://github.com/CartoDB/bigmetadata/issues/110
Yeah, looks like OBS_GetAvailableNumerators
is good for the purposes here. I imagine, though, people using the catalog to find the information about the measures they are interested in instead. I'd be curious about the usage of OBS_Search
, and be surprised if it's used more than a dozen or two times.
My two cents: source and date should be available and exposed in the catalog and the Builder UI.
Agreed. The designs for the Builder UI include both of these things (including a nifty date selector), and I'm working on updating the catalog right now.
OBS_Search
would be more useful if we could expose the available date ranges.@talos do you have plans for exposing available dates?
cc @AbelVM