Tag Info

Hot answers tagged

4

Turns out that ESRI just added this feature, but only for users of ArcGis server - the public server will have it turned off. The feature is called ExportTiles and it has been introduced in 10.2.1 for REST API: It'll export things into ArcGis's .Tpk or bundled image formats.


3

The expression "host the OpenLayers map on site" isn't much clear as using OpenLayers is more a client side topic: OpenLayers is a JavaScript library and works on the browser. Using OpenLayers doesn't depend in any way on the hosting machine. So I assume you would like to set up a geographic server. The things you should care about are: processing power ...


2

Luckily a standardized series of bounding boxes already exists, the TMS tile scheme. If your ok with making more requests for smaller amounts of data, splitting it into tiles can work very well, it caches well, and makes nice looking URLs. Once you have a tile coordinate(zoom/x/y) it can be converted to a bounding box, fetch the data, then depending on the ...


2

The best reference for this is this page on the OSM Wiki. It has Pseudo code as well as code in various languages for converting from the XYZ tilenames, to the bounding box. The Pseudocode for this is as follows n = 2 ^ zoom lon_deg = xtile / n * 360.0 - 180.0 lat_rad = arctan(sinh(π * (1 - 2 * ytile / n))) lat_deg = lat_rad * 180.0 / π Note that this ...


2

We work regularly with tiled layers in our applications and I usually store tiles directly on a dedicated disk which I host as a virtual directory. You can see the tile directory here: http://argeomatica2012.cloudapp.net/SOLIDARIDAD_ortho/ I then add the tiles directly as a XYZ layer to my OpenLayers map like so: layerXYZ = new OpenLayers.Layer.XYZ("XYZ ...


1

Jakub Kania was correct in his comment that the date/time have to be added to the url to make it different from the url of tiles in the cache. You have to subclass OpenLayers.Layer.XYZ for that: OpenLayers.Layer.CustomXYZ = OpenLayers.Class(OpenLayers.Layer.XYZ, { getURL: function () { var url = OpenLayers.Layer.XYZ.prototype.getURL.apply(this, ...


1

I think the problem is not in the "resolution" as size X x Y but in the "resolution" as DPI (dots per inch): you have (for example) 96 DPI (standard) on your screen and the clients have higher DPI on their screens. This resolution is controlled by DPI parameter of your service cache. ...


1

I would try to use the tilestache-seed.py script: https://github.com/TileStache/TileStache/blob/master/scripts/tilestache-seed.py You can get the bounds of your parcel (which units depend on the units of your data) and pass it into the script. use the '-x', '--ignore-cached' options to force the tiles to be regenerated. Since your data is coming from ...


1

No the caches are not deleted. Once you delete the service you can delete the caches. To locate the caches you can edit the "service" before deleting and the final tab (caching) at the top shows you the location shows you the cache location.


1

It appears my assumption was correct. This is what I did to fix the issue: Created a copy of the service Copied the cache from the original service to the new one Deleted the cache at the levels where tiles appeared to be missing (in my case, the last three levels) Recreated all tiles at the levels I deleted Copied the levels from the new service back to ...


1

As you can see here it is a known issue. There is bug submitted to GWC GitHub: https://github.com/GeoWebCache/geowebcache/issues/232


1

It looks like you've done a pretty good job of following best practices for creating the cache. Your servers have enough horsepower, but pulling the map data from your database might be an issue. Here's a little summary of this site that has a few additional tips for getting the most bang for your buck. 1 - Analyze your map before publishing it! This may ...


1

Monotonically increasing is a maths term that roughly means that "the next one is greater than this one". It doesn't have to be by the same amount each time. So in the context of GeoWebCache configuration, the code expects that the expiration rules increase in zoom level. You've pretty much got it in your second example: <expireCacheList> ...



Only top voted, non community-wiki answers of a minimum length are eligible