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

Extend Carto importer to process tiling of GeoTIFFs #7

Closed
7 tasks
jjmata opened this issue Mar 10, 2017 · 9 comments
Closed
7 tasks

Extend Carto importer to process tiling of GeoTIFFs #7

jjmata opened this issue Mar 10, 2017 · 9 comments

Comments

@jjmata
Copy link
Member

jjmata commented Mar 10, 2017

Same as #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:

  • File too big (facilitate avoiding the max_import_file_size limit restriction)
  • Lack of gdal2tiles.py in path (fix the same for other gdal* binaries, please!)
  • Non-georeferenced TIFFs get loaded but not tiled / they don't error out (and maybe get presented on a non-referenced canvas in the future?)

Test to make sure that orthomosaics generated by the major vendors work:

@jjmata jjmata added this to the April O'neil milestone Mar 10, 2017
@jjmata
Copy link
Member Author

jjmata commented Mar 10, 2017

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.

@jjmata
Copy link
Member Author

jjmata commented Mar 10, 2017

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:

@jjmata jjmata modified the milestones: James May, April O'neil Mar 30, 2017
@jjmata
Copy link
Member Author

jjmata commented Mar 30, 2017

Moving to next milestone.

@jjmata
Copy link
Member Author

jjmata commented Apr 4, 2017

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!)

@jjmata jjmata mentioned this issue Apr 4, 2017
7 tasks
@jjmata
Copy link
Member Author

jjmata commented Apr 5, 2017

I've started on at least part of this, so taking over for now ...

@jjmata jjmata assigned jjmata and unassigned apercas Apr 5, 2017
@jjmata
Copy link
Member Author

jjmata commented Apr 5, 2017

@jjmata jjmata modified the milestones: Juno, James May Apr 26, 2017
@jjmata
Copy link
Member Author

jjmata commented Apr 26, 2017

Not critical for April, so moving to next milestone.

@jjmata jjmata removed their assignment Jun 12, 2017
@jjmata
Copy link
Member Author

jjmata commented Jun 30, 2017

Another milestone, another delay.

@jjmata jjmata removed this from the Juno milestone Jun 30, 2017
@ivanprado
Copy link

I'll close the ticket now that rasters can be imported directly to Postgres without the need external use of tiling

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

No branches or pull requests

3 participants