#5104 closed enhancement (fixed)
Iris driver does not add height information
Reported by: | rveciana | Owned by: | warmerdam |
---|---|---|---|
Priority: | low | Milestone: | 1.11.0 |
Component: | default | Version: | 1.10.0 |
Severity: | normal | Keywords: | IRIS |
Cc: |
Description
It would be good to have some metadata in each band indicating the height of the data represented. This only affects the CAPPI product, since is the only one where height changes in each layer.
I have changed the driver file so it adds the "height" metadata in each layer when the product is CAPPI.
The band creation is moved after the metadata creation to detect the product type before creating the band.
Attachments (1)
Change History (5)
by , 11 years ago
Attachment: | irisdataset.cpp added |
---|
comment:1 by , 11 years ago
Milestone: | 1.10.1 → 2.0 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
trunk r26065 "IRIS: add height information on bands; rename dataset metadata item CAPPI_HEIGHT --> CAPPI_BOTTOM_HEIGHT (#5104)"
I just pushed it in trunk. Changing the name of a metadata item in a stable branch is normally not appropriate, but as it is a new and likely niche driver, I could also push it in 1.10 if you insist.
follow-up: 3 comment:2 by , 11 years ago
Actually is not a change in a name, but adding a new label to the metadata. The behaviour of the existing features does not change. Anyway, if it's better to wait to the new version, just do what you consider is the best, please.
comment:3 by , 11 years ago
Replying to rveciana:
Actually is not a change in a name, but adding a new label to the metadata. The behaviour of the existing features does not change. Anyway, if it's better to wait to the new version, just do what you consider is the best, please.
-->Actualization: It's true, there is one label that changes the name, to avoid confusion. So maybe it's better to wait to the 2.0 version.
comment:4 by , 10 years ago
Milestone: | 2.0 → 1.11.0 |
---|
The irisdataset.cpp driver file