Hi everyone! I have an issue that I’m struggling to resolve and I’m hoping someone may be able to assist or guide me.
I am trying to use the GetMap feature from the WMS service (which works). However it seems when I add a cql_filter to the url, I get an error message that the request is invalid. If I remove some other get fields within the url (layers in particular - which shortens the url), then I get a response.
It seems that when the url is over 200+ characters, I get the issue. My question is, can I somehow get geoserver to accept longer URLs? I cannot use POST because my implementation uses Mapbox which calls a url and not post variables.
CAUTION: This email originated from outside of RPS.
Hi everyone! I have an issue that I’m struggling to resolve and I’m hoping someone may be able to assist or guide me.
I am trying to use the GetMap feature from the WMS service (which works). However it seems when I add a cql_filter to the url, I get an error message that the request is invalid. If I remove some other get fields within the url (layers in particular - which shortens the url), then I get a response.
It seems that when the url is over 200+ characters, I get the issue. My question is, can I somehow get geoserver to accept longer URLs? I cannot use POST because my implementation uses Mapbox which calls a url and not post variables.
So in terms of if I’m using Tomcat to serve Geoserver, I’m not certain - I am using a standard install so I thought this used the built-in webserver - which I assume is Java?
Secondly, while joining two layers together might help a bit to keep the url length down - it won’t be a permanent solution for me because of the dynamism required by the cql_filter (this would vary in length)
Thirdly, unfortunately I cannot use POST because I’m integrating it into Mapbox which seems to want a url (no post options as far as I can tell).
Thank you so much for all your responses so far, if there is any other suggestion I’d really appreciate it - for example a way to perhaps alter the webserver to handle longer urls?
Hi everyone! I have an issue that I’m struggling to resolve and I’m hoping someone may be able to assist or guide me.
I am trying to use the GetMap feature from the WMS service (which works). However it seems when I add a cql_filter to the url, I get an error message that the request is invalid. If I remove some other get fields within the url (layers in particular - which shortens the url), then I get a response.
It seems that when the url is over 200+ characters, I get the issue. My question is, can I somehow get geoserver to accept longer URLs? I cannot use POST because my implementation uses Mapbox which calls a url and not post variables.
Any help would be appreciated, thank you!
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
Beyond that you are reaching the limits of what URLs can do due to a limitation of the mapbox api.
Crazy ideas to try next
If you are just filtering content, make a parameterized sql view that takes the parameters you need to control, and hope you can stay under the limit (as parameters are smaller than cql expression)
Even a simple map preview URL generated by GeoServer goes beyond 200, I picked one at random for a single layer
it was 240 chars.
If you’re hitting the 2000 chars limit, either find a way to make URLs shorter, or better yet, switch to a base library that is not limited to GET, such as OpenLayers.
Another possible option would be to add a custom proxy in between, you give it “filters” and get back an identifier for each of them, then add just the id in the request,
and as the request goes through the proxy, it will expand the full filter (since the hard limit is normally found in the browser, using a server side trick like this one would dodge it).
Come to think of it, the GeoServer community module called “parameter extractor” does some of that, and has a REST API to create new mappings… but you’ll have to access it
with administrative credentials, which might be a significant limit for you. See: https://docs.geoserver.org/stable/en/user/community/params-extractor/index.html
Cheers
Andrea
···
== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.ithttp://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.