Skip to content

Hardcoded SPATIAL_REF_SYS_CSV makes it awkward to package #683

@Diviloper

Description

@Diviloper

Is your feature request related to a problem? Please describe.
When building a self-contained PyMEOS wheel, the idea is that all required data is contained in the wheel. Since the path to the csv containing the spatial reference systems (SPATIAL_REF_SYS_CSV) is hardcoded and cannot be change after build time, it is impossible to set at runtime, which is the method that I was using in PyMEOS for other data (such as the proj data).

Describe the solution you'd like
The ability to modify SPATIAL_REF_SYS_CSV at runtime.

Describe alternatives you've considered
I've considered (although not really tried) to compile MEOS overriding the definition of SPATIAL_REF_SYS_CSV with the relative path of where the file will be located in the wheel. However, I'm not sure if this would work, since if I'm not mistaken, a relative path would start looking from when the program using the library is executed, and not from the library root folder.
I've also considered just copying the csv file to the hardcoded path on install, but this seems a bit shabby.

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