Skip to content

Consistent handling of optional columns #491

@bifbof

Description

@bifbof

The Trackintel model has two types of columns that it accesses.
The required ones, without which you can't create a Trackintel object, and the optional ones mentioned in the documentation.
The handling of the optional columns is rather confusing

  • some like accuracy are mentioned, but nowhere used with any function
  • some like trips in tours are not mentioned at all, although they are returned every time by the generate_tours function
  • no information is given about what type these optional types should be
  • basically no tests are written for them, e.g. for io functions

We should treat them consistently and define: which ones are really used, their datatypes etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions