[OSM-talk] Osmarender 3.0

[Nick Hill]

Hello Tom

That would be a good option. Perhaps use the agent string, user 
preference or javascript to determine SVG compatibility.

If SVG rendering is not available, then do something like:

xmlstarlet tr osmarender.xsl osm-map-features.xml | rsvg-convert -f png 
 >myimg.png

Which could easily be put into a script under apache, with a suitable 
MIME header to serve a pre-rendered png.

However, I feel we should encourage adoption of open standards such as 
SVG, and help iron out bugs in the implementations. We can suggest (but 
not require) users to use an SVG plug-in if the browser doesn't support 
SVG. It is reasonable for there to be feature set and speed enhancements 
to be achieved by using SVG. This will apply pressure to M$ to support SVG.

IF a user is using png, include a link on the viewer page along the 
lines of: "It appears your browser doesn't support scalable vector 
graphics (SVG). See: <a 
href='http://wiki.openstreetmap.org/index.php/SVG'>Updating to SVG</a>

Tom Chance wrote:
> Ahoy,
> 
> On Thursday 28 September 2006 11:34, Andy Robinson wrote:
>> Obviously some compatibility issues with the SVG and browsers but bearing
>> in mind the IE oriented populous out there a link to the Adobe viewer
>> download would provide a significant number with functionality.
> 
> What about optionally popping the SVG through Inkscape or rsvg or something 
> similar on the server to produce a PNG instead?
> 
> Regards,
> Tom
>