[Geoserver-devel] App-Schema mappings default geometry

GeoServer GeoServer Developer
1

Hi all,

Currently is not possible to specify in App-Schema mappings the default geometry of a mapped feature type,
note that having a default geometry defined is mainly important for WMS.

Most of the times a geometry will be available in the root feature type and a default geometry will be correctly
and automatically selected.

But in certain situations a feature type may have multiple geometries, or the geometry may be nested,
for example:

<wfs:member>

  <st:Station gml:id​ = "station.st.1"​>

    <st:name>​station1​</st:name>

    <st:location>

      <st:name>​Europe​</st:name>

      **<st:position>**

**        <gml:Point srsDimension​="2"**

**          srsName​=["http://www.opengis.net/gml/srs/epsg.xml#4326"](http://www.opengis.net/gml/srs/epsg.xml#4326)​ >**

**          <gml:pos>​-1.0 1.0​</gml:pos>**

**        </gml:Point>**

**      </st:position>**

    </st:location>

  </st:Station>

</wfs:member>

In this case the geometry is nested inside the location element. I propose to extend App-Schema
mappings to allows us to define explicitly the default geometry:

<FeatureTypeMapping>

  <sourceDataStore>​stations​</sourceDataStore>

  <sourceType>​stations​</sourceType>

  <targetElement>​st:Station​</targetElement>

  **<defaultGeometry>st:location/st:position</defaultGeometry>**

  <attributeMappings>

    <AttributeMapping>

      <targetAttribute>​st:Station​</targetAttribute>

      <idExpression>

        <OCQL>​strConcat('station.', ID)​</OCQL>

      </idExpression>

    </AttributeMapping>

Any objection or comments ?

Cheers,

Nuno Oliveira

··· 
-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit [http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_it](http://twitter.com/geosolutions_it)

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
 
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.
2

Nuno,

that sounds like a useful improvement. One consideration is what happens when a nested geometry is multivalued and has a cardinality of zero or more than one. Also, do you anticipate that your implementation will work with nested properties generated by feature chaining? I am thinking of joining and filtering with spatial predicates.

Please also update <modules/extension/app-schema/app-schema/src/test/resources/test-data/AppSchemaDataAccess.xsd> to include this new element. I think this is still the canonical source for the schema, although we do not yet have a good way of distributing it.

Kind regards,
Ben.

On 19/02/18 22:29, Nuno Oliveira wrote:

Hi all,

Currently is not possible to specify in App-Schema mappings the default geometry of a mapped feature type,
note that having a default geometry defined is mainly important for WMS.

Most of the times a geometry will be available in the root feature type and a default geometry will be correctly
and automatically selected.

But in certain situations a feature type may have multiple geometries, or the geometry may be nested,
for example:

&lt;wfs:member&gt;

   &lt;st:Station gml:id​ = &quot;station\.st\.1&quot;​&gt;

     &lt;st:name&gt;​station1​&lt;/st:name&gt;

     &lt;st:location&gt;

       &lt;st:name&gt;​Europe​&lt;/st:name&gt;

\*&lt;st:position&gt;\*

\*         &lt;gml:Point srsDimension​=&quot;2&quot;\*

\*           srsName​=&quot;http://www.opengis.net/gml/srs/epsg.xml#4326&quot;​ &gt;\*

\*           &lt;gml:pos&gt;​\-1\.0 1\.0​&lt;/gml:pos&gt;\*

\*         &lt;/gml:Point&gt;\*

\*       &lt;/st:position&gt;\*

     &lt;/st:location&gt;

   &lt;/st:Station&gt;

&lt;/wfs:member&gt;

In this case the geometry is nested inside the location element. I propose to extend App-Schema
mappings to allows us to define explicitly the default geometry:

&lt;FeatureTypeMapping&gt;

   &lt;sourceDataStore&gt;​stations​&lt;/sourceDataStore&gt;

   &lt;sourceType&gt;​stations​&lt;/sourceType&gt;

   &lt;targetElement&gt;​st:Station​&lt;/targetElement&gt;

\*&lt;defaultGeometry&gt;st:location/st:position&lt;/defaultGeometry&gt;\*

   &lt;attributeMappings&gt;

     &lt;AttributeMapping&gt;

       &lt;targetAttribute&gt;​st:Station​&lt;/targetAttribute&gt;

       &lt;idExpression&gt;

         &lt;OCQL&gt;​strConcat\(&#39;station\.&#39;, ID\)​&lt;/OCQL&gt;

       &lt;/idExpression&gt;

     &lt;/AttributeMapping&gt;

Any objection or comments ?

Cheers,

Nuno Oliveira

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <https://transient.nz/&gt;
New Zealand

3

Hi Ben,

Thank you for the feedback :slight_smile:

In the first step nested properties generated by feature chaining will be ignored, the default geometry will need to be a mapped property of the feature type.
Then, this may be extended to support the use case of having a chained feature with cardinality 0 or 1.

Thank you for the heads up regarding the AppSchemaDataAcess schema, I will update it.

Regards,

Nuno Oliveira

On 02/19/2018 10:42 PM, Ben Caradoc-Davies wrote:

Nuno,

that sounds like a useful improvement. One consideration is what happens when a nested geometry is multivalued and has a cardinality of zero or more than one. Also, do you anticipate that your implementation will work with nested properties generated by feature chaining? I am thinking of joining and filtering with spatial predicates.

Please also update <modules/extension/app-schema/app-schema/src/test/resources/test-data/AppSchemaDataAccess.xsd> to include this new element. I think this is still the canonical source for the schema, although we do not yet have a good way of distributing it.

Kind regards,
Ben.

On 19/02/18 22:29, Nuno Oliveira wrote:

Hi all,

Currently is not possible to specify in App-Schema mappings the default geometry of a mapped feature type,
note that having a default geometry defined is mainly important for WMS.

Most of the times a geometry will be available in the root feature type and a default geometry will be correctly
and automatically selected.

But in certain situations a feature type may have multiple geometries, or the geometry may be nested,
for example:

&lt;wfs:member&gt;

   &lt;st:Station gml:id​ = &quot;station\.st\.1&quot;​&gt;

     &lt;st:name&gt;​station1​&lt;/st:name&gt;

     &lt;st:location&gt;

       &lt;st:name&gt;​Europe​&lt;/st:name&gt;

\*&lt;st:position&gt;\*

\*         &lt;gml:Point srsDimension​=&quot;2&quot;\*

\* srsName​=&quot;http://www.opengis.net/gml/srs/epsg.xml#4326&quot;​ &gt;\*

\*           &lt;gml:pos&gt;​\-1\.0 1\.0​&lt;/gml:pos&gt;\*

\*         &lt;/gml:Point&gt;\*

\*       &lt;/st:position&gt;\*

     &lt;/st:location&gt;

   &lt;/st:Station&gt;

&lt;/wfs:member&gt;

In this case the geometry is nested inside the location element. I propose to extend App-Schema
mappings to allows us to define explicitly the default geometry:

&lt;FeatureTypeMapping&gt;

   &lt;sourceDataStore&gt;​stations​&lt;/sourceDataStore&gt;

   &lt;sourceType&gt;​stations​&lt;/sourceType&gt;

   &lt;targetElement&gt;​st:Station​&lt;/targetElement&gt;

*<defaultGeometry>st:location/st:position</defaultGeometry>*

   &lt;attributeMappings&gt;

     &lt;AttributeMapping&gt;

<targetAttribute>​st:Station​</targetAttribute>

       &lt;idExpression&gt;

         &lt;OCQL&gt;​strConcat\(&#39;station\.&#39;, ID\)​&lt;/OCQL&gt;

       &lt;/idExpression&gt;

     &lt;/AttributeMapping&gt;

Any objection or comments ?

Cheers,

Nuno Oliveira

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Regards,
Nuno Oliveira

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
  The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.