SVGs in reference documentation

[paagkame]

Describe the problem

We use SVGs in the reference documentation that look like exports from a 3D/CAD software.

See for example: https://opensimulationinterface.github.io/open-simulation-interface/structosi3_1_1MovingObject.html

Small edits with a vector graphic tool are possible, but major changes like creating another vehicle should come from the origin software that has been used.

Describe what you have already tried

For changes I group paths of the SVG that belong together, for example, all paths that belong to the wheel to move/hide it or copy and paste it into another SVG.

But some style went missing as my vector graphic software wasn't the origin software, for example, the arrow heads of the coordinate systems. I had to rebuild them with another object instead of applying an style to the path.

Describe your research

Newly crearted objects in a vector graphic tool would never look alike.

SVGs use a vanishing point perspective.

Text is converted to path, but seems to be Gill Sans MT.

Ask your question

Who created this SVGs initially?

What tool did they use?

Would it make sense to collect all objects like, a car, a truck, a traffic sign, a traffic light, etc. in a library to be more?

Can we agree on a few guidelines for editing svgs.

[paagkame]

@engelben
Do you know who created the SVGs initially?

[paagkame]

SVG are an export of the 3D blender file.

Still to be clarified: Where are the native blender files.