Detect if running in an environment with arcpy and use their mosaic and zonal stats functions in that case #10

nickrsan · 2023-06-12T21:22:38Z

This one is kind of interesting. We should detect at install time if we're running in an arcpy environment. If we are, skip adding GDAL as a dependency (this is just a list comprehension in setup.py, not sure about other package specs). Then we can run raster merging and zonal stats without additional installations and with less code that runs faster. But we still want to support the current pipeline since it is more cross-platform and doesn't require a license. We'll want to see if we can test the arcpy branch and we'll want to compare the outputs with current methods to make sure we get roughly comparable numbers (pandas has a method for asserting two data frames are roughly equal down to a certain decimal precision. We'll use that)

nickrsan · 2023-06-12T21:29:18Z

This probably also suggests an architecture where mosaicking and zonal stats are run as classes. There can be a subclass for EE zonal stats, rasterstats zonal stats, and arcpy zonal stats. Similarly, we'll have subclasses for
gdal mosaicking and arcpy mosaicking.

nickrsan added this to EEDL Development Jun 12, 2023

nickrsan converted this from a draft issue Jun 12, 2023

nickrsan self-assigned this Jun 12, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Detect if running in an environment with arcpy and use their mosaic and zonal stats functions in that case #10

Detect if running in an environment with arcpy and use their mosaic and zonal stats functions in that case #10

Uh oh!

Detect if running in an environment with arcpy and use their mosaic and zonal stats functions in that case #10

Detect if running in an environment with arcpy and use their mosaic and zonal stats functions in that case #10

Comments

Uh oh!

Uh oh!