Data Exchange

NCP-OUSD · 30 questions

• City communications converts a plaza USD twin to glTF for the public web viewer. What must the team verify beyond a successful file write?
• Transit exports station wayfinding USD to glTF for mobile kiosks. Which validation best ensures conversion fidelity?
• Parks delivers a playground twin as glTF for a contractor tablet app. What fidelity concern should lead the handoff checklist?
• A museum converts gallery USD to glTF for accessibility web previews. Which check best verifies format-conversion fidelity?
• Public-works lookdev uses agency MaterialX graphs that must land as UsdShade networks. What should the team produce first?
• Permitting must map GIS parcel attributes into USD custom properties for hearing exhibits. What artifact should authors create?
• Transit must bring signal-controller JSON into a station twin. Which preparation defines a sound data-exchange approach?
• A water utility will import SCADA tag structures into plant twins. What should precede importer implementation?
• County archives need reviewable ordinance exhibits and heavy runway twins. How should USDA and USDC be chosen?
• Transit produces nightly LiDAR-derived stages and hand-authored platform overlays. Which format pairing matches the trade-offs?
• Parks wants human-diffable fountain setups in git and fast loads in public viewers. Which approach fits USDA/USDC trade-offs?
• Emergency management must brief stakeholders on choosing a delivery package format. What trade-off should they articulate?
• Facilities BIM must round-trip courthouse rooms through a DCC and USD. What outcome defines a successful pipeline?
• Transit round-trips platform furniture through a DCC back into USD. Which validation is essential?
• Parks artists edit playground meshes in a DCC then return content to USD. What structural property should the round-trip preserve?
• Airport lookdev round-trips gate materials between a DCC and USD shading networks. What should the pipeline prioritize?
• A zoning importer must keep nonstandard hearing-exhibit tags when bringing models into USD. Which approach supports those attributes?
• Sanitation export must retain proprietary truck-bay codes when publishing USD packages. What practice preserves those nonstandard fields?
• Fire training imports nonstandard prop metadata from a vendor format into USD. How should that metadata land?
• Library export must retain accession IDs on exhibit assets in USD. Which strategy is appropriate?
• City QA needs automated integrity checks on plaza USD exports from a DCC. What should they write?
• Transit must block bad platform packages before publish. Which data-exchange practice fits?
• Permitting QA must reject hearing-exhibit USD exports that omit stage upAxis or metersPerUnit. What should the integrity validator enforce?
• Public-works needs a curb-ramp package validator that catches broken texture and reference paths before publish. What integrity check belongs in that validator?
• A city GIS team must convert parcel extrusion meshes into OpenUSD for the digital twin. What should their exporter primarily produce?
• Stormwater engineering wants flood-plain meshes from a proprietary engineering format available as municipal USD. What is the right converter outcome?
• Transit scripts an exporter from signal-plan CAD into the city USD library. Which design best matches OpenUSD exchange practice?
• Facilities extends a DCC USD importer so housing-authority custom schemas survive into the artist scene. What should the importer extension do?
• Airport tools import gate USD that uses custom model kinds into a DCC. What importer behavior keeps civic structure intact?
• Parks extends a DCC USD importer so pavilion UsdShade networks map into the artist material stack. What is the correct focus?