Skip to content

ENH: warning for not setting the crs of trackintel objects #575

@hongyeehh

Description

@hongyeehh

The current read functions in io would proceed without an error or warning when not providing a crs as input; the resulting trackintel class object thus has no crs set (e.g., running print(pfs.crs) will return None). This might cause problems later when running some analysis functions that require a crs, e.g., predict_transport_mode raises a warning: UserWarning: The CRS of your data is not defined..

Shall we add a warning statement if no crs is provided?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestquestionFurther information is requested

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions