Hexagon Geospatial


Need a push in the right direction when configuring WebMap, Portal or SDI services? Looking for hints and tips, or just looking for Ideas and information? The WebGIS discussion board is where you start those discussions, connect and share information.
Showing results for 
Search instead for 
Do you mean 
Posts: 74
Registered: ‎03-08-2017
Accepted Solution

SDI 6.1 to Geomedia WebMap 2015 - WFS filter clause malformed



we currently have a setup like this : Client --> SDI 6.1 --> Geomedia WebMap 2015.


The WFS GetFeature query is received by SDI with a BBOX Parameter. SDI, which is used as a facade replaces the BBOX for a filter parameter which lacks srsName in Envelope :


<Envelope xmlns="http://www.opengis.net/gml">


should be :


<Envelope xmlns="http://www.opengis.net/gml" srsName="EPSG:XXXX">


If the srsName is not present, Geomedia 2015 returns <gml:null>missing</gml:null> and if present everything works fine.


Is there a way to prevent SDI from modifying the received query and make it send it as received (with only http://xxxx/) replaced ? If not is it possible to always add srsName parameter ?





Posts: 294
Registered: ‎11-05-2015

Re: SDI 6.1 to Geomedia WebMap 2015 - WFS filter clause malformed

It will be really hard to reason on the exact logic of the ancient 6.1 version of SDI (especially, since there were differences between revisions, i.e. the third number in the version - do you have 6.1.8 or 6.1.10?).


The exact behavior you experience (WFS Facade translating the KVP BBOX into a filter expression) has been fixed in 15 EP4 of Geospatial SDI.



One thing you could try is to use the fully qualified form of the KVP BBOX parameter, that is - to provide the srsName in it. So instead of BBOX=minx,miny,maxx,maxy it would look like BBOX=minx,miny,maxx,maxy,srsName

Would that change anything?

Posts: 74
Registered: ‎03-08-2017

Re: SDI 6.1 to Geomedia WebMap 2015 - WFS filter clause malformed



thanks for your reply.


We already pass the srsName as bbox's fifth parameter and there's no effect on gml filter.


We ended up using SDI 2015 and the problem is gone.



Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.