You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we move into production and start tracking usage metrics we should be able to quantify the amount of data being egressed from this API vs. if this API did not exist and the requests would have instead been required to download the entire shapefile to do the analysis.
If hydrocron did not exist, each request would need to be downloading multiple granlues from the shapefile swot collection. We should be able to build a dashboard or report which shows the 'theoretical' egress that would be required by users to build the same time series they can get directly from the API. We can then show a comparison of the size of the data egressed from the API.
The text was updated successfully, but these errors were encountered:
As we move into production and start tracking usage metrics we should be able to quantify the amount of data being egressed from this API vs. if this API did not exist and the requests would have instead been required to download the entire shapefile to do the analysis.
If hydrocron did not exist, each request would need to be downloading multiple granlues from the shapefile swot collection. We should be able to build a dashboard or report which shows the 'theoretical' egress that would be required by users to build the same time series they can get directly from the API. We can then show a comparison of the size of the data egressed from the API.
The text was updated successfully, but these errors were encountered: