Closed jjmata closed 6 years ago
Yes, this means we create a default viz. as with #3 as well. Everything that we do in #3 that makes sense here, we should also do it with GeoTIFFs that people upload as well.
What is not terribly clear is that we should actually continue uploading the damn TIFFs to PostGIS, but for the time being let's leave it that way.
/cc @javisantana so he doesn't get rid of TIFF imports quite yet or without letting us know first :trollface:
Moving to next milestone.
Once we have #1 working, could we use some of the logic there to help here @apercas? What I envision is that we import the GeoTIFF into PostGIS and then create a default visualization just like the ones we've been putting on codepen - that one only works on Safari due to HTTPS cross-domain requests.
That way we save ourselves having to wait for the tiling (except we do wait for the import/overlays to be created!)
I've started on at least part of this, so taking over for now ...
This is WIP here: https://github.com/splashblot/dronedb/tree/tileo-feature/tiff-tiler
Not critical for April, so moving to next milestone.
Another milestone, another delay.
I'll close the ticket now that rasters can be imported directly to Postgres without the need external use of tiling
Same as https://github.com/splashblot/dronedb/issues/3 but starting with a pre-stitched GeoTIFF (basically do everything we do for unstitched images but skip to the step after stitching has been completed by ODM for people who submit a well-referenced TIFF.)
Extra credit: Possibly store assets in S3 per organization if possible! Parallelize at some point as well, see https://github.com/GitHubRGI/geopackage-python/wiki/Usage-Instructions-for-gdal2tiles_parallel.py
Make sure error conditions are well handled/reported:
max_import_file_size
limit restriction)gdal2tiles.py
in path (fix the same for othergdal*
binaries, please!)Test to make sure that orthomosaics generated by the major vendors work: