Tag Info

New answers tagged

1

For those who may be interested: the problem seems to have been that my .vrt had coordinates that spanned across the -180 longitude. Left was a pixel or two beyond the line (-180.00004) and right was ~0 degrees). Clipping it seems to have solved the problem.


0

In case anyone is interested, the problem above was a simple error on my part - the srs for the Layer was incorrect.


1

You can easily fill areas with textures and patterns by bringing in external images. You might create the patterns yourself in image editing software such as GIMP or Inkscape, or find ready-made images from resource websites such as Subtle Patterns or Free Seamless Textures. Taken from the TileMill Documentation where you can find an easy ...


1

Line 9 on your osm-bright.osm2pgsql.mml file, you left out a comma when adding the line "type": "shape", You need to have proper JSON format.


0

Problem is CORS which is not allowing the tiles to load from 192.168.1.127 I configured the proxy and now its working fine.


0

Expecting , delimiter Do you have spaces where you should be using a comma on the command line call?


1

The style is invoked in renderd.conf with something like XML=/home/jburgess/osm/svn.openstreetmap.org/applications/rendering/mapnik/osm-local.xml So you can exchange that call to another xml file, or use two configuration files for renderd. If it is pure mapnik, duplicate generate_tiles.py, and change mapfile = "osm.xml" to another style file. In both ...


0

So completely changed my workflow and I have compact couchdb databases in a matter of seconds/minutes from mbtiles. Reduced Tilemill -> Couchdb rendering by days. New workflow: Tilemill -> mbtiles -> cdbtiles -> couchdb Using more of the great open-source software by MapBox et al (https://github.com/mapbox and mapbox.com) Couple of gotchs to installing ...


0

As I mentioned in my comment: Changing the srs of the tag to +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 +no_defs +over has done the trick


0

I had the same kind of errors, that came from the fallback "build-from-source" because npm couldn't find pre-compiled packaged. Turns out I had Node 64 bits installed. I just switched to Node 32 bits, cleared my node_modules folder and everything built well (with a few errors on an optional dep but nothing blocking).


1

The values for x and y in this case are probably just indices for an X-Y-Z tilemap. The indices of a TMS service are unitless, they simply count the number of tiles from the top-left corner. In your example, the _unitsPerPixel function returns the scale of the pixels for the given zoom level. The value is the width and height of one pixel in the units of ...


0

Just query the table: SELECT name FROM planet_osm_polygon WHERE admin_level='4' AND ST_Contains(way, ST_GeomFromText('POINT(-11817883.86 4424094.21)',900913));



Top 50 recent answers are included