You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry, just noticed this. I dont actually use this email address regularly.
We are likely to re-start the OWS Context SWG Meetings soon. We are trying
to tie up the loose ends of the GeoJSON Encoding release as a standard
right now.
Actually we have discussed this. My personal opinion is that the 'Content'
element is the wrong place as this is typically reserved for the actual
content (data returned).
I personally would either put it in a fake 'POST' box in a service offering
or create a custom type (transactionalOffering).
Happy to discuss, but i suggest you mail mail me roger.brackin@envitia.com
directly. I dont know if you are a swg observer, if so mail the ows Context
list.
We can put it on the Agenda for a meeting in the next few weeks.
BTW if you change the namespace to your own. "www.acme.org' etc, you can do
whatever you want, at least for experimentation purposes.
As discussed at https://github.com/pka/qgpkg/blob/master/ows_geopackage_extension.md and opengeospatial/geopackage#270 it would be interesting to have geopackage as an offering similar to KML/GML. Challenge is how to reference a specific table in the geopackage, I like the proposal by @pepijnve to include the table-name with a hash
a geopackage offering could thus be expressed as
The text was updated successfully, but these errors were encountered: