Timeline for How to apply "Band" settings using gdal Python bindings?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:34 | history | edited | CommunityBot |
replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
|
|
| Oct 26, 2013 at 12:39 | history | tweeted | twitter.com/#!/StackGIS/status/394080763945435136 | ||
| Oct 26, 2013 at 1:25 | answer | added | user2856 | timeline score: 5 | |
| Oct 25, 2013 at 22:51 | history | edited | RyanKDalton | CC BY-SA 3.0 |
added 326 characters in body
|
| Oct 25, 2013 at 22:47 | comment | added | blah238 |
Not an expert on GDAL but it appears that CreateCopy is not meant for transformation of the "metadata" of a dataset, e.g. the number and order of bands can be considered part of the metadata of the file, which CreateCopy intends to simplify for you. So yes, I think you must use Create instead, which is a bit more involved. The source to gdal_merge.py could be useful to look at.
|
|
| Oct 25, 2013 at 22:13 | history | edited | RyanKDalton | CC BY-SA 3.0 |
added 20 characters in body; edited title
|
| Oct 25, 2013 at 22:01 | history | asked | RyanKDalton | CC BY-SA 3.0 |