Here is excel sheet in Google Docs from GeoSolutions team (http://geo-solutions.blogspot.com/2010/12/estimating-time-and-space-required-to.html)
By the looks of it you render the QGIS WMTS in a different projection than the original WMTS. This can be seen by the angle of intersection of the highways. In QGIS this seem to be a perfect 90 degree angle, in the browser it is not. The reprojecting is done locally in QGIS, not at the server side. Therefore the original image gets distorted resulting in the ...
The zoomscales in QGIS probably differ from the configured grid set in GeoServer. This causes resampling of the images in QGIS resulting in less sharp images and less performance.
See GeoServer documentation.
You can change the zoomscales in QGIS via:
Different sets I use are: (Copy paste to XML, then ...
In other implementations (as in, our implementation) this is done with palette modification; you can quickly recolor a PNG image without touching the actual data, if you know the full original palette.
Google doesn't do that; they likely have a tile-based database and tiles of vector data that are rasterized on the fly.
I'd recommend using TileMill to generate the tiles, it can save them out to a variety of formats including as mbtiles bundles which can be used for offline applications. Tilemill will give you cartographic control over the maps, and produces beautiful results.
Alternatively, you could download the styled data from Cloudmade, the .img files should be full ...
I think there are two things that should help you accomplish this:
documentation for creating custom layers
sample showing how to
put tiles in local storage
Side note: you linked to the 1.6 docs. While valid for 1.6, the current version of the API is 2.5 and we recommend you use that as 1.6 is no longer being updated.
Edit: Here's a working example of a ...
Another way would be to use Maperitive's generate-tiles command.
Note: "couple of GBs" could be an optimistic estimate. Also note that Web tile servers usually don't pre-render all high-zoom tiles (like those for level 17) because a very small number (less than 1%) of them is actually ever used (requested) by browsers. So you'd probably need a way to ...
i think you can achieve this with some css bindings which is not a gis solution. in css there are lots of css media types and one of these is print element. you can add this to your index page with this way:
<link rel="stylesheet" type="text/css" media="print" href="print.css">
and with some css code may help you.
There was a mention of a TileCache patch for this on the OSGeo mailing lists:
Unfortunately the links to the patches no longer work. Apparently the patch involved a few changes to the code base, and would allow different caches to be used based on any URL argument.
I have an old script (in ...
I made a cheat-sheet that lists the total number of tiles for given zoom-levels.
It has two tables. One showing the number of zoom-levels needed to show things at a certain scale, starting from a tile showing people.
level 1: 1 # Person
level 2: 5 # Car
level 3: 21 # House building
level 4: 85 # Square
level 5: 341 # Small neighbourhood
level 6: 1,365 # ...
Luckily you do not need to trust in what you read from the web but you can make a test with your own data. It is not as simple as "PNG tiles are much larger than JPEG, but have better quality". That is mostly true with aerial and satellite images which can be compressed effectively with lossy jpeg method. PNG is lossless and quality is thus perfect but the ...
Did you try what the error message suggested and set the extent_type to loose?
I've also had to update one of the Python files in TileCache to avoid the "...
I needed my TileCache configuration to look like this:
I also needed to use a TMS layer type in OpenLayers. Everything is better now!
answer to my comment(this code is for my tms scheme and you can adapt it to your need):
var originShift = 2 * Math.PI * 6378137 / 2.0;
var initialResolution = 2 * Math.PI * 6378137 / 256; //tilesize
var lon = 10;
var lat = 20;
var mx = lon * originShift / 180.0;
var my = Math.log(Math.tan((90 + lat) * Math.PI / 360.0)) / (Math.PI / 180.0);
my = my * ...
Unless you have access to some kind of geospatial server such as GeoServer, MapServer, or access to any ESRI Server products, rendering the GeoTiffs will be a problem.
What I have done in the past when lacking a geospatial server was convert what I can via QGIS to a geojson file. QGIS can handle several formats of data which can be exported in several ...
It sounds like you first tried a source install of Mapnik. At this time input plugins were properly installed into the default directory at /usr/local/lib/mapnik/input. But the postgis plugin was not built because you did not have the pg_config program available and/or the postgres-devel package. If you followed http://github.com/mapnik/mapnik/wiki/...
you might want to have a look at https://github.com/mapbox/tilelive-decorator
This allows you to update properties of vector tile features dynamically from Redis, but I am sure you can implement it with an other data source. This should fit quite well with your use case.
Underneath it uses https://www.npmjs.com/package/tile-decorator to do the actual work ...
(B2) When you will try to request getCapabilities for the WMTS layer and layer name has same name in geowebcache.xml you will get the response which contains capabilities of two layers with the same name but different . If you are getting layers on client via OpenScales you'll notice that HashMap of my:Layer will be broken.
Different names in geowebcache....
Ran into the same issue (e), using namespace:layername for WMTS layer parameter solved this issue for me.
I noticed following behaviour:
Requesting a WMTS Tile without namespace for the WMTS layer parameter
always forces a reseed of tiles (e.g.
As per the documentation, switching from WMS to GeoWebCache only requires a URL change from:
/geoserver/wms <- direct WMS
/geoserver/gwc/service/wms <- geocached wms
and you're good to go, no need to switch WMTS. BTW, GeoWebCache requires all tiles be 256x256.
You can also seed the cache from the GeoCache home that can be reached from the Geoserver ...
See the details for the sample Esri service at that URL, which contains the line:
Single Fused Map Cache: true
Verify that your own service also contains this line - chances are that it doesn't. In that case you need to build a cache using the instructions at Creating map cache tiles.
You'll then be able to display your data as a tiled layer.
MapProxy is certainly a good option. If it is just a script you require, TileCache is another option. It's not as configurable as MapProxy, but it is a nice, light-weight solution. If you are already serving your WMS using GeoServer, then I'd recommend GeoWebCache.
I suggest to use EPSG:3857 as CRS for the raster during the tiling process.
EPSG:900913 is not included in current GDAL and QGIS anymore, thus the special spherical mercator treatment is not applied. The proj definition for EPSG:3857 is
+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +wktext +no_defs
I know this isn't quite what you are looking for, but I thought you might find it useful anyway. Have you seen this example by Odoe which uses css filters on the maps? Might be limited outside of chrome
If I understood correct your problem is that it is impossible to determine the combination of layers with each request as users can select any of the 140 layers and the client is sending one request for all layers combined (ie not a request for each layer).
In that case you could try fronting your WMS servers with a caching service like MapProxy or Mapcache ...
If you are using QGIS, you could utilise the OpenLayers plugin. Progams such as Mapertive can download tiles from OpenStreetMap, using the generate-tiles method. Other programs may be available for other sources. Mapertive exports the images into the 'Tiles' subfolder.
Once you have the tiles downloaded, make a copy of one of the files in the qgis\python\...
When publishing your map service in the Service Editor, Go to the Caching -> Advanced Settings. Down the page, where you see Area of interest to cache, you can set it to either Full extent of the map (maybe entire world), Current Extent of the map, or you can import the Area of Interest from a Feature Class. If you select the last one, ArcGIS prompts you for ...
It sounds like what you are really wanting is to be able to override specific tiles in a map.