Re: [Geoserver-users] App-Schema WMS Support

2016-11-29 Thread Ben Caradoc-Davies 
Kevin,

a common pattern is to deliver WMS with a simple features profile; for 
example, GeoSciML has a bunch of "portrayal" schemas with type names 
ending in "View". If you can resolve your property cardinality mapping, 
these simple features support WMS just like any other. This can also be 
a useful strategy to support WFS clients that are not able to consume 
complex features. They will also be very fast.

Simple features can be served in parallel with your complex features; 
for WMS these can be almost transparent, and you can even craft your 
user interface to guide users back to the complex features discovered 
via WMS.

Kind regards,
Ben.

On 30/11/16 10:19, kweis...@harris.com wrote:
> Hello Ben,
>
> Thanks for the quick response.  I see what you mean about the location of the 
> spatial element within the XML response structure.  Most of our schemas 
> (which I do not control) bury it a few levels deep so I don't think the 
> app-schema plugin will work for us unfortunately.
>
> Thanks again for the help.
>
> Kevin M. Weiss
> Software Engineer
> CRITICAL NETWORKS / HARRIS CORPORATION
> harris.com  / kevin.we...@harris.com
>
>
> -Original Message-
> From: Ben Caradoc-Davies [mailto:b...@transient.nz]
> Sent: Tuesday, November 29, 2016 3:01 PM
> To: Weiss, Kevin <kweis...@harris.com>; geoserver-users@lists.sourceforge.net
> Subject: Re: [Geoserver-users] App-Schema WMS Support
>
> Kevin,
>
> I expect that this is caused by the feature of interest lacking a geometry 
> property at the top-level (an attribute in UML-speak). In the tutorial 
> example, MappedFeature has a geometry property, but GeologicUnit has only an 
> association with zero or more MappedFeatures that describe its location. For 
> example, a geologic unit might be mapped as several outcrops (the 
> gsml:occurrence association). Here is the UML from the GeoSciML 4.0 (the 
> older version in the tutorial is similar):
> http://www.geosciml.org/geosciml/4.0/documentation/html/index.htm?goto=1:3:1:105
>
> I expect app-schema WMS to work for types that have a top-level geometry 
> property. The WMS page also documents limitations on styling with properties 
> from referenced features.
>
> Kind regards,
> Ben.
>
> On 30/11/16 09:09, kweis...@harris.com wrote:
>> Hello all,
>> I'm trying to enable WMS support on an app-schema feature per the 
>> instructions here 
>> (http://docs.geoserver.org/latest/en/user/data/app-schema/wms-support.html). 
>>  The data is retrievable via WFS 2.0 requests, but when I try to request the 
>> product via WMS the client receives a ServiceExceptionReport stating that 
>> "Rendering process failed".  Inspecting the logs it appears to be resulting 
>> from a NullPointerException in StreamingRenderer.java at line 2686.  Moving 
>> up the stack I see a warn message stating that a transform exception 
>> occurred when trying to de-project the current envelope.  It looks like it's 
>> trying to transform the requested BBOX to a null projection.
>>
>> Naturally, I assumed I had screwed something up configuration-wise so I 
>> imported the app-schema tutorial "gsml" workspace and restarted GeoServer to 
>> test.  Oddly enough, "gsml:MappedFeature" displays properly via WMS, but 
>> "gsml:GeologicUnit" causes the same error I saw with my own app-schema 
>> mappings.  Has anyone else seen this behavior?  Am I missing some 
>> configuration value somewhere or is this something I should report via the 
>> bug tracker?
>>
>> The issue was originally discovered using GeoServer 2.9.2, but was 
>> replicated in our environment using GeoServer 2.10.0 as well (using the 
>> appropriately versioned plugins of course).
>>
>> Thanks,
>>
>> Kevin M. Weiss
>> Software Engineer
>> CRITICAL NETWORKS / HARRIS CORPORATION harris.com  /
>> kevin.we...@harris.com
>>
>>
>> --
>>  ___
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
> --
> Ben Caradoc-Davies <b...@transient.nz>
> Director
> Transient Software Limited <http://transient.nz/> New Zealand
>

-- 
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] App-Schema WMS Support

