OGC Geopackage seems promising format for sharing and editing spatial data. FME (2016) is now supporting its core geometry types, but it would be good if FME would support also its additional geometry types (including arcs) as described in Geopackage standard: http://www.geopackage.org/spec/#extension_geometry_types
Released
OGC Geopackage additional geometry types
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.
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.
+22- Safer
The team advises that CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE and MULTISURFACE are possible for us to support but we don't in FME 2017.0. FME 2017.0 does add Raster to Geopackage however. We also support updates too.
We're targetting FME 2017.1 to add support for these types, and also non-spatial data in Geopackage following the protocol that our friends over at OGR/GDAL have embraced.
@tiiipponen we have added support for circular arcs in FME 2017.1 .
Also, you can now create table with no geometry column. On the Geopackage feature type, uncheck the Spatial in the Table Creation Parameters
'
+10- Contributor
But what about the gpkg Reader? Does that read the GDAL option correctly? Should the output for aspatial tables have the geometry column REMOVED, not just set to null geometry?
Otherwise other vendors cannot read the results in a spatialite database output if they have not implemented the extension.
+10- Contributor
Hello kimo
FME 2017.1 and newer can handle aspatial tables, according to aspatial extension introduced by GDAL some time ago. It can also handle attribute tables according to GeoPackage 1.2 standard.
In the GPKG writer you can decide which variant you want, as described by @MarkAtSafe below.
FME GPKG reader can deal with it fairly well afaik and tested. If other systems will be able to deal with it depends on the GDAL version integrated in the other client.
QGIS handles everything well. ESRI (up to 10.5 for sure and for 10.6 I don't know) is still sticking with GPKG 1.1 which does not support attribute tables and several geometry types. Sad to say but that's how it is for now.