[OSGeo-Standards] WMS-C and handling of tiled=true? Indicating a
Restriction or an Ability
jgarnett at refractions.net
Wed Aug 27 16:09:38 EDT 2008
Now that I am at work I realized I answered your comment incorrectly.
The TileServer your describe is good; I will just need a way to tell (as
a client) that such a server is not a general purpose WMS (and thus uDig
will be forced to only make GetMap requests in accordance with the
Perhaps this is the intentions of the "tiled=true"
VendorSpecificParameter for GetMap?
- My impression was that tilted=true was intended to let a full fledged
WMS implementation switch GetMap between dispatching to the normal
rendering path vs dispatching to tile lookup?
- If tiled=true is indeed a flag indicating that *only* tile lookup is
supported the my workflow will need to be modified. Something like
checking the GetMap preamble documented by the VendorSpecificParameters;
and iff "tiled=true" was present, I could assume that a generic GetMap
was not supported ...
Hopefully this is the correct venue for these discussions.
Satoru Takagi wrote:
> Hi all,
> There seems to be the considerable difference between the function
> that is necessary for a tiling server and the function of the WMS server.
> The simplest tiling server can be achieved even by the simple file
> system (For example, mere httpd without CGI, servlet, PHP..) which
> stored tile files and metadata.
> Therefore, I think that the spacifications for tiling server should be
> designed based on simpler mechanism (the basic URL based web) rather
> expansion of the functions and its specifications of a dynamic server
> such as WMS.
> Satoru Takagi
More information about the Standards