admin管理员组

文章数量:1026373

CRS is getting set as undefined, no matter what I run. Not a biggy, but throws a warning when I import to QGIS. Am I doing something wrong, or is it a bug?

My codes:

ogr2ogr -f "GPKG" -nlt POINT -a_srs EPSG:20355 'C:\Test.gpkg' "MSSQL:DSN=dsn;database=DBASE;tables=UV_FI;driver={SQL Server}"

ogrinfo 'C:\Test.gpkg' gpkg_contents -sql "SELECT * FROM gpkg_contents"

OGRFeature(SELECT):0
  table_name (String) = UV_FI
  data_type (String) = features
  identifier (String) = UV_FI
  description (String) =
  last_change (DateTime) = 2024/11/16 20:56:31.966+00
  min_x (Real) = 604072
  min_y (Real) = 7569720
  max_x (Real) = 611630
  max_y (Real) = 7584990
  srs_id (Integer64) = 99999

Possible related to

CRS is getting set as undefined, no matter what I run. Not a biggy, but throws a warning when I import to QGIS. Am I doing something wrong, or is it a bug?

My codes:

ogr2ogr -f "GPKG" -nlt POINT -a_srs EPSG:20355 'C:\Test.gpkg' "MSSQL:DSN=dsn;database=DBASE;tables=UV_FI;driver={SQL Server}"

ogrinfo 'C:\Test.gpkg' gpkg_contents -sql "SELECT * FROM gpkg_contents"

OGRFeature(SELECT):0
  table_name (String) = UV_FI
  data_type (String) = features
  identifier (String) = UV_FI
  description (String) =
  last_change (DateTime) = 2024/11/16 20:56:31.966+00
  min_x (Real) = 604072
  min_y (Real) = 7569720
  max_x (Real) = 611630
  max_y (Real) = 7584990
  srs_id (Integer64) = 99999

Possible related to

本文标签： ogrLosing CRS when writing to GPKG with OGR2OGGDALStack Overflow

版权声明：本文标题：ogr - Losing CRS when writing to GPKG with OGR2OGGDAL - Stack Overflow 内容由热心网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://it.en369.cn/questions/1745642638a2160839.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。