i've just been saving (via /save as) a geopackage in qis (2.18.11) - which worked pretty fine. the output layer CRS information is correctly identified as WGS84 includig EPSG code (4326).

the same geopackage in arcgis 10.4 (and 10.5) is identified as a WGS84 but EPSG information is missing - thus the feature class properties are set to "Custom" by arcgis. as a consequence the relavant information for arcgis' semi-automatic transformation is missing, which results in serious troubles with projection on the fly for any kind of non WGS84-based projection. as far as i could figure out the CRS settings of the geopackage can't be changed within arcgis.

is there

  • a way to verify the CRS-settings of the geopackage (with an external tool) ?
  • a way to edit that settings with any kind of tool ?
  • or a known workaround for arcgis ?
  • In GeoPackage the table "gpkg_contents" is listing all the tables and their srs_id. Or you can read that info from table "gpkg_geometry_columns". Finally run SELECT * FROM "gpkg_spatial_ref_sys" WHERE srs_id=xxxx. If projection is not recognized correctly there must be a bug either in GGIS/GDAL or in ArcGIS.
    – user30184
    Aug 4, 2017 at 14:05

1 Answer 1


Depending on what systems you're running and software you have installed, you can check the meta data using ogrinfo from the command line (if on windows I believe you'll likely need to install the OSGEO4W packages, which you may already have from your QGIS install).

Arc often doesn't read perfectly fine CRS data made outside of Arc, even when it's WGS84, but you can fix this by simply using the define projection tool. It will just redefine the CRS of the layer.

  • thx for the information. ogrinfo returns <br> GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS 84",6378137,298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich",0, AUTHORITY["EPSG","8901"]], UNIT["degree",0.0174532925199433, AUTHORITY["EPSG","9122"]], AUTHORITY["EPSG","4326"]] <br> which seems quite ok ... and thus should be ok for ArcGIS as well
    – robert tuw
    Aug 4, 2017 at 12:14
  • ... and ArcGIS' define projection tool returns an error - "cannot alter the spatial reference of xxxxx", seems that the tool doesn't change geopackages' properties
    – robert tuw
    Aug 4, 2017 at 12:23
  • If the subtle difference is still causing problems you could try to use ogr2ogr (again on the command line) using the -update and -a_src flags to redefine the projection to what makes Arc happy. I've previously pulled the WKT of the CRS from files that Arc reads happily (using ogrinfo again) or maybe here (spatialreference.org/ref/epsg/wgs-84/esriwkt).
    – scabecks
    Aug 6, 2017 at 3:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.