[Geomoose-users] TMS layers in GeoMoose 2.2

[Mark Volz]

Jim

Success!

It turns out that my grids were slightly off so that mapcache had to recreate each tile.  Now that the grids are set up the correctly I am seeing speeds of about 3-10 ms.

You mentioned that 800 ms seemed slow.  The imagery that I am using is about 23 GB worth of 6 inch Pictometry.  Made of four Jpeg compressed geotiffs with overviews.  And accessed through a tile index.  I know I keep hearing "uncompressed geotiffs is the fastest."  However, the size of uncompressed geoTiffs is unacceptable to me.  Anyways, If you have any other ideas on how I can speed up the speed of Mapserver producing the rasters for Mapcache to use let me know.

I am still somewhat concerned that mapcache was so slow when the grid was not exactly the same but that is more of a mapcache issue than a GeoMOOSE issue

Thanks You


For the curious:

Make sure the extent in the mapcache grid is exactly the same as the extent in the mapbook.






Mark Volz
GIS Specialist

From: Jim Klassen [mailto:klassen.js at gmail.com]
Sent: Thursday, June 07, 2012 11:43 AM
To: Mark Volz
Cc: geomoose-users at lists.osgeo.org
Subject: Re: [Geomoose-users] TMS layers in GeoMoose 2.2

Are you using tiled="true" or tiled="false" with WMS?  Try the other option.

Those timings don't make any sense.  Both MapCache demo and GeoMoose are using OpenLayers for the actual map.  Can you look at the image requests and see if there is anything odd about the GeoMoose calls?

My guess is the pink tiles in GeoMoose are related to timeouts on the server.  Did you request too many tiles at once.  This can easily happen if your cache isn't seeded or you zoomed while it was still generating tiles.  This effect can be amplified by the MapCache meta-tile size.

You should be able to do much better than 800ms with MapServer and GeoTIFFs, especially over a county sized area.

On Jun 7, 2012, at 11:16 AM, Mark Volz wrote:


Jim,

If I am not mistaken, I think TMS is in any projection (in my case county).  I think XYZ is in 3857.

Anyways, I just wanted to check out TMS as WMS in GeoMOOSE is extremely slow so I was hoping to use it mainly for debugging.  Please not the timings that I found.  This is for an area that already has a cache.

Mapcache WMS Source in GeoMOOSE - 7 seconds, many pink tiles, which is unacceptable
Mapcache TMS and WMS Source in Mapcache demo  - usually less than 10 ms
Mapserver using a GeoTiff to create an image for GeoMOOSE  - about 800ms which is okay, but 10 ms is so much faster!

I don't know why Mapcache is running so slow in GeoMOOSE.  It is taking roughly 1000 times longer to load in GeoMOOSE than in the Mapcache Demo.




Mark Volz
GIS Specialist

From: Jim Klassen [mailto:klassen.js at gmail.com]
Sent: Thursday, June 07, 2012 10:20 AM
To: Mark Volz
Cc: geomoose-users at lists.osgeo.org<mailto:geomoose-users at lists.osgeo.org>
Subject: Re: [Geomoose-users] TMS layers in GeoMoose 2.2

I haven't tried a TMS that isn't in the 3857 projection.  I wouldn't be surprised if this isn't easily supported before 2.6.  I know when I was trying out different TMS parameters in 2.4 that I needed to create a custom layer type to deal with it.  For more standard TMS layers, I used the "xyz" type in 2.4.

I would recommend you use WMS to access your MapCache tiles if you are using non-web-mercator projections in GeoMoose 2.2.  MapCache will still use any cached tiles to assemble the result.  GeoMoose 2.6 (along with the newer OpenLayers version) at least has the potential to make non-standard TMS configurations work from the mapbook.  (Although I suspect the code for the TMS map source will need to be extended... it will at least be possible to do this in a sane manner).

I haven't tried WMTS.  I suspect it misses the biggest reason of having tiles in the first place... the fact that they can be cached using standard HTTP caches and CDNs that aren't geo-spatially aware.  Tiles aren't so much for your server as they are for the network.  Also, make sure you have HTTP1.1 Keep-Alives active on your web servers.  Assuming that your data and map files are organized so that MapServer can operate efficiently, without Keep-Alives, the extra network overhead from the many requests for tiles will overwhelm any speedup from having everything cached.

Jim Klassen

On Jun 7, 2012, at 9:54 AM, Mark Volz wrote:



Hello,

I am trying to figure out how to set up a TMS layer for geoMOOSE.  If anyone knows what parameters are needed let me know.

Here is an example request from the mapcache TMS demo: http://10.0.8.116/mapcache/tms/1.0.0/MNSOUTH11@UTM15/0/0/1.jpg

Also, if WMTS or something else will work better for GeoMOOSE 2.2 / 2.6 let me know.


Thank You!

Mark Volz
GIS Specialist



_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.osgeo.org<mailto:Geomoose-users at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/geomoose-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120607/ceb10cd1/attachment.html>