Skip to content

Check robustness of CRS specifications in tutorials #164

Description

@florisvdh

Given current migrations of CRS representation in sp, sf>=0.9-0, rgdal and dependent packages, our tutorials will need to be checked for existing non-compliant CRS specifications. This may be needed repeatedly, as things are still evolving (both in PROJ & GDAL and in the major R packages).

Also some packages, e.g. raster (see https://github.com/rspatial/raster/issues), are currently not yet compliant, hence they must be used with care at least with PROJ >=6 (but e.g. with sf as well).

In general, changes in geospatial packages are ongoing and more changes are to be expected, at least in the function's output.

For now: avoid hard-coded proj4strings, including things like "+init=epsg:31370". More info and coding examples:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions