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

Simplify Conversion Code: Use Only Rioxarray for NetCDF to COG #16

Open
srizvi-NASA opened this issue Apr 2, 2024 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@srizvi-NASA
Copy link

The current conversion code utilizes both rasterio and rioxarray libraries for processing netcdf data into COG format. However, simplifying the conversion process by using only rioxarray seems feasible and advantageous.

Previously, rioxarray encountered an issue when converting object data types in MUR-JPL-L4-GLOB-v4.1 files to NumPy timedeltas. This can likely be addressed by implementing data pre-processing steps before feeding the data to rioxarray.

Here's why transitioning to solely using rioxarray is beneficial:

  1. Reduced Complexity: Maintaining a single library simplifies the codebase and reduces potential dependency conflicts.
  2. Leveraging Rioxarray's Functionality: Rioxarray offers built-in functions specifically designed for working with COG datasets, which can streamline the conversion process.
  3. Resolving Previous Exception: By addressing the data pre-processing step mentioned above, we can overcome the prior exception encountered with rioxarray.

By transitioning to a single library approach using rioxarray, we can achieve a more efficient and robust conversion process.

@frankinspace frankinspace added the enhancement New feature or request label Apr 3, 2024
@frankinspace
Copy link
Member

Supportive of using only rioxarray

@srizvi-NASA
Copy link
Author

I am in the process of making sure that the net2cog handles level-2 data. The current code is good for level-3 (gridded data). The code and the use of various libraries will depend upon a generalized solution to handle level-2 data.

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

No branches or pull requests

2 participants