Opened 10 years ago
Last modified 6 years ago
#2675 new enhancement
r.in.gdal -e should set region to newly imported map
| Reported by: | volcan01010 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 7.6.2 |
| Component: | Raster | Version: | 7.0.0 |
| Keywords: | r.in.gdal region | Cc: | |
| CPU: | Unspecified | Platform: | Linux |
Description
When running r.in.gdal with the -e flag (to update the region from the imported raster extents), the command finishes by setting the region to the default setting (even if that was not the previous setting).
It may be preferable for it to set the region to match the newly imported map, so that follow up operations e.g. r.composite are run with the correct settings.
Change History (13)
comment:1 by , 9 years ago
| Milestone: | 7.0.1 → 7.0.2 |
|---|
comment:3 by , 9 years ago
The suggestion of falling back to the actual region rather than the unexpected default region sounds reasonable to me.
comment:6 by , 9 years ago
| Milestone: | 7.0.4 → 7.0.5 |
|---|
comment:7 by , 8 years ago
| Milestone: | 7.0.5 → 7.3.0 |
|---|
comment:10 by , 7 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:11 by , 6 years ago
| Milestone: | 7.4.2 → 7.6.0 |
|---|
All enhancement tickets should be assigned to 7.6 milestone.
Note:
See TracTickets
for help on using tickets.
Ticket retargeted after 7.0.1 milestone closed