Due to the source and use in combination with other Statbel-datasets, the variable names in the spatial datasets are relatively non-intuitive and unstandardized (lower/uppercase, point/underscore, current and historical identifiers, etc.).
This is logical for users using this package in combination with other Statbel-datasets with similar identifiers, but not so much if the package is used as such, i.e. an R-friendly source of detailed Belgian administrative spatial objects to which you can add your own data. In this case generic but consistent naming of variables becomes more relevant.
How to deal with this depends a bit on the goals/use of the package, i.e. more generic as "BelgiumMaps" or more specific as "BelgiumMaps.StatBel".
Due to the source and use in combination with other Statbel-datasets, the variable names in the spatial datasets are relatively non-intuitive and unstandardized (lower/uppercase, point/underscore, current and historical identifiers, etc.).
This is logical for users using this package in combination with other Statbel-datasets with similar identifiers, but not so much if the package is used as such, i.e. an R-friendly source of detailed Belgian administrative spatial objects to which you can add your own data. In this case generic but consistent naming of variables becomes more relevant.
How to deal with this depends a bit on the goals/use of the package, i.e. more generic as "BelgiumMaps" or more specific as "BelgiumMaps.StatBel".