It would be also cool to be able to directly use a string as image content for a marker (rather than just for the filename). That should be quite easy to do.
On 24/06/2016 14:28, Nathan Woodrow wrote: > Raymond, > > Code generated SVGs is a pretty cool idea. Would be super keen to see > that once you have something! > > On Fri, Jun 24, 2016 at 10:25 PM, Neumann, Andreas <a.neum...@carto.net > <mailto:a.neum...@carto.net>> wrote: > > Pretty cool - so we can deliver script-generated SVG code instead of > a filename? Nice! > > Care to do a blog post with some example? This sounds quite exciting > to me. > > Andreas > > On 2016-06-24 14:12, Raymond Nijssen wrote: > >> Hi Hugo, >> >> It works! Thanks a lot!! >> >> This is exactly what i was looking for, but somehow could not find. >> >> Here is a little example with some fake svg's: >> >> http://terglobo.nl/downloads/example.png >> >> Now I will script generating svg based on real data. >> >> Regards, >> Raymond >> >> >> On 23-06-16 09:02, Hugo Mercier wrote: >>> On 22/06/2016 19:06, Richard Duivenvoorde wrote: >>>> On 22-06-16 14:39, Hugo Mercier wrote: >>>>> Hi Raymond, >>>>>> - Add a text field to my feature layer containig svg, and >>>>>> somehow make >>>>>> qgis display that on my map; >>>>> >>>>> This should work, no ? >>>> >>>> Are you sure? This would mean that the value(!) of an attribute >>>> would >>>> contain the actual svg (code, not filename). >>>> Any example on how to use that with styling then? >>> >>> Hmmm exact, I don't think you can include the content (I tried to >>> include a data url but it does not work). >>> >>>> >>>>>> - Add a text field to my feature layer containig a path to a >>>>>> png (or >>>>>> svg), and somehow make qgis display that on my map. >>>>> >>>>> An SVG marker with the file name defined as an expression ? >>>> >>>> Same here, while we managed to get for example colors dynamic, >>>> we could >>>> not find a way (yet) to set the marker-svg once filename is >>>> retrieved >>>> from an attribute... >>>> >>>> Happy to get an example or pointers :-) >>> >>> with an SVG-marker the filename can be "data-defined", so you can for >>> instance use an expression like '/xxx/mymarker_' || id || '.svg' >>> >>> >>> _______________________________________________ >>> Qgis-developer mailing list >>> Qgis-developer@lists.osgeo.org >>> <mailto:Qgis-developer@lists.osgeo.org> >>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> >> >> _______________________________________________ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org> >> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org> > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer