Autodesk APS 混合使用RVT与DWG时AggregatedView中DWG位置偏移的配置解决方案咨询

Hey there! Let's tackle this DWG positioning issue in your AggregatedView. I've run into similar scenarios with mixed RVT/DWG models before, and the root cause almost always relates to coordinate consistency between your Revit setup and APS's model processing pipeline. Here's a step-by-step breakdown of what to check and configure:

1. Revit 端的坐标绑定与验证 #

First, let's make sure your DWG is properly integrated with Revit's shared coordinate system—this is the foundation for correct positioning in APS:

• Bind the DWG link instead of just linking it: In Revit, when you link the DWG, don't stop at just attaching it. Go to the Manage tab, find Links, select the DWG, and choose Bind Link. This merges the DWG's coordinate system with your Revit project's shared coordinates, rather than keeping it as an external reference that APS might misinterpret.
• Confirm the DWG's positioning setting: When linking the DWG initially, ensure you select By Shared Coordinates in the Positioning dropdown, not Auto - Origin to Origin or Auto - Center to Center. After binding, double-check that the DWG stays aligned with your RVT model in Revit—if it's correct here, we're halfway there.
• Re-save the RVT project: After binding and verifying, save the RVT file again before uploading it to APS. This ensures the updated coordinate data is embedded in the file.

2. APS Model Derivative 转换时的参数配置 #

The way you translate your DWG (and even RVT) in APS can make all the difference. By default, DWG translations might use internal coordinates instead of shared ones:

• Enable shared coordinates export for DWG: When creating a translation job for your DWG via the Model Derivative API, add advanced parameters to force using shared coordinates. Here's a snippet of the JSON payload you can use in your POST job request:

{
  "input": {
    "urn": "your-dwg-urn-here"
  },
  "output": {
    "formats": [
      {
        "type": "svf",
        "views": ["2d", "3d"],
        "advanced": {
          "exportSharedCoordinates": true
        }
      }
    ]
  }
}

This tells APS to prioritize the shared coordinate system embedded in the DWG (from your Revit binding) over its internal origin.

• Verify RVT translation settings: For your RVT models, ensure they're also translated with shared coordinates enabled. Most of the time, RVT translations pick up georeferenced data automatically, but it doesn't hurt to confirm the same exportSharedCoordinates: true parameter is set if needed.

3. AggregatedView 聚合时的坐标对齐 #

When setting up your AggregatedView, you need to ensure all models are aligned using the same coordinate baseline:

• Specify the coordinate system in AggregatedView configuration: When creating the aggregated view, explicitly set the coordinate reference to georeferenced or shared (depending on your project's setup). This ensures APS doesn't use internal origins for any of the models in the aggregation.
• Cross-check model coordinate metadata: Use the Model Derivative API's GET {urn}/metadata endpoint to inspect the coordinate properties of both your RVT and DWG models. Look for fields like coordinateSystem—both should show shared or georeferenced if they're aligned correctly. If the DWG shows internal, your translation parameter wasn't applied correctly.

额外排查步骤 #

If you're still seeing offsets after the above steps:

• Preview the DWG alone: Load the DWG's SVF in the APS Viewer without aggregating it first. If it's already in the wrong position, the issue is in the translation step (go back to step 2). If it's correct, the problem is in the AggregatedView configuration.
• Re-export DWG from Revit: Sometimes, the original DWG might have messy coordinate data. Export the DWG directly from your Revit project (using Export > CAD Formats > DWG) and select Shared Coordinates as the export base point. Then upload this exported DWG to APS for translation.

备注：内容来源于stack exchange，提问作者anthip