<html><head></head><body><div class="yahoo-style-wrap" style="font-family:verdana, helvetica, sans-serif;font-size:13px;"><div>In Vol 227, Issue 8 I explained my bewilderment that the processes I have used throughout the existence of Geopackages were now not working. I was able to solve this by downloading the latest Spatialite and using the spatialite.exe command processor.<br><br>The successful command was of the form: SELECT AddGeometryColumn('','control','geom_control','4269','POINT',2,true); This had worked with an earlier version of spatialite_gui.exe (2.0.0-devel) Same software. Now, no go.<br><br>The other problem was having populated geometry fields that were not recognized as geometry fields. I had mistakenly been populating the geopackage geometry columns with binary data from PostGIS tables. <br><br>I remedied this by exporting the data from PostGIS as textual geometries, then imported into geopackage fields as ST_GeomFromText(). A nice project would be to have both softwares recognize the other's standards and accommodate.<br><br>An unsolved part of my mystery remains. Why can't we convert PostGIS tables to geopackage tables and retain the Primary Fields as GUIDs? I was able to work around this for now.<br><br>I regret providing a link to my free PDF book without clarifying that I am not trying to sell anything. It is not a trap.<br><br>Dennis K. McKay<br>Retired Federal Cadastral Surveyor</div><div><br></div></div></body></html>