The mesh database
The shared catalog of object types: what you can see in it, what you can read from it, and how to browse it.
The mesh database is the catalog of object types: plates, holders, tip boxes, instruments. Each item has a name (the object type) and a folder of files: the URDF, the object model YAML, the meshes, and, for objects that can be localized, tag files.
You do not edit the catalog. You copy an item's model files into your project, where you can edit them; see Adding an object. The meshes stay in the catalog and are read from it when a world loads.
What you can see
An item is visible to you when it is public, or when it is shared with your organization. Items of other organizations are not listed, and asking for one by name answers "not found", the same as a name that does not exist.
What you can read
With your own sign-in or API token you can read an item's listing (name, tags, file list) and its model files:
<name>.urdf<name>.object_model.yamltags.yamlandunits/<handle>/tags.yaml, when the item has them
Meshes and other files are not downloadable with your credentials; a request for one is refused with a message pointing you to add the object to a project instead. The platform reads the meshes on your behalf when it loads a world that uses the item.
Browsing from the CLI
zeon mesh-database list
zeon mesh-database list --tag <tag>
zeon mesh-database show wellplate_96_flatbottom| Command | What it prints |
|---|---|
zeon mesh-database list | The items visible to you. --tag keeps items whose tags include that exact string. |
zeon mesh-database show <name> | One item: manifest (file list), tags, visibility, import time. |
An item record holds:
| Field | Description |
|---|---|
name | The object type. Lowercase, ^[a-z_][a-z0-9_-]{0,63}$. |
manifest | Every file in the item folder, with sub-paths. |
tags | Free-form labels for filtering. |
visibility | Whether the item is public or shared with specific organizations. |
imported_at | When the item was last uploaded. |
anchor_count, preset_count, part_count, anchors, presets, parts | A summary of the object model. Empty means "not computed" for that item, not zero. |
Browsing in the app
The Object Database lists the catalog your organization can see, with your project's copy taking the place of the catalog's where you have one. The object picker in the World Builder lists the same catalog.
Items without a model
Some items carry only geometry: no <name>.urdf and <name>.object_model.yaml pair. They are listed, but cannot be added to a project. zeon new object refuses them with a message naming the missing files, and the Object Database shows them disabled with (missing URDF and YAML).
Versions
An item has one current set of files. There is no version to pin. A project keeps the model files it copied until you replace them, so a later catalog change does not reach your anchors. Meshes are always read from the catalog entry.
When you need an object that is not there
Adding or changing catalog items is done by Zeon. Contact Zeon with the object you need. To change anchors, parts or presets for your own use, edit your project's copy; that needs no catalog change.
Updated 9 days ago