[Geoserver-users] LayerFeatureConstraints and BasMapLayers in POST GetMap request

Hello,

I’m trying to execute a GetMap request through POST. The Get request work great, but the Post request is complaining about two things:

  • the layer VLakgericht (a basemaplayer) is unknown
  • LayerFeatureConstraints not implemented yet.

How to get the basemaplayer throug an post request and is the LayerFeatureConstraints implementation comming anytime soon? (1’m working with geoserver 1.5.4)

Attached are the GET and POST request

Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com

De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:

http://www.denhaag.nl/disclaimer

GetMapPost.txt (2.66 KB)

GetMapGet.txt (738 Bytes)

Hi Kris,

I believe the problem with your requests is that the layer names are
namespace prefix qualified. For instance "topp:states". An alternative
is to declare them in the default namespace on the server. For instance,
out of the box "topp" is the default, so just "states" will suffice.
However just "tiger_roads" will not. You must use "tiger:tiger_roads".

If that does not fix the problem can you include the geoserver logs? Thanks.

As for LayerFeatureConstraints implementation, there is no immediate
plan to do so. Unfortunately there is no project which has a use case
for that functionality at the moment. We are of course willing to accept
a patch or point you at someone who you can pay to do it :).

-Justin

K Geusebroek wrote:

Hello,

I'm trying to execute a GetMap request through POST. The Get request
work great, but the Post request is complaining about two things:

- the layer VLakgericht (a basemaplayer) is unknown
- LayerFeatureConstraints not implemented yet.

How to get the basemaplayer throug an post request and is the
LayerFeatureConstraints implementation comming anytime soon? (1'm
working with geoserver 1.5.4)

Attached are the GET and POST request

Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com
<mailto:k.geusebroek@anonymised.com>

De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:

http://www.denhaag.nl/disclaimer

!DSPAM:4007,4734200e254028992556831!

------------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

!DSPAM:4007,4734200e254028992556831!

------------------------------------------------------------------------

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

!DSPAM:4007,4734200e254028992556831!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Hello Justin,

I’ve tried the option with and without the namespace. I digged into the code and found that there just wasn’t support for the basemapgroup layers in the post version of the getmap request.

Attached you’ll find a patch that solves this issue.

I’m willing to dig in a little deaper into the layerfeatureconstraints issue to maybe make a patch myself. Can you or anybody point me in the right direction on where to look for the precise implementation en where the code should be.

Thank in advance

Kris

Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com

Justin Deoliveira jdeolive@anonymised.com 11/11/07 11:59 >>>

Hi Kris,

I believe the problem with your requests is that the layer names are
namespace prefix qualified. For instance “topp:states”. An alternative
is to declare them in the default namespace on the server. For instance,
out of the box “topp” is the default, so just “states” will suffice.
However just “tiger_roads” will not. You must use “tiger:tiger_roads”.

If that does not fix the problem can you include the geoserver logs? Thanks.

As for LayerFeatureConstraints implementation, there is no immediate
plan to do so. Unfortunately there is no project which has a use case
for that functionality at the moment. We are of course willing to accept
a patch or point you at someone who you can pay to do it :).

-Justin

K Geusebroek wrote:

Hello,

I’m trying to execute a GetMap request through POST. The Get request
work great, but the Post request is complaining about two things:

  • the layer VLakgericht (a basemaplayer) is unknown
  • LayerFeatureConstraints not implemented yet.

How to get the basemaplayer throug an post request and is the
LayerFeatureConstraints implementation comming anytime soon? (1’m
working with geoserver 1.5.4)

Attached are the GET and POST request

Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com
<mailto:k.geusebroek@anonymised.com>

De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:

http://www.denhaag.nl/disclaimer

!DSPAM:4007,4734200e254028992556831!



This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

!DSPAM:4007,4734200e254028992556831!



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

!DSPAM:4007,4734200e254028992556831!


Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:

http://www.denhaag.nl/disclaimer

geoserver-wms-post-basemap-20071112a.patch (4.63 KB)

Sweet, thanks for the patch Kris!! Created a jira task for this patch as
well:

http://jira.codehaus.org/browse/GEOS-1503

I will get to these two issues tonight at some point.

As for support for feature layer constraints, i will have to look into
it a bit to give you a good answer. However off the top of my head it
will involve:

1. Patching SLDParser.java in geotools. Do e search for
"LayerFeatureConstraints" and you should see

2. Patching StreamingRenderer. The rendering subsystem is not by forte
but I think you will have modify the rendering code to check the style
for a filter in the LayerFeatureTYpe constraints, and use it when
accessing hte datastore to render.

Andrea should be able to provide a better idea of whats involved for 2.
I will look into it a bit tonight and give you a more detailed answer.

-Justin

K Geusebroek wrote:

Hello Justin,

I've tried the option with and without the namespace. I digged into the
code and found that there just wasn't support for the basemapgroup
layers in the post version of the getmap request.

Attached you'll find a patch that solves this issue.

I'm willing to dig in a little deaper into the layerfeatureconstraints
issue to maybe make a patch myself. Can you or anybody point me in the
right direction on where to look for the precise implementation en where
the code should be.

Thank in advance

Kris

Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com
<mailto:k.geusebroek@anonymised.com>

Justin Deoliveira <jdeolive@anonymised.com> 11/11/07 11:59 >>>

Hi Kris,

I believe the problem with your requests is that the layer names are
namespace prefix qualified. For instance "topp:states". An alternative
is to declare them in the default namespace on the server. For instance,
out of the box "topp" is the default, so just "states" will suffice.
However just "tiger_roads" will not. You must use "tiger:tiger_roads".

If that does not fix the problem can you include the geoserver logs? Thanks.

As for LayerFeatureConstraints implementation, there is no immediate
plan to do so. Unfortunately there is no project which has a use case
for that functionality at the moment. We are of course willing to accept
a patch or point you at someone who you can pay to do it :).

-Justin

K Geusebroek wrote:

Hello,

I'm trying to execute a GetMap request through POST. The Get request
work great, but the Post request is complaining about two things:

- the layer VLakgericht (a basemaplayer) is unknown
- LayerFeatureConstraints not implemented yet.

How to get the basemaplayer throug an post request and is the
LayerFeatureConstraints implementation comming anytime soon? (1'm
working with geoserver 1.5.4)

Attached are the GET and POST request

Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com
<mailto:k.geusebroek@anonymised.com>

De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt

u op:

http://www.denhaag.nl/disclaimer

------------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

!DSPAM:4007,4734200e254028992556831!

------------------------------------------------------------------------

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

!DSPAM:4007,4734200e254028992556831!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:

http://www.denhaag.nl/disclaimer

!DSPAM:4007,473820f526518362916074!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira ha scritto:

Sweet, thanks for the patch Kris!! Created a jira task for this patch as
well:

http://jira.codehaus.org/browse/GEOS-1503

I will get to these two issues tonight at some point.

As for support for feature layer constraints, i will have to look into
it a bit to give you a good answer. However off the top of my head it
will involve:

1. Patching SLDParser.java in geotools. Do e search for
"LayerFeatureConstraints" and you should see

That I already added to support remote layers, not sure
it's picked up when the layer is not remote thought.

2. Patching StreamingRenderer. The rendering subsystem is not by forte
but I think you will have modify the rendering code to check the style
for a filter in the LayerFeatureTYpe constraints, and use it when
accessing hte datastore to render.

Hmmm.... what about having the MapContext setup deal with this?

Andrea should be able to provide a better idea of whats involved for 2.
I will look into it a bit tonight and give you a more detailed answer.

Cheers
Andrea