You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: j.chetwynd[at]btinternet.com [Submitted to the original trac issue database at 1.32pm, Sunday, 26th June 2011]
All major browsers now support SVG natively.
mapnik is not currently served with the correct mime type, and hence is saved top disk, rather than rendered in the browser
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 7.42am, Monday, 27th June 2011]
I assume you are talking about the results of the export tab on the home page? If so then that is served as image/svg+xml which I believe to be the correct type - certainly it is what is listed in my mime.types file. If you have a source that says it should be something else then please let me know.
What you are seeing is not the result of the mime type being wrong, it's the result of us deliberately sending a Content-Disposition header with all the exports because they are intended to be exporting a map to disk, not rendering it in the browser. In addition to which most browsers would choke on the quantity of SVG that a typical map export involves so letting the browser try and render it is generally a bad idea.
Mapiteritive is nothing to do with us - you would need to report any issue you have with that to it's author.
Reporter: j.chetwynd[at]btinternet.com
[Submitted to the original trac issue database at 1.32pm, Sunday, 26th June 2011]
All major browsers now support SVG natively.
mapnik is not currently served with the correct mime type, and hence is saved top disk, rather than rendered in the browser
The text was updated successfully, but these errors were encountered: