EPOS

h1. About WFS App Schema for BoreholeView

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

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

  boreholeid character varying NOT NULL,

  identifier character varying,

  name character varying,

  description character varying(255),

  purpose_href character varying(255),

  purpose character varying(50),

  status_href character varying(255),

  status character varying(30),

  drillingmethod_href character varying(255),

  drillingmethod character varying(50),

  operator character varying(50),

  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 character varying(50),

  boreholelength_m real,

  elevation_m real,

  elevation_srs character varying,

  positionalaccuracy real,

  source character varying,

  parentborehole_uri character varying,

  metadata_uri character varying,

  genericsymbolizer character varying(50),

  cored boolean,

  accesstophysicaldrillcore boolean,

  existsdetaileddescription boolean,

  existsgeophysicallogs boolean,

  existsgeologicaldescription boolean,

  existsgroundwaterlevel boolean,

  existsrockgeochemistry boolean,

  existsporegaschemistry boolean,

  existsgeotechnicalinfo boolean,

  existsgroundwaterchemistry boolean,

  location_wgs84 geometry,

h2. ## app-schema.properties

This file should be put in geoserver/WEB-INF/classes.

Information from it are used by the datastore part of the gsmlp_BoreholeView.xml file from workspaces.

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