SVG images exported by Python's matplotlib are not clipped correctly, the matplotlib developers have closed a corresponding bug report years ago, describing the root cause in detail (https://github.com/matplotlib/matplotlib/issues/4341).
The attached file renders correctly e.g. in Firefox.
Steps to Reproduce:
1. import the attached SVG-file into a drawing
The actual plot curve overlaps the axes.
The actual plot curve should be within the plotting window.
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 139102 [details]
SVG generated by matplotlib, renders incorrectly in LO
Created attachment 139103 [details]
Image exported as PNG by matplotlib
This is the correct rendering as rendered e.g. by Firefox
Created attachment 139104 [details]
Wrongly rendered SVG image, exported as PNG
This PNG is exported by LO, showing LO's faulty rendering of SVG images
Build ID: 80fb8d406ced47e6a2089f0c8ba5c103d2fec91f
CPU threads: 4; OS: Windows 6.3; UI render: GL;
TinderBox: Win-x86@42, Branch:master, Time: 2018-01-15_05:18:42
Locale: nl-NL (nl_NL); Calc: CL
Build ID: 3215f89-f603614-ab984f2-7348103-1225a5
Created attachment 139119 [details]
reduced file, which still shows the error
It has nothing to do with the position of the clipPath definition. I have moved it to the begin and removed all <g> elements, so that it is on same level as the referencing element and known before used.
I think it is similar to bug 97657: The clip-path attribute is not supported.
It makes no difference, whether you use a path or rect for the clipPath.
The error still exists in Version: 220.127.116.11.alpha1+ (x64)
Build ID: e33424dd887cb1a11a3dba2513ef0f4bf93a6dbe
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-01_00:43:29
Locale: de-DE (en_US); Calc: CL
*** Bug 100135 has been marked as a duplicate of this bug. ***
Reverting 5903235d57acb13d9d5286d23b443a01aeab9a3c would fix this issue. thus, duplicate of bug 97539
*** This bug has been marked as a duplicate of bug 97539 ***