EPOS

h1. About WFS App Schema for BoreholeView

https://epos.brgm-rec.fr/geoserver/ows?service=wfs&version=2.0.0&request=GetFeature&TYPENAMES=gsmlp:BoreholeView&OUTPUTFORMAT=text/xml;%20subtype=gml/3.2&count=1&resolveDepth=*

h2. # Trusted environment

This app schema has been successfully set up with those versions of GeoServer:

- BRGM ressource-rec: GeoServer 2.8.0

- BRGM epos-rec: GeoServer 2.9.2

h2. # Link to resources

Several content are offered in https://forge.brgm.fr/svnrepository/epos/trunk/tools/geoserver/

h1. # Tips for configuration of App-schema

h2. ## workspace

The content of workspaces (the gsmlp folder) should be put in your geoserver/data/workspaces.

h2. ## DB part (for xsd version 1.0.0)

App schema provided in SVN is actually set up for one table called "borehole_eu" with those columns:

 CREATE TABLE epos.borehole_eu

(

  boreholeid character varying NOT NULL,

  gmlidentifier character varying,

  name character varying,

  gsmlpidentifier character varying,

  description text,

  purpose_href character varying(255),

  purpose character varying(255),

  boreholeuse text,

  boreholeuse_href character varying(255),

  status_href character varying(255),

  status character varying(30),

  drillingmethod_href character varying(255),

  drillingmethod text,

  operator text,

  driller character varying(50),

  drillstartdate date,

  drillenddate date,

  startpoint_href character varying(255),

  startpoint character varying(30),

  inclinationtype_href character varying(255),

  inclinationtype character varying(30),

  boreholematerialcustodian text,

  boreholelength_m real,

  elevation_m real,

  elevation_srs character varying,

  source character varying,

  parentborehole_uri character varying,

  metadata_uri character varying,

  genericsymbolizer character varying(255),

  cored boolean,

  accesstophysicaldrillcore boolean,

  detaileddescription character varying(255),

  detaileddescription_href character varying(255),

  geophysicallogs character varying(255),

  geophysicallogs_href character varying(255),

  geologicaldescription character varying(255),

  geologicaldescription_href character varying(255),

  groundwaterlevel character varying(255),

  groundwaterlevel_href character varying(255),

  groundwaterchemistry character varying(255),

  groundwaterchemistry_href character varying(255),

  rockgeochemistry character varying(255),

  rockgeochemistry_href character varying(255),

  poregaschemistry character varying(255),

  poregaschemistry_href character varying(255),

  geotechnicalinfo character varying(255),

  geotechnicalinfo_href character varying(255),

  location_wgs84 geometry,

  positionalaccuracy text,

  CONSTRAINT pk_borehole_eu_06_on_boreholeid PRIMARY KEY (boreholeid)

)

h2. ## app-schema.properties

The datastore part from gsmlp_BoreholeView.xml is linked to a app-schema.properties file.

This file actually indicate how app-schema should connect to your database.

It should be put in geoserver/WEB-INF/classes.

h2. ## GML namespace and workspace

If GML namespace is not appearing in your BoreholeView response(replaced by null, e.g. null:name).

- Check in your GeoServer that gml namespace and workspace are properly set and attached to GML v3.2.

- Check in your "BoreholeView.xml" mapping that reference to GML is also pointing v3.2.