On 23 March 2018 at 15:09, Even Rouault wrote:
> OK, so now you can and should use https://github.com/OSGeo/gdal to track
> developement and file new tickets/issues
Even,
FYI, if you'd like to create issues labelling scheme different than the modest
default, here is small Python script that can
There is an important difference between the PROJ4 and the PROJ5+
API/syntax:
The old PROJ4 API uses latlong WGS84 as pivot datum for coordinate
transformations like
projection1 -> latlong WGS84 -> projection2
or in '+to' syntax
projection1 +to projection2
The new PROJ5+ API no longer uses a piv
Piyush,
> I tried to search the gdal-dev archives but could not find much on this
> topic.
> HDF5 files support half precision floats and so does numpy. I was wondering
> if there were any plans to include support for this data type?
There's no native support for Float16 in C++, so your bes
Hi,
I tried to search the gdal-dev archives but could not find much on this
topic.
HDF5 files support half precision floats and so does numpy. I was wondering if
there were any plans to include support for this data type?
I understand that some compilers may not support it but support could
On vendredi 23 mars 2018 10:59:02 CEST Rahkonen Jukka (MML) wrote:
> Hi,
>
> Am I right that there is no option to force the writing of "id" member to
> GeoJSON features? I have noticed that if I run ogr2ogr with -preserve_fid
> option then the "id" member is added { "type": "Feature", "id": 0,
>
Even,
On Fri, Mar 23, 2018 at 8:09 AM, Even Rouault
wrote:
> OK, so now you can and should use https://github.com/OSGeo/gdal to track
> developement and file new tickets/issues
> Trac ticket creation has been disabled. You can still modify existing tickets.
>
> One side effect of pushing the rewr
