Re: [OSM-dev] Not filling polygon holes
On Tue, Jun 17, 2008 at 11:29 PM, Martijn van Oosterhout http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev>> wrote: > On Tue, Jun 17, 2008 at 5:56 PM, Brian Peschel <http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev>> wrote: > >/ (not sure if this should be here or on the mapnik list, so I put it on /> >/ both. Apologies for overposting) /> >/ />/ > I have seen a couple of discussions on the Open Street Map lists about />/ > multi-polygons. And I believe I saw a comment of two about not filling />/ > polygons with holes. /> > Mapnik supports polygons with holes just fine. Occasionally there are > problems with the OSM data getting converted into the right format, > but if you have properly constructed shapefiles it shouldn't be a > problem. > > Have a nice day, I have access to the mapnik source code. I see the code where it supports multiple polygon in a single shapefile record (by looking at the number of parts). But it appears to be then returning each part as a polygon in the larger mapnik::polygon_impl. Unless you are saying that the mapnik library understands the shapefile direction part and is not filling counter clockwise shapes (as defined by the shapefile definition)? Hmmm... This probably makes more sense on the mapnik mail list, I will post this over there. - Brian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
[OSM-dev] Not filling polygon holes
(not sure if this should be here or on the mapnik list, so I put it on both. Apologies for overposting) I have seen a couple of discussions on the Open Street Map lists about multi-polygons. And I believe I saw a comment of two about not filling polygons with holes. I have some shapefiles with polygons. Many of these polygons have holes. I would like to draw images that do not fill the 'hole' areas of the polygons (so you can see coverage). Is that possible? - Brian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
[OSM-dev] Tiger CFCC code conversion
I previous post pointed me to the page on the wiki: http://wiki.openstreetmap.org/index.php/TIGER_to_OSM_Attribute_Map which has most of the Tiger CFCC code conversions. But it is missing the Classification D, E, F, and H. Is there info for these classifications? Specifically, I am interested in D and H. Looking at the OSM style sheet, it looks like D is broken into 5 different styles (using multiple attributes): leisure, amenity, places, stations, and maybe power_towers. It appears H would be in 2 styles (again, multiple attributes). Any places I can look? - Brian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
[OSM-dev] Question about ShieldSymbolizer in template file
I was looking at the template file osm-template.xml. In there I see a definition for a ShieldSymbolizer.
[OSM-dev] Rendering Rules
First, let me say I think the maps that Open Street Map are producing look great! So, here is my question(s). Based on what I can gather from the wiki, it looks like the US data all started from TIGER data and has been updated from there. And, again based on the wiki, all the rendering styles appear to come from the tags that are used (highway=trunk, railway=rail, etc) based on this page: http://wiki.openstreetmap.org/index.php/Map_Features So, how did the conversion from the TIGER CFCC codes to your tags occur? Is there a master list that has the conversion from one set to another? I have been playing with the Mapnik source code for rendering some maps. I have data in a custom format, so I had to write my own driver. Is there some place I can see the style definitions that are being used on Open Street Map? For example, as you zoom in, a road may appears black. Then as you zoom in, it changes to white with a black background. (Python calls them Style and Rule and c++ calls them feature_type_style and rule_type). Thanks! Brian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
