The image_service from earth-genome

image_service's Introduction

Image Service

This project establishes a web service for pulling satellite imagery from various providers. Links to available services and detailed instructions are given at the primary Heroku entry point.

There are also several tools available for local image processing:

Manual_reprocessing: Mosaicking and color correction for image tiles downloaded elsewhere.
Georeferencing: Conversions between vectors and rasters and a tool to restore georeferencing to images.
The modules in webapp/grabbers: Local access to the satellite provider APIs (redundant with the web service).

Dependencies

GDAL
API keys in out-of-repo files .env and webapp/.google_config.json.

Developing and deploying

The image service is based a containerized Flask web app, deployed on Heroku. To test locally:

docker-compose build
docker-compose up

To deploy to Heroku:

heroku container:push --recursive -a earthrise-imagery
heroku container:release web worker thumbnailworker

image_service's People

Contributors

Stargazers

Watchers

image_service's Issues

Figure out how to interact with DG img.geotiff() method.

Geotiff headers come back correct. Images are almost purely black (pixel values <~ 24 out of uint16 possible values) and cannot be opened with pillow tif utilities (though they can be with cv2).

Orthorectification?

Clash between Shapely and other GEOS libraries

This is an issue with external libraries.

There is a known clash between shapely and the GEOS libraries - osgeo and therefore possibly rasterio and gbdxtools. So far, importing shapley before the other libraries has
cured the problem here - and I think the reordering of imports in dg_grabber.py is the only place this explicitly impacts the code base. When working from the interpreter, I know have to import utilities.geobox.geobox before dg_grabber.

There is some thought that the clash lies between Homebrew python / gdal installations
and shapley. See: shapely/shapely#260

If an exception is thrown, it will typically come with a (somewhat cryptic) message of the form:
"Assertion failed: (0), function query, file AbstractSTRtree.cpp, line 287."

Recommend Projects