Thanks, Even and team!
I've followed the contributing directions and am all set to contribute.
It'll be great to be able to integrate Rasterio and GDAL issues. This move
hugely benefits some of my projects and I am very grateful for it. I've
complained about the friction of contributing to GDAL
Even this is awesome. Great work!
Zac
> On Mar 23, 2018, at 9: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
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 rewritten commit messages is that all still
opened pull requests (~20)
Hi all,
I'm happy to declare this motion passed with +1 from myself, HowardB, JukkaR
and KurtS
I'm going now to proceed to the implementation stage.
The existing github mirror is going to be cloned at
https://github.com/OSGeo/gdal_svn_mirror_backup
And the new repository that I prepared
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, "properties":
However, if I don't use -preserve_fid I have not discovered
Julien,
> That is pretty much what I did, however I was looking for a way to avoid
> extra copies of features (maybe I am doing this wrong).
>
In your case, you don't need to copy the features (in the CreateFeature() case
I mentionned, I need too since ownership of the passed feature belongs
Hi Even,
Thank you very much for your answers. Please find some comments enclosed.
Regards,
Julien
Le 21/03/2018 à 11:09, Even Rouault a écrit :
I am writing some code that processes features from a Layer, and I am
facing two distinct problems :
1) Since the processing of features might be