I am using Geoserver 1.5.0v and working on a mobile GIS (java midlet)
project.
My problem is when the geoserver responds to the getCapabilities command
with a 146KB file, where if i cut away all the supported EPSG projections,
the file shrinks down to 36KB. Since i am working on a mobile project, 146KB
is a big file and takes for a GPRS mobile about 30seconds.
I was wondering, if there is any way, the geoserver could be configured to
send back only the relevant EPSG and not every supported EPSG.
Following is a part of the wms getCapabilities response
I am using Geoserver 1.5.0v and working on a mobile GIS (java midlet)
project. My problem is when the geoserver responds to the getCapabilities command
with a 146KB file, where if i cut away all the supported EPSG projections,
the file shrinks down to 36KB. Since i am working on a mobile project, 146KB
is a big file and takes for a GPRS mobile about 30seconds.
Hopefully some day we'll throw away the current config subsystem
and we'll add a filter to limit the supported SRS (in which order
that will happen, I don't know)
Cheers
Andrea
Thanks for such a prompt reply. I followed the link and I understood that
there is not much we can do to avoid it.
1. Either to edit it manually and save it on the server and send it when
asked for getCapabilities (WMS)
2. Modify those libraries as mentioned by chris, but than you wrote that the
server looses some functionalities.
The other way i was thinking was to have a servlet in between the SERVER and
the CLIENT. So the getCapabilities response is pruned and personalised
before sending it to the client.
Thanks for such a prompt reply. I followed the link and I understood that
there is not much we can do to avoid it. 1. Either to edit it manually and save it on the server and send it when
asked for getCapabilities (WMS)
2. Modify those libraries as mentioned by chris, but than you wrote that the
server looses some functionalities.
Well, if you're not playing with polar areas (stereographic polar) and
you take care of declaring the TOWGS84 in all your wkt you should
have no problems... well, this is only I guess, I haven't made
any real test.
can you assume when it will be possible to limit the offered SRS of
Geoserver via Admin interface (which version)? We made a quick workaround by
storing a local copy of the Capability-XML-file on the server and removing
most of the SRS-codes in this file. Now loading the local geoserver WMS in a
map client is quickly done. I know it is a quick-and dirty solution, but it
helps !
We use Geo. 1.5.3: is it possible to edit the epsg.sql in the
gt2-epsg-hsql-2.3.4.jar-file and create a new gt2-epsg-hsql-database out of
it and use this one ? This would be another quick possibility.
Hope this problem can be solved soon.
Best regards, Cornelius
aaime wrote:
Choe ha scritto:
Hi Andrea,
Thanks for such a prompt reply. I followed the link and I understood that
there is not much we can do to avoid it.
1. Either to edit it manually and save it on the server and send it when
asked for getCapabilities (WMS)
2. Modify those libraries as mentioned by chris, but than you wrote that
the
server looses some functionalities.
Well, if you're not playing with polar areas (stereographic polar) and
you take care of declaring the TOWGS84 in all your wkt you should
have no problems... well, this is only I guess, I haven't made
any real test.
Cheers
Andrea
-------------------------------------------------------------------------
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/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
