Skip to main content
Released

GeoPackage-writer registers the proper geometry type in GPKG_GEOMETRY_COLUMNS fo

Related products:FME Form
  • March 27, 2018
  • 3 replies
  • 57 views

***Note from Migration:***

Original Title was: GeoPackage-writer registers the proper geometry type in GPKG_GEOMETRY_COLUMNS for tables with features of a single geometry-type


Feature tables in GeoPackage are registered in the GPKG_GEOMETRY_COLUMNS table with their geometry column, SRS and geometry type. Right now FME registers all tables with the common geometry type GEOMETRY. For tables that contains features with only one single geometry type FME should register this geometry type in the GPKG_GEOMETRY_COLUMNS table

as defined in the GeoPackage-specification. For example, a table with only point features (geopackage_type: wkb_point) should be registered as a POINT geometry type instead of the GEOMETRY geometry type. This will help other applications (like QGIS, for example) to better understand the contents of the GeoPackage table.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

bruceharold
Influencer
Forum|alt.badge.img+19
  • Influencer
  • March 29, 2018

Excellent idea - gets my vote!


jorge_rosales
Contributor
Forum|alt.badge.img+8
  • Contributor
  • September 26, 2019

I agree. In fact, a GeoPackage database is a "custom" SpatiaLite database, FME allows geometry selection for SpatialLite (set "Create Generic Spatial Columns" to "No") but not for GeoPackage.

 


Forum|alt.badge.img+2

Completed for FME 2020.0