I agree with you on this, was just mentioning it more to see if it was the same effort or different one the upverter side. Generally, I wish the KiCad team (or really ) would take this sort of thing on. Actually, one of the next steps we’ve been considering is automated documentation generation, so managing all of these files could become important. We can also edit the script to move the svgs into a. An svg per PCB layer is a neat idea, but we would probably build the layout into a single SVG and let the renderer handle toggling layers on/off.

In future versions we can build it as a GitHub application so that the conversion is run in the cloud so that you don’t have to commit the svg artifacts. It’s frustrating, but we believe companies using proprietary file formats as a tool to increase switching cost for users is one of the big issues destroying progress in hardware Thanks! Yeah, that’s right. It’s very similar to what upverter was doing before they closed it. We wanted something that was well-supported by many software libraries and had a relatively intuitive hierarchy, so landed on a JSON format. Right, there are pros/cons to a lot of file formats, like Altium’s pipe-delimited format, Eagle’s XML format ( now closed source packaged with installer), KiCAD’s ASCII format (possibly based on gEDA?).

Pcbdoc kicad