Customizing USD

NCP-OUSD · 12 questions

• County IT must ship a municipal CRS helper plug-in for the city's digital-twin viewers. What build constraint is essential?
• Transit is compiling a platform schema plug-in for authority viewers. What should the build match?
• A city digital-twin lab must run OpenUSD in an air-gapped environment with agency-approved libraries only. What is the right approach?
• Public-works assets include underground utility vaults that do not fit stock model kinds cleanly. When is a custom model kind appropriate?
• Transit wants a custom kind for platform-segment under model hierarchy rules. What is the goal of that customization?
• Permitting needs consistent parcel-setback metadata on hearing-exhibit stages. Which customization fits?
• A water utility must represent valve-actuator state beyond what stock UsdGeom provides. What should developers create?
• Housing unit packages use an authority-specific asset URI scheme that standard file resolvers do not understand. What should the team integrate?
• Airport import/export must carry proprietary gate-status fields through USD without dropping them. Which approach supports nonstandard attributes?
• Stormwater needs procedural flood-extent meshes to appear in Hydra without baking permanent USDA geometry. What should developers write?
• Emergency management wants temporary barricade geometry materialized for Hydra during drills without shipping full mesh assets. Which customization fits?
• Library exhibit tooling needs placeholder pedestals that resolve as renderable geometry without separate pedestal USD files on disk. What should they write?