2016-11-29 Thread kweis...@harris.com 
Hello Ben,

Thanks for the quick response.  I see what you mean about the location of the 
spatial element within the XML response structure.  Most of our schemas (which 
I do not control) bury it a few levels deep so I don't think the app-schema 
plugin will work for us unfortunately.

Thanks again for the help.

Kevin M. Weiss
Software Engineer
CRITICAL NETWORKS / HARRIS CORPORATION
harris.com  / kevin.we...@harris.com


-Original Message-
From: Ben Caradoc-Davies [mailto:b...@transient.nz] 
Sent: Tuesday, November 29, 2016 3:01 PM
To: Weiss, Kevin <kweis...@harris.com>; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] App-Schema WMS Support

Kevin,

I expect that this is caused by the feature of interest lacking a geometry 
property at the top-level (an attribute in UML-speak). In the tutorial example, 
MappedFeature has a geometry property, but GeologicUnit has only an association 
with zero or more MappedFeatures that describe its location. For example, a 
geologic unit might be mapped as several outcrops (the gsml:occurrence 
association). Here is the UML from the GeoSciML 4.0 (the older version in the 
tutorial is similar):
http://www.geosciml.org/geosciml/4.0/documentation/html/index.htm?goto=1:3:1:105

I expect app-schema WMS to work for types that have a top-level geometry 
property. The WMS page also documents limitations on styling with properties 
from referenced features.

Kind regards,
Ben.

On 30/11/16 09:09, kweis...@harris.com wrote:
> Hello all,
> I'm trying to enable WMS support on an app-schema feature per the 
> instructions here 
> (http://docs.geoserver.org/latest/en/user/data/app-schema/wms-support.html).  
> The data is retrievable via WFS 2.0 requests, but when I try to request the 
> product via WMS the client receives a ServiceExceptionReport stating that 
> "Rendering process failed".  Inspecting the logs it appears to be resulting 
> from a NullPointerException in StreamingRenderer.java at line 2686.  Moving 
> up the stack I see a warn message stating that a transform exception occurred 
> when trying to de-project the current envelope.  It looks like it's trying to 
> transform the requested BBOX to a null projection.
>
> Naturally, I assumed I had screwed something up configuration-wise so I 
> imported the app-schema tutorial "gsml" workspace and restarted GeoServer to 
> test.  Oddly enough, "gsml:MappedFeature" displays properly via WMS, but 
> "gsml:GeologicUnit" causes the same error I saw with my own app-schema 
> mappings.  Has anyone else seen this behavior?  Am I missing some 
> configuration value somewhere or is this something I should report via the 
> bug tracker?
>
> The issue was originally discovered using GeoServer 2.9.2, but was replicated 
> in our environment using GeoServer 2.10.0 as well (using the appropriately 
> versioned plugins of course).
>
> Thanks,
>
> Kevin M. Weiss
> Software Engineer
> CRITICAL NETWORKS / HARRIS CORPORATION harris.com  / 
> kevin.we...@harris.com
>
>
> --
>  ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/> New Zealand

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] App-Schema WMS Support

2016-11-29 Thread Nuno Oliveira 
Hi,

Layer 'gsml:GeologicUnit' fails the rendering process in WMS because it 
doesn't have any defined geometry, maybe the rendering pipeline should 
be more explicit about this.
Anyway, if you are interested in WMS I guess is because you want to 
actually draw something so a geometry is required :)

Layer 'gsml:MappedFeature' defines the shape geometry property in is 
mappings:


 gsml:shape
 
 SHAPE
 


If you check the associated schema:
http://www.geosciml.org/geosciml/2.0/xsd/geologicFeature.xsd

you can see that the shape property has type 'gml:GeometryPropertyType' 
which mark this property as a geometry property:


 
 
 Points to the GML shape object that describes
 the geometry of the MappedFeature. The shape
 object may have any dimensionality. The shape
 of a mapped feature is determined by observation,
 not assertion
 
 


So if I understood the problem correctly, you basically need to define a 
geometry property in you schema and define the correct mapping.

Regards,

Nuno Oliveira

On 11/29/2016 08:09 PM, kweis...@harris.com wrote:
> Hello all,
> I'm trying to enable WMS support on an app-schema feature per the 
> instructions here 
> (http://docs.geoserver.org/latest/en/user/data/app-schema/wms-support.html).  
> The data is retrievable via WFS 2.0 requests, but when I try to request the 
> product via WMS the client receives a ServiceExceptionReport stating that 
> "Rendering process failed".  Inspecting the logs it appears to be resulting 
> from a NullPointerException in StreamingRenderer.java at line 2686.  Moving 
> up the stack I see a warn message stating that a transform exception occurred 
> when trying to de-project the current envelope.  It looks like it's trying to 
> transform the requested BBOX to a null projection.
>
> Naturally, I assumed I had screwed something up configuration-wise so I 
> imported the app-schema tutorial "gsml" workspace and restarted GeoServer to 
> test.  Oddly enough, "gsml:MappedFeature" displays properly via WMS, but 
> "gsml:GeologicUnit" causes the same error I saw with my own app-schema 
> mappings.  Has anyone else seen this behavior?  Am I missing some 
> configuration value somewhere or is this something I should report via the 
> bug tracker?
>
> The issue was originally discovered using GeoServer 2.9.2, but was replicated 
> in our environment using GeoServer 2.10.0 as well (using the appropriately 
> versioned plugins of course).
>
> Thanks,
>
> Kevin M. Weiss
> Software Engineer
> CRITICAL NETWORKS / HARRIS CORPORATION
> harris.com  / kevin.we...@harris.com
>
>
> --
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

-- 
==
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
mob:   +39  333 8128928

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

Re: [Geoserver-users] App-Schema WMS Support

2016-11-29 Thread Ben Caradoc-Davies 
Kevin,

I expect that this is caused by the feature of interest lacking a 
geometry property at the top-level (an attribute in UML-speak). In the 
tutorial example, MappedFeature has a geometry property, but 
GeologicUnit has only an association with zero or more MappedFeatures 
that describe its location. For example, a geologic unit might be mapped 
as several outcrops (the gsml:occurrence association). Here is the UML 
from the GeoSciML 4.0 (the older version in the tutorial is similar):
http://www.geosciml.org/geosciml/4.0/documentation/html/index.htm?goto=1:3:1:105

I expect app-schema WMS to work for types that have a top-level geometry 
property. The WMS page also documents limitations on styling with 
properties from referenced features.

Kind regards,
Ben.

On 30/11/16 09:09, kweis...@harris.com wrote:
> Hello all,
> I'm trying to enable WMS support on an app-schema feature per the 
> instructions here 
> (http://docs.geoserver.org/latest/en/user/data/app-schema/wms-support.html).  
> The data is retrievable via WFS 2.0 requests, but when I try to request the 
> product via WMS the client receives a ServiceExceptionReport stating that 
> "Rendering process failed".  Inspecting the logs it appears to be resulting 
> from a NullPointerException in StreamingRenderer.java at line 2686.  Moving 
> up the stack I see a warn message stating that a transform exception occurred 
> when trying to de-project the current envelope.  It looks like it's trying to 
> transform the requested BBOX to a null projection.
>
> Naturally, I assumed I had screwed something up configuration-wise so I 
> imported the app-schema tutorial "gsml" workspace and restarted GeoServer to 
> test.  Oddly enough, "gsml:MappedFeature" displays properly via WMS, but 
> "gsml:GeologicUnit" causes the same error I saw with my own app-schema 
> mappings.  Has anyone else seen this behavior?  Am I missing some 
> configuration value somewhere or is this something I should report via the 
> bug tracker?
>
> The issue was originally discovered using GeoServer 2.9.2, but was replicated 
> in our environment using GeoServer 2.10.0 as well (using the appropriately 
> versioned plugins of course).
>
> Thanks,
>
> Kevin M. Weiss
> Software Engineer
> CRITICAL NETWORKS / HARRIS CORPORATION
> harris.com  / kevin.we...@harris.com
>
>
> --
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users