ensureGeoIndex does not create index with GeoJSON fields set to true

[velvia]

ensureGeoIndex creates geo indexes with geoJson set to false

How much is this client maintained? I see almost no activity within the last year.

[tariqdaouda]

It has been relatively stable recently (the next version is coming soon). I am still maintaining it by fixing bugs and adding features as needed. But as this is a community project now, unless there is a high demand for a feature I mainly concentrate on the ones I need and rely on pull requests for the rest. Feel free to send PRs.

[velvia]

Ok, is this the right repo to submit or is there another one that’s been taken up by the community?

On May 4, 2021, at 3:15 PM, Tariq Daouda @.***> wrote:

It has been relatively stable recently. I am still maintaining it by fixing bugs and adding features as needed. But as this is a community project now, unless there is a high demand for a feature I mainly concentrate on the ones I need and rely on pull request for the rest. Feel free to send PRs.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ArangoDB-Community/pyArango/issues/202#issuecomment-832284943, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIDPWY2MYHWCNCYK73HTSLTMBPXVANCNFSM44C5CWDQ.

[dodgytricycle]

Instead of ensureGeoIndex, you could try creating a geo index using ensureIndex as it accepts additional index arguments. collection.ensureIndex(index_type='geo', fields=['b'], name=None, geoJson=True)