<div>Thank you for the explanations. Three supplements:</div>
<div> </div>
<div>1. Being able to add user defined styles to KML would be cool, e.g. through the means suggested in the RFC 18 but also through Virtual Format (VRT)?</div>
<div> </div>
<div>2. I stumbled over the STYLEITEM "AUTO" in the UMN MapServer docu:</div>
<div><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mapserver.gis.umn.edu/docs/howto/ogr_howto/#styleitem-auto-rendering-layers-using-style-information-from-the-ogr-file" target="_blank">http://mapserver.gis.umn.edu/docs/howto/ogr_howto/#styleitem-auto-rendering-layers-using-style-information-from-the-ogr-file
</a><br>This enables that color and style is coming from individual shape objects (currently MapInfo TAB and DGN only) as opposite to the usual case where style is defined at the layer level. Idea: I think that if OGR can pass-through styles on an object basis it's technically not too difficult to set styles at the layer level (as suggested before).
<br> </div>
<div>3. Are there any current applications of OGR styles (for an end user) besides for MapServer as described above and through the (programmer's) C API?<br> </div>
<div>-- Stefan</div>
<div> </div>
<div><span class="gmail_quote">2007/12/28, Daniel Morissette <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:dmorissette@mapgears.com" target="_blank">dmorissette@mapgears.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Stefan Keller wrote:<br>><br>> 1. Is there also a concept and a way to change style output in an<br>
> ogr2ogr call, e.g. for KML?<br>><br><br>I don't think ogr2ogr supports "changing" the style assigned to a given<br>feature or assigning new styles to features, but when translating<br>between formats that support styles (
e.g. TAB, MIF and DGN) then the<br>styles are maintained as much as possible.<br><br>With respect to KML, last time I checked I don't think the KML driver<br>supported styles, so the answer is no, at the moment it is not possible
<br>to control the style of the features written to KML output (but<br>technically that's feasible and could be implemented someday).<br><br>> 2. Regarding the style concept perhaps it would be helpful to mention<br>
> similarities to SLD and eventually also to Mapfile symbols (if there are<br>> any)?<br>><br><br>The concept of assigning rendering rules to geometries is shared in both<br>cases but that's about it. The terminology (pen/brush/etc vs
<br>symbolizers) and encoding (compact text strings vs verbose XML) are<br>completely different.<br><br>SLD also supports building up classifications using filter encoding<br>which is not part of the OGR style concept.<br>
<br>Why did OGR invent its own encoding instead of reusing SLD? Mostly<br>because the OGR style encoding predates the days when SLD became well<br>known (to me anyway) and widely used. But even if we were to do this<br>again today I'm not sure if we would opt for a verbose XML encoding...
<br>we'd probably spend a lot of time debating the performance issues vs the<br>benefits of interoperability with SLD.<br><br>BTW, this question would really belong on the gdal-dev list, so I have<br>cross-posted my reply to gdal-dev (and ask that further replies be sent
<br>only to gdal-dev).<br><br>Daniel<br>--<br>Daniel Morissette<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>_______________________________________________
<br>FWTools mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:FWTools@lists.maptools.org" target="_blank">FWTools@lists.maptools.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.maptools.org/mailman/listinfo/fwtools" target="_blank">
http://lists.maptools.org/mailman/listinfo/fwtools</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://fwtools.maptools.org/" target="_blank">http://fwtools.maptools.org/</a> <br></blockquote></div>
<br>