New answers tagged

0

{ "mapSettings":{ "roads":{ "type": "WMS", "projection": "EPSG:27700", "projectionDef": "+proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000 +y_0=-100000 +ellps=airy +datum=OSGB36 +units=m +no_defs +nadgrids=ostn02", "attribution": "(c) Crown Copyright", "units": "m", "maxExtent": [250000,150000,400000,180000], "url": "http://council.company.com/...


0

Mapshaper.org is a handy free online tool that allows you to upload a geojson file, display it as a map, then choose one of three simplification alogrithims which you can adjust the strength of with a slider. It updates the map and highlights in red any places where there's a loss of integrity like an overlap between two regions. There's a 'fix' button that ...


2

Column and row along with the zoom level are needed to identify a specific tile. This section in the osm wiki shows how they are calculated.


1

The .osm file is the raw data that you can download from the OSM server. It contains nodes with coordinates and attributes ("tags"), lines with the nodes they are built from, and relations containing nodes, lines or othe relations. You will need a software that transforms that file to something that can be displayed. One choice is the Mapnik or tilemill ...


0

The data volumes seem low but I'm wondering what the size of the actual image is that you're going to output? That may be the problem. Can you try with a lower resolution and see if that helps. You may need to tile the data prior to going into the rasterizer if you're looking to produce a huge huge output raster.


1

Instead of creating a tile layer inside your getTile callback, you'll have to create an ol.layer.Tile with an ol.source.XYZ and a custom tileUrlFunction and tileLoadFunction: new ol.layer.Tile({ source: new ol.source.XYZ({ tileUrlFunction: function(tileCoord) { // create a simplified url for use in the tileLoadFunction return tileCoord....


1

This is very old question, but there are (at least) two important caveats, depending on the task at hand. The task may result in rendering a (very) large number of empty tiles without specific management of the tile creation process. The size on disk of a tile pyramid may be much (more than 100%) larger than expected from the sum of its component file ...


0

Use restrict extent as below example, so User will not go beyond the defined extent. Reference: http://dev.openlayers.org/docs/files/OpenLayers/Map-js.html#OpenLayers.Map.restrictedExtent Example: http://dev.openlayers.org/examples/restricted-extent.html


0

There really was no easy way for me to complete this other than what I suggested in the first place which was to "render the DEMs as all values of 1 and mask out the NoData values and then convert to polygon". Technically I converted the NoData to 0 and all valid pixels to 1 with this Con Statement ... Con(IsNull("myDEM"), 0, 1) and did away with the "0" ...


0

I did further research, and the following three "vendorOption" parameters were recommended where labels are left off when you really want them labeled in the tiles. I'll explain each briefly and why it did or did not help in my case. <VendorOption name="spaceAround">-1</VendorOption> <VendorOption name="conflictResolution"&...


0

If you use latest MapTiler version from http://www.maptiler.com/ to generate the tiles, it will directly produce for you an ready to use openlayers.html viewer. You clearly use a very old version of MapTiler - as the viewer you show here is based on the old OpenLayers (v2) and the XML file is not anymore generated by recent MapTiler versions. Instead, there ...



Top 50 recent answers are included