. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2.1 Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . of files, which includes a directory of metadata. The template system name (SYSNAME) is the directory name under which the template files are stored. The metadata directory (METADIR) contains pre-defined pre-defined board outlines, connector positions, schematic elements, design rules, etc. . 4.2.1 Metadata A template’s METADIR must contain the required files, and might optionally contain any of the optional

of files, which includes a directory of metadata. The template system name (SYSNAME) is the directory name under which the template files are stored. The metadata directory (METADIR) contains pre-defined pre- defined board outlines, connector positions, schematic elements, design rules, etc. . 4.2.1. Metadata A template’s METADIR must contain the required files, and might optionally contain any of the optional display window. A single click on a template’s icon on the top will load that template’s info.html metadata file and display it in the display window. A click on the OK button starts the new project creation

Creating templates The template name is the directory name where the template files are stored. The metadata directory is a subdirectory named meta containing files describing the template. All files and template name will be renamed with the new project file name, excluding the file extension. The metadata consists of one required file, and may contain optional files. All files must be created by the directory structure. Here is an example showing project files for raspberrypi-gpio template: And the metadata files: 4.3.1. Required File: meta/info.html HTML-formatted information describing the template

Creating templates The template name is the directory name where the template files are stored. The metadata directory is a subdirectory named meta containing files describing the template. All files and template name will be renamed with the new project file name, excluding the file extension. The metadata consists of one required file, and may contain optional files. All files must be created by the directory structure. Here is an example showing project files for raspberrypi-gpio template: And the metadata files: 4.3.1 Required File: KiCad 15 / 22 meta/info.html HTML-formatted information describing

directory name where the template files are stored. The metadata directory is a subdirectory named meta containing files describing the template. The metadata consists of one required file, and may contain optional Template example Here is an example showing project files for raspberrypi-gpio template: 19 And the metadata files: Required File: meta/info.html HTML-formatted information describing the template. The

3D models are external files that footprints can link to; they are not embedded in footprints. Metadata associated with the footprint. Footprints in KiCad are organized into footprint libraries, which on a set of parameters. Editing footprint properties Footprints have a number of properties and metadata items that can be defined. These include text fields, attributes that can be set or not (such as files as well as other exports, such as STEP files. Additionally, the footprint type is included as metadata in IPC-2581 exports. Footprint 3D models can be shown and hidden in the 3D viewer based on their

3D models are external files that footprints can link to; they are not embedded in footprints. Metadata associated with the footprint. Footprints in KiCad are organized into footprint libraries, which on a set of parameters. Editing footprint properties Footprints have a number of properties and metadata items that can be defined. These include text fields, attributes that can be set or not (such as files as well as other exports, such as STEP files. Additionally, the footprint type is included as metadata in IPC-2581 exports. Footprint 3D models can be shown and hidden in the 3D viewer based on their

ERP system via a REST API. The REST endpoint can provide symbol and footprint mappings and other metadata. A search panel in the Schematic editor, which lets you search for symbols, labels, and schematic initially created. 3 Symbol fields are now synced to footprints in the PCB, so schematic symbol metadata is available in the board design. Graphical polygons on copper PCB layers can now have nets assigned

ERP system via a REST API. The REST endpoint can provide symbol and footprint mappings and other metadata. A search panel in the Schematic editor, which lets you search for symbols, labels, and schematic are initially created. Symbol fields are now synced to footprints in the PCB, so schematic symbol metadata is available in the board design. 3 Graphical polygons on copper PCB layers can now have nets

3D models are external files that footprints can link to; they are not embedded in footprints. Metadata associated with the footprint. Footprints in KiCad are organized into footprint libraries, which on a set of parameters. Editing footprint properties Footprints have a number of properties and metadata items that can be defined. These include text fields, attributes that can be set or not (such as files as well as other exports, such as STEP files. Additionally, the footprint type is included as metadata in IPC-2581 exports. Footprint 3D models can be shown and hidden in the 3D viewer based on their