Skip to content

Documentation issue: ordered/geoJSON on collection.add_geo_index #234

Closed
@Adrian-at-CrimsonAzure

Description

@Adrian-at-CrimsonAzure

In the base collection, it seems like the ordered index value is incorrectly documented. According to theArangoDB docs this geoJSON being set to true turns on geoJSON support/indexing. Here in the docstring nothing of the sort is mentioned, and it implies that it has something to do with coordinate ordering.
https://github.com/ArangoDB-Community/python-arango/blob/86411ef40dc22b51a21eccdce8cc179b46d322f1/arango/collection.py#L1169-L1200

It took me way too long to figure out how to turn on geoJSON support because of this.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions