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

Report to compare egress size from API vs full granule #162

Open
frankinspace opened this issue Apr 17, 2024 · 0 comments
Open

Report to compare egress size from API vs full granule #162

frankinspace opened this issue Apr 17, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@frankinspace
Copy link
Member

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.

@frankinspace frankinspace added the documentation Improvements or additions to documentation label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant