Recently, I had the occasion to attempt to generate an OGC GeoPackage from QGIS and publish it using GeoServer. The use case was fairly straightforward. I had been given data in GML format and needed to publish it. For many valid reasons (such as lack of spatial indexing), GeoServer does not natively support publishing GML data. As a result, I need to convert it to something that GeoServer did support.
QGIS opened and displayed the data easily and, from there, I could export it into any number of formats. (Or I could have used OGR.) The feature attributes had very long names and I didn’t want to lose that richness by exporting to shapefile. I was trying to keep my server-side life simple, so I was hoping to avoid setting up an RDBMS data store for this purpose. It was then that I noticed QGIS supports exporting to GeoPackge, so I decided to give it a go.
For purposes of this post, I am using a shapefile of building footprints of Leonardtown, Maryland. The process is the same for a GML file, however.
As shown below, you initiate the process like any other by right-clicking and choosing “Save As…” in the context menu.
Continue reading “Publishing GeoPackage to GeoServer Using QGIS”
Those are my words, not theirs.
It came to light today that OGC has decided to withdraw the GeoServices REST Specification, also known as the “ESRI REST API,” as a proposed standard. I will not take up the relative merits of the specification or the implications of OGC potentially adopting an industry-developed specification that has so much implied workflow embedded in it. With this decision, three facts remain unaltered:
- The ESRI REST API will continue forward as a widely-used de facto standard in the form of ArcGIS Server installs and other emulations, such as that in Arc2Earth.
- GeoJSON will continue forward as a widely-used de facto standard in the form of numerous open-source implementations.
- OGC still has no JSON syntax.
Yes, twelve years after the birth of JSON, five years after the release of the ESRI REST API and its embedded JSON syntax, and five years after the release of GeoJSON 1.0, OGC is still has no entry in the JSON space. Between Esri and GeoJSON, the utility of JSON in web mapping applications has been roundly proven. In the ESRI arena, find me anyone who willingly uses the SOAP API these days while the adoption of support for GeoJSON across the open-source GIS world speaks volumes. The industry has voted with its feet and its code as to what it prefers.
Continue reading “OGC Abandons the Web”
The Open Geospatial Consortium (OGC) has published a draft GeoPackage specification for comment. The GeoPackage specification attempts to create a non-proprietary means for packaging and exchanging all geospatial data in all its forms (vector, raster, and tiles). A couple of things that jump out at me:
- It calls out SQLite as the reference implementation of a GeoPackage container
- It calls out SpatiaLite 4 as the reference implementation of a vector feature store
- It does not call out a reference implementation for rasters or tiles
- It does not mention exchange of cartography.
Continue reading “Comment Period Open for GeoPackage Specification Draft”
So this is what I get for missing the Ignite sessions at WhereCampDC*:
*I got to dance with my daughter and help her chase fireflies so I win.
The worst-kept rumor/secret in recent memory is now “out there” so here are my thoughts:
Continue reading “GeoServices REST Specification and OGC”