On 28/03/2010, at 7:58 AM, Frank Gasdorf wrote: OK, but I'm a bit confused about the place of the implementation. Could you explain the main reason not to implement it as an extension in geotools? Is it because of the pending status as a standard (TMS/WMSC)? Should the udig one be a reference client implementation?
Nothing so complicated.
I have not had time to port the code to geotools. 1) Porting is in two phases; porting the WMSC parsing code and code to fetch tiles. 2) Porting the tile fetching code that is currently done with eclipse Jobs (it would need to be translated to the java.util.concurrency Future api). There are two plugable strategy classes one caches in memory; the other caches on disk.
You can actually see the original code was done in geotools but was dropped due to lack lack of community feedback.
(The above fetches nasa world wind tiles) The classes I looked at are very similar to the geotools wms extension. And many classes are implemented twice (geotools WMSComplexType / udig WMSCComplexType and their internal classes (like _ServiceType)). Is it planed to move this stuff to the geotools library, so geoserver and other projects can benefit from it?
I would love to see it migrated; at the moment all my volunteer time is going into uDig 1.2.0 release. What I would *love* to see happen is the code submitted as a patch to the geotools "wms" module - and have the "wms" module take on all manner of tile server specifications. If you would like to join me as module maintainer of wms and prepare the patch I would assist in the migration (transitioning uDig to depend on the classes as they are moved to geotools).
Simone has also expressed interest in the section item 2) above so I am CCing him on this conversation. Jody
Thanks, Frank
2010/3/27 Jody Garnett <jody.garnett@xxxxxxxxx>
Hrm you are correct GeoWebCache stopped working for me from the opengeo site; I have just continued testing with tilecache.
Jody On 27/03/2010, at 12:54 AM, Frank Gasdorf wrote: Hello, Sorry for cross-posting!
I wondered about the results using local geoserver with activated and configured geowebcache and udig 1.2 RC1 wmsc wizzard. I try to describe, perhaps somebody could confirm:
- Add Web map Tile Cache Layer (WMSC)
- add url http://localhost:8080/geoserver/wms?tiled=true- The final request was http://localhost:8080/geoserver/wms?TILED=true&REQUEST=GetCapabilities&SERVICE=WMS
So all the parameter keys are changed to upper cases because of
org.geotools.data.ows.AbstractRequest class (setProperty() uses
toUpperCase()). The Geowebcache WMSGetCapabilities class calls
the getParameter of HttpServletRequest :
HttpServletRequest .getParameter("tiled");
I debugged a bit and the responding capabilities document has no VendorSpecificCapabilities section.
It looks like a bug in geowebcache because it ignores the uppercase TILED Parameter, doesn't it? Tilecache.org seems not handle tiled or TILED at all and always returns a capabilities document with a VendorSpecificCapabilitiessection.
Is the "tiled" request parameter a specific implementation of geowebcache or is it a required parameter described in the TMS specification (where can I find it)? In regards, Frank
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
| 