Eagle import: Unsuported layer tKeepout. Should this be F.CrtYd?

[Rene Poeschl]

From https://www.autodesk.com/products/eagle/blog/every-layer-explained-autodesk-eagle/ i would gather that the keepout layers in eagle is used for the same thing as the courtyard layers in kicad. If this is correct then it might be a good idea to convert drawings from the keepout layer to the courtyard layers on import (right now it is pushed to the dwgs layer by default.)

[Wayne Stambaugh (stambaughw)]

This would seem to be the case but I'm not sure it can be mapped 100% to KiCad but it might be close enough to be worthwhile. Does anyone have any reason as to why we shouldn't do this?

[Rene Poeschl (poeschlr)]

Can DRC deal with filled polygons on the courtyard layer? If it can not then we might need to additionally convert such filled polygons to pure outlines as part of the import step. (Might be a good idea anyways as it would fit better with other kicad footprints. But if DRC can deal with filled polygons than this is only a bonus that might be best as an option of the import.)

[Seth Hillbrand (sethh)]

It can. We pushed that off to v6 as polygons render filled to gerbers in 5.0

[Rene Poeschl (poeschlr)]

Is the courtyard layer intended for gerbers? I thought that one is intended for kicad internal use only? (For checking if two parts are too close to each other.)

[Seth Hillbrand (sethh)]

You are right. I'm conflating the Edge.Cuts layer. But the logic we use for that can be used for courtyard as well. And probably should.

[KiCad Janitor (kicad-janitor)]

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2347