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

Add gdal raster mosaic #11706

Closed
dbaston opened this issue Jan 23, 2025 · 4 comments · Fixed by #11715
Closed

Add gdal raster mosaic #11706

dbaston opened this issue Jan 23, 2025 · 4 comments · Fixed by #11715
Assignees
Labels
enhancement gdal_cli Anything related to the new 3.11 "gdal" CLI frontend

Comments

@dbaston
Copy link
Member

dbaston commented Jan 23, 2025

Feature description

Rename the current gdal raster buildvrt to gdal raster mosaic and allow output in any supported format.

Additional context

As discussed in #11558 (comment)

@dbaston dbaston added enhancement gdal_cli Anything related to the new 3.11 "gdal" CLI frontend labels Jan 23, 2025
@jratike80
Copy link
Collaborator

jratike80 commented Jan 23, 2025

I am not totally sure if t a good idea to support any supported format. Mosaics can be big, some formats will not work at all, and for the drivers that work user should be aware of reasonable options. But yes, they need to know them when they materialize the vrt anyway.

"Mosaic" feels good when flat images are stiched side by side, but how about combining bands with -separate. Is the result so much a mosaic?

@dbaston
Copy link
Member Author

dbaston commented Jan 23, 2025

"Mosaic" feels good when flat images are stiched side by side, but how about combining bands with -separate.

Maybe this could be a separate command, something like gdal raster stack ?

@jratike80
Copy link
Collaborator

Maybe this could be a separate command, something like gdal raster stack ?

Makes me think about https://stacspec.org/en that can be flat or deep, or cube. Pile?

@mdsumner
Copy link
Contributor

I think we see the issue where gdalwarp is the superset that includes gdal_translate. I would just vote for

gdalwarp <inputs> output.<ext>

but, as ever that's weird for cases that don't involve reprojection or even resampling. How is a "mosaic" functionally different from this?

gdal raster reproject <inputs> output.<ext>

warp is currently standing in for merge,mosaic,reproject,translate and I think that needs some thought - can we sensibly refactor this? Maybe "convert" should do mosaicing-via-warper when needed, and normal "translate" otherwise.

(I will explore this more, just those immediate thoughts). I overall support "mosaic" as a concept in addition to "convert", "reproject" and I think that's clean enough despite the fair amount of functional overlap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement gdal_cli Anything related to the new 3.11 "gdal" CLI frontend
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants