<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tiles are not related to the raster workshop as such.<br>
<br>
When you request a map in MGOS, it renders all features on the server
and sends the resulting image<br>
to the client. This can take a long time, especially if the data is
complex.<br>
<br>
One solution would be to pregenerate all possible sizes and displays of
the map, but that would result<br>
in a HUGE number of images. This would also be annoying if you wanted
to turn a layer on or off.<br>
<br>
Instead, MapGuide can serve tiles in a grid, so that a user with a
600x600 display gets two tile rows<br>
and two tile cols (a 300x300 tile). A user with a 900x900 display can
then use the same tiles plus some more.<br>
<br>
These tiles can then be saved, so that no processing power is required
for subsequent rendering.<br>
To make sure that it is possile to turn layers on/off MapGuide makes
tiles from special groups,<br>
known as "base layers". You can then have ordinary layers and groups
displayed on top of the base layer tiles.<br>
<br>
This also makes it possible to have dynamic data displayed up-to-date,
while stale<br>
background data takes up very few resources.<br>
<pre class="moz-signature" cols="72">Regards, Kenneth Skovhede, GEOGRAF A/S
</pre>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:nelyass.heglig@gnpoc.com">nelyass.heglig@gnpoc.com</a> skrev:
<blockquote
cite="mid:73ADA55D1F0491438223865EFF4E44C9C52781@hgl-mail-svr1.heglig.corp.gnpoc.com"
type="cite">
<pre wrap="">Many thanks for your reply
As I know from mapguide 6.5 tile maps means that the map image is
divided into tiles (a network gird like).
Which means when you zoom to an area the server sends you only the
viewed tiles in that area the same concept as in google earch.
As I remember the was utitlity in mapguide 6.5 called raster workshop
can divide raster format data into tiles.
My question is the same concept applied in mapguide open source or not?
And does the server divide the map image into a grid of tiles or not?
Thanks
Nadir Elyass
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mapguide-users-bounces@lists.osgeo.org">mapguide-users-bounces@lists.osgeo.org</a>
[<a class="moz-txt-link-freetext" href="mailto:mapguide-users-bounces@lists.osgeo.org">mailto:mapguide-users-bounces@lists.osgeo.org</a>] On Behalf Of Zac Spitzer
Sent: Friday, December 19, 2008 3:11 PM
To: MapGuide Users Mail List
Subject: Re: [mapguide-users] What is Tile Map?
On Fri, Dec 19, 2008 at 10:57 PM, <a class="moz-txt-link-rfc2396E" href="mailto:nelyass.heglig@gnpoc.com"><nelyass.heglig@gnpoc.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Sirs,
Would you tell what are the deferences between Tile map and ordinary
</pre>
</blockquote>
<pre wrap=""><!---->map
tiled maps are cached (unless otherwise configured)
</pre>
<blockquote type="cite">
<pre wrap="">
Which one has a greater performance?
</pre>
</blockquote>
<pre wrap=""><!---->
tiled because of cachng
</pre>
<blockquote type="cite">
<pre wrap="">
What happen behind the seen with the data from the server and client
</pre>
</blockquote>
<pre wrap=""><!---->sides?
</pre>
<pre wrap=""><!---->
I don't know what your asking here???
</pre>
<blockquote type="cite">
<pre wrap="">
Do all data format (sdf, shp, raster etc.) can be used in tile maps?
</pre>
</blockquote>
<pre wrap=""><!---->
there is no difference here between tiled and dynamic maps
</pre>
<blockquote type="cite">
<pre wrap="">
Thanks in advance
Nadir Elyass
_______________________________________________
mapguide-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapguide-users@lists.osgeo.org">mapguide-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapguide-users">http://lists.osgeo.org/mailman/listinfo/mapguide-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>