Closed vincentvanhees closed 1 month ago
Instead of making this flexible, I now think it is much more important to document clearly the data format that is expected. This is not clear from the existing documentation. Next, I think it is a lot easier for hbGIS users to adept their file column names. Revising hbGIS to handle more column name variations is unattractive because it requires extra time investment and it increases code complexity and by that maintainability.
Currently the code is strict about the expected column name in which the identifier is stored for locations that are linked to an individual. It would be good to make this flexible. For example: