OCCT Community Samples & Projects Registry

A curated, in-repo registry of open-source projects built on Open CASCADE Technology plus, where available, runnable usage samples demonstrating how these projects integrate with OCCT.

The registry is community-driven and grows by contribution. It gives the community a place to:

• discover OCCT-based projects without leaving the repo,
• propose their own project for inclusion via a structured GitHub workflow, and
• find concrete usage samples next to the project metadata.

Scope

This registry holds OCCT-team projects (authored or maintained by Open Cascade SAS / the OCCT project, including the commercial OCCT Components) and open-source third-party projects built on OCCT. Third-party non-open-source products are out of scope here - see CONTRIBUTING.md.

Layout

applications/   End-user apps (viewers, modelers, inspectors, converters, ...)
libraries/      Reusable libraries and frameworks built on top of OCCT
wrappers/       Language bindings (C#, Java, JavaScript, Python, ...)
examples/       Usage sample apps (own repos, demo / reference code - OCCT or community)

examples/ is for sample/demo apps that ship in their own repositories (e.g. an OCCT C# demo on Windows, a Qt viewer skeleton). Authorship can be either OCCT-team or community. It is distinct from wrappers/ (the bindings themselves) and from applications/ (end-user products).

Each project lives in <bucket>/<category>/<slug>/ and contains:

• project.yaml - structured metadata (see SCHEMA.md)
• README.md - human-facing description, screenshots, and links
• (optional) a snippets/ subfolder - usage / integration snippets shipped with the entry

Browsing

• By bucket: start at the README.md inside each top-level folder (applications | libraries | wrappers | examples).
• By taxonomy: see _taxonomy.yaml for the canonical list of industries, scopes, software types, and licenses used across all entries.

Adding a project

Recommended path: open a Project Registration issue. Go to Issues -> New issue -> Project Registration, fill the form, and a maintainer will land the entry as a PR on your behalf. No CLA required.

Direct PRs are also welcome - the registry is metadata + Markdown, no signature needed. See CONTRIBUTING.md for the workflow.

OCCT Components (commercial extensions)

Open Cascade SAS maintains a separate suite of commercial OCCT extensions - data exchange (DXF, ACIS-SAT, JT, Parasolid, RVM, IFC, USD), mesh processing, PMI / volume / web visualization, automation (BestFit, CAM, unfolding, collision detection), and C# / Java wrappers. They are not mirrored in this registry:

• Source-code preview: Open-Cascade-SAS/OCCT-Components
• Licensing: occt3d.com/components

Notice & legal

This registry is a community catalog, not an endorsement. Inclusion of a project here does not imply that the OCCT project, Open Cascade SAS, or any of its contributors endorse, support, vouch for, or are affiliated with the listed project. Conversely, exclusion is not a judgment.

All product names, logos, and trademarks are property of their respective owners; their use here is nominative (referring to the project by its own name) and not a claim of ownership.

Each project.yaml carries a source: field stating how the entry was created:

source value	Meaning
occt-team	Authored or maintained by Open Cascade SAS / OCCT project.
maintainer-confirmed	Project maintainer (or someone with their permission) registered the entry - either through the Project Registration flow on this repository, or had previously opted in via the dev.opencascade.org listing form.

There is no path for unsolicited third-party listings - the registry only holds entries with maintainer consent or OCCT-team authorship.

Removal & correction requests

If you maintain a listed project and want the entry removed or corrected:

1. Open a GitHub issue with title Samples - Remove <project name> or Samples - Correct <project name>, OR
2. Reach the OCCT maintainers via the contact form at dev.opencascade.org/webform/contact_us (or the "Contact us" link on occt3d.com).

Removal takes effect on the current branch and in subsequent releases. The repository's git history keeps the prior commits - this is normal version-control behaviour and matches every package index and software directory; rewriting history is not offered.