[mapguide-users] RE: MapGuide Automated Tiling Engine

[Kori Maleski]

Hi Jason,

 

The Tiling Engine is using the available API functionality of MGO 1.1.0 and
MGE SP1.

 

Once 1.2 is released, it will be updated to reflect the tile improvements.

 

I was staying away from customization until then.

 

 

Cheers and thanks,

 

 

  _____  


 <http://www.websoftdev.com/> 

 <http://www.websoftdev.com/> 

 <http://www.websoftdev.com/> 

Kori Maleski

Senior Application Developer

WEBSOFT DEVELOPERS, INC.

P: (530) 759-8754 ext 114

F: (530) 759-0923

kori.maleski at websoftdev.com

  _____  

 

  _____  

From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Monday, May 07, 2007 12:09 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] RE: MapGuide Automated Tiling Engine

 

Hi Kori,

 

Currently, the tile service code only renders a tile if it does not exist,
otherwise it just streams back the existing tile.  Look around line 172+ in
ServerTileService.cpp:

 

<
<http://trac.osgeo.org/mapguide/browser/branches/1.2.x/MgDev/Server/src/Serv
ices/Tile/ServerTileService.cpp>
http://trac.osgeo.org/mapguide/browser/branches/1.2.x/MgDev/Server/src/Servi
ces/Tile/ServerTileService.cpp>

 

I guess it would be convenient for tile generators to have a Create()
function that only returns a result code... no point in shipping image
bytestreams around for this.  You'd likely want to have a filter argument to
this function where you could restrict creation to things like "if not
exists" or "if older than".

 

You could hack a file existence check before trying to generate the tile,
but please be aware that the directory structure for cached tiles has
changed considerably in MapGuide OS 1.2, and the ability to specify tile
size on a per-server basis has been added, so any calculations made based on
a fixed tile size or tile group size may be invalid.  Because of this,
you'll have to account for the server version number in any such test.
Personally, I wouldn't risk this, as the tile structure is an undocumented
feature, and is liable to change.  Stick with the APIs to reduce your risk
and maintenance overhead.

 

More information on these settings and changes can be see in the
serverconfig.ini file in SVN (look for [TileServiceProperties]) :

 

<
<http://trac.osgeo.org/mapguide/browser/branches/1.2.x/MgDev/Server/src/Core
/serverconfig.ini>
http://trac.osgeo.org/mapguide/browser/branches/1.2.x/MgDev/Server/src/Core/
serverconfig.ini>

 

in this email thread:

 

<
<http://lists.osgeo.org/pipermail/mapguide-internals/2007-January/000509.htm
l>
http://lists.osgeo.org/pipermail/mapguide-internals/2007-January/000509.html
>

 

and in this RFC:

 

< <http://trac.osgeo.org/mapguide/wiki/MapGuideRfc13>
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc13>

 

Additionally, there should be considerable speed improvements for tile
generation with MapGuide OS 1.2:

 

<http://trac.osgeo.org/mapguide/wiki/MapGuideRfc11>

 

Jason

 

  _____  

From: Kori Maleski
Subject: RE: [mapguide-users] RE: MapGuide Automated Tiling Engine

The MapGuide TileService function that retrieves tiles is the same one that
does a check to see if it exists, so there isn't a handy way to skip the
process.

I may be able to speed the requests if they do already exist.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 15120 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapguide-users/attachments/20070507/ba709eb8/winmail-0001.bin