3

I am the technical lead of GA’s effort to adopt GeodesyML. I see that you’ve solved your problem by upgrading to a later version of GeoServer. I would like to suggest a slightly different approach to your mapping and share with you our own implementation of a GeodesyML web feature service, which you may find helpful. Our interpretation is that GeodesyML ...


2

I was also struggling with this same issue where I could not add variables from .properties files inside data_dir configuration files even if app-schema.properties path was set as system variable. Solution for me was to use environment variables that I could add on runtime environment. For example inside datastore.xml file I could reference environment ...


1

You need to add a primary key metadata table as described in the manual to tell GeoServer which column to use as your primary key.


1

Support for viewParams is up to the specific datastore, the needs to be special code to handle them. For example, here is the handling of view params in JDBC data stores (e.g., PostGIS, Oracle, SQL Server and so on), as part of the "SQL view" mechanism (dubbed "virtual table" down in GeoTools): https://github.com/geotools/geotools/blob/...


1

GeoServer App schema, allows you to map your complex data to a schema, so that you can serve your data though a WFS (a complex feature WFS). The WFS requests that come from the client (in this case QGIS) are the same as they would be for a simple feature WFS. In any WFS, the data is sent without any styling. It's the clients responsibility to parse the ...


1

As @nmtoken mentioned before, HALE can work with complex features. The thing is, that the plugin in hale studio that do an export to a GeoServer AppSchema mapping only supports a PostGIS source schema. To make a long story short: for my approach it's not possible to use HALE, because my data is stored in a gml file. For more details see the Plugin ...


Only top voted, non community-wiki answers of a minimum length are eligible