I have an image of 144 rows x 640 cols x 224 bands in ENVI format, in bil and
UInt16 (hdr states interleave = bil, data type = 12).
In order to convert to GTiff, I state:
gdal_translate -ot UInt16 input.raw test.tif
but values in test.tif are wrong: e.g. a pixel with value of 1038.0 in
input.raw
On mercredi 19 décembre 2018 06:30:30 CET Andrew C Aitchison wrote:
> Do we need to consider (real and false) precision when converting between
> OGRSpatialReference and string ?
Can you explain more what you mean ? I don't understand.
--
Spatialys - Geospatial professional services
http://www.s
On Wed, 19 Dec 2018, Even Rouault wrote:
On mercredi 19 décembre 2018 06:30:30 CET Andrew C Aitchison wrote:
Do we need to consider (real and false) precision when converting between
OGRSpatialReference and string ?
My concern is that since since a WKT1 string encodes floating point
values a
On mercredi 19 décembre 2018 11:29:09 CET Andrew C Aitchison wrote:
> On Wed, 19 Dec 2018, Even Rouault wrote:
> > On mercredi 19 décembre 2018 06:30:30 CET Andrew C Aitchison wrote:
> >> Do we need to consider (real and false) precision when converting between
> >> OGRSpatialReference and string ?
Even Rouault-2 wrote
> ICreateLayer() when receiving a OGRSpatialReference* may decide to change
> the
> axis mapping strategy. That is: if it receives a OGRSpatialReference with
> AUTHORITY_COMPLIANT order, it may decide to switch to
> TRADITIONAL_GIS_ORDER
> and GetSpatialRef()::GetDataAxisToS
On mercredi 19 décembre 2018 05:46:26 CET jratike80 wrote:
> Even Rouault-2 wrote
>
> > ICreateLayer() when receiving a OGRSpatialReference* may decide to change
> > the
> > axis mapping strategy. That is: if it receives a OGRSpatialReference with
> > AUTHORITY_COMPLIANT order, it may decide to sw
Hi,
Motion: GDAL/OGR 2.4.0 rc1 is promoted to be the official 2.4.0 final release.
---
My vote: +1
---
I didn't have any feedback on this one, so I assume things go well.
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
_
+1
-Jukka Rahkonen-
Even Rouault-2 wrote
> Hi,
>
> Motion: GDAL/OGR 2.4.0 rc1 is promoted to be the official 2.4.0final
> release.
>
> ---
>
> My vote: +1
>
> ---
>
> I didn't have any feedback on this one, so I assume things go well.
>
> Even
--
Sent from: http://osge
I know that a number of format-specific options can be set as environment
variables so they don't have to be specified on the command line
(TIFF_USE_OVR, GTIFF_IGNORE_READ_ERRORS). Is there a way to set defaults
for other format-specific dataset creation options (for geotiff, TILED=YES,
COMPRESS=L
On mercredi 19 décembre 2018 11:22:00 CET Luke Roth wrote:
> I know that a number of format-specific options can be set as environment
> variables so they don't have to be specified on the command line
> (TIFF_USE_OVR, GTIFF_IGNORE_READ_ERRORS). Is there a way to set defaults
> for other format-sp
+1
On 12/19/18 8:18 AM, jratike80 wrote:
> +1
>
> -Jukka Rahkonen-
>
>
> Even Rouault-2 wrote
>> Hi,
>>
>> Motion: GDAL/OGR 2.4.0 rc1 is promoted to be the official 2.4.0 final
>> release.
>>
>> ---
>>
>> My vote: +1
>>
>> ---
>>
>> I didn't have any feedback on this one, so I assume
+1
Tamas
Even Rouault ezt írta (időpont: 2018. dec.
19., Sze, 14:11):
> Hi,
>
> Motion: GDAL/OGR 2.4.0 rc1 is promoted to be the official 2.4.0 final
> release.
>
> ---
>
> My vote: +1
>
> ---
>
> I didn't have any feedback on this one, so I assume things go well.
>
> Even
>
> --
> Sp
+1
Daniel
On 2018-12-19 8:11 a.m., Even Rouault wrote:
Hi,
Motion: GDAL/OGR 2.4.0 rc1 is promoted to be the official 2.4.0 final release.
---
My vote: +1
---
I didn't have any feedback on this one, so I assume things go well.
Even
--
Daniel Morissette
Mapgears Inc
T: +1 418
13 matches
Mail list logo
