Tag Info

New answers tagged

0

OSM relations are stored in the Postgis database with negative id to distinguish them from ways that could have the same id. So you have to put that negative osm_id value into your style definition. Apart from that, you could as well look into the polygon table. Relations of type boundary or multipolygon that form a closed line should land there (unless the ...


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 ...


0

Osmosis stores the OSM data in the same way as the editor uses it: nodes, ways and relations. One of the time consuming tasks of osm2pgsql is to convert closed ways and multipolygon relations to multipolygons that can be used for rendering, as well as defining a rendering order of features that overlap like bridges over ways or other buildings. This is not ...


1

The GADM database of Global Administrative Areas has downloadable shapefile up to level four for Viet Nam http://www.gadm.org/


0

I had the same problem and was able to solve it using the nodata parameter in TileMill. When adding the geotiff as a layer, in the Advanced box I entered nodata="255" to make a white background transparent. The only CartoCSS I used was this: #geotifflayer { raster-opacity:1; raster-scaling: bilinear; } The mapnik documentation on the nodata parameter ...


3

I ran into the same problem and I ended up using adopted way_area size clauses. By default they seemed to be too small for me. So when zooming out it would fetch so many very small polygons that that was too much data to transfer. So basically you don't display too small polygons when being zoomed out. You have to try and error until you have the best ...


0

Use shield for examples like this. Here is the CartoCSS reference. Here is an example to start with.


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

What you are looking for is MapBox' maker example page. I believe you have to add additional CSS markup for each zoom level. In their example, they show how to change the size of the marker-width at each zoom level. What is happening is that you don't have enough room to display the label text in the marker size. text-allow-overlap:false; fixes the ...


0

Just guessing, but you may be missing some dependencies. According to the instructions at https://www.mapbox.com/tilemill/docs/source/ you could try a sudo apt-get install of the following: postgresql-9.1 postgresql-server-dev-9.1 postgresql-contrib-9.1 postgresql-9.1-postgis


0

If I understand your problem correctly, there may be another workaround to this as well by using the comp-op operations (which can be quite confusing). Let's say you had your #raster layer and a #shp poly layer. The shp layer is polys defining areas that you WANT to see from the raster. Anything outside the shp polys will be masked with the following ...


1

That should be easy to do in QGIS. Load the postal Shapefile and join the sales rep data, then style based on sales rep. You can use the OpenLayers plugin to load background tiles (note though that these won't print).


1

I encountered the same issue and found another solution: global-pattern.


0

I used a version of osm2pgsql that can handle 64-bit IDs. I think it happens when I merged some pbf data files with osm2pgsql into one database or "style" the data with the style attribute that osm2pgsql offers. I rebuild the Database using osmconvert to put thinks together and osm2pgsql to import that merged file into the postGIS Databse (without style=). ...



Top 50 recent answers are included