Geometry in the file has extents greater than 20 miles

[chris-reese]

Hello all,

I've done extensive research and followed instructions from multiple forum posts with no success. I'll explain the situation and then what I've tried already. I've been working with the engineer to remedy this situation and have continued to fail. I'm attempting to link a Civil 3D CAD file into Revit. The CAD file is a 3D model which will be linked into a Revit model containing site and building elements. Additionally, I have access to both Civil 3D and Revit and I've attempted to manipulate the CAD file with no success. I'm also having the same situation when I try to link a different CAD project too. Lastly, I can't link the CAD file into Revit to publish coordinates to the Revit file because the extents are too great. 

I've already tried recommendations from both of these posts:

https://forums.autodesk.com/t5/revit-architecture-forum/geometry-in-the-file-has-extents-greater-tha...

https://forums.autodesk.com/t5/revit-structure-forum/geometry-in-the-file-has-extents-grater-than-1e...

The engineer has also tried:

• Sending the file with the surface "blocked" into the drawing to remove the external data reference
• followed these directions - https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/How-to-import-Civil-3D-O...
• Exporting the files to IFC

I've performed the following:

• turn on and unfreeze all layers
• bind/insert/remove all xrefs
• changed the origin of the dwg to 0,0,0
• Zoom extents and removed extra geometry
• explode all 
• create a new block and create new dwg
• cut and paste into new dwg
•  purge and audit
• removed geolocation from the CAD file

If anyone has ANY additional solutions or recommendations please let me know. I'll also update this post if I figure out what the problem is. DWG for reference. Thank you!

[SteveKStafford]

I removed all the AECC Structure label elements in the file and it loads into Revit 2018 with no warnings.

[chris-reese]

Thanks for the reply Steve,

Is there a quick way to do this? I'm still new to Civil 3D. 

Thanks, 

[SteveKStafford]

I just opened the file in AutoCAD, they were large question mark symbols. Selected them individually and deleted them until there were no more... here's my version attached.

[chris-reese]

I'm not sure what I'm doing differently but I'm still getting the "greater than 20 miles" error when I delete the orange i circles. I even deleted the layers they were on and all the extra text with it. The dwg you provided does load into Revit but there's no 3D data. There only seems to be 2D line work. Additionally, I'm having the same issue with the drawing attached and I don't see any orange i circles.

I need to resolve this issue because I have multiple other drawings on different projects and they all need to be able to be uploaded to BIM 360 Glue. 

Lastly, I tried this method and still haven't found a solution. https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2018/EN...

[SteveKStafford]

I didn't notice which version of Revit you are using. I saved the file I edited in AutoCAD 2013 version. I'm looking at the new file you've posted and I don't get any warnings but it's extents are larger and I don't see any elements after import except for a single circle. That suggests AEC elements from Civil 3D need to be saved/exported so they can be viewed in Revit.

Exploding the AEC elements to blocks was sufficient to being able to see them. I used wblock after exploding and it linked to Revit without warnings.

[chris-reese]

I'm using Revit 2019. I tried saving the file as ACAD 2013 but am still getting the error message. It's strange that you aren't getting the same error message. I think it's also worth noting that I get the "extents greater than 20 miles" whether I create a new project or try to link it into an existing project. Maybe it's something with the Revit 2019? 

I've tried xploding and creating a wblock but still got the same error. I'm definitely wondering if its a version error. 

[ToanDN]

You need ask the engineer to Export the Civil 3D DWG to vanilla AutoCAD DWG. Save As won't cut it.

[SteveKStafford]

I used the files he posted. I didn't open it in Civil 3D, I used AutoCAD Architecture 2018 and used Save set to 2013. I used Revit 2018. Don't have 2019 installed here, they skipped from 2018 to 2020.

[ToanDN]

Do you see this when you open it?

[SteveKStafford]

Looks like what I recall from Friday. Initially nothing was visible in Revit when I linked the file. After I used explode on AECC elements they were reduced to blocks and they showed up in Revit. Ideally whoever sent the file to them should export it so that's already "done".

[chris-reese]

Hi Toan,

This is exactly what I'm seeing on my end too. I didn't see the question marks that Steve referenced. I just tried this: https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/How-to-use-the-Shared-Re...

No success locating the Revit model in the location that the CAD file links too. Going to try exploding again but as I stated before, I didn't have any success exploding the CAD file or making a wblock. I'll update results after. 

[ToanDN · Accepted solution]

https://knowledge.autodesk.com/support/civil-3d/learn-explore/caas/CloudHelp/cloudhelp/2019/ENU/Civi...

File attached.

[chris-reese]

Toan,

Your file worked perfectly when I linked it into Revit. I'm trying to recreate your workflow so I can use it on other drawings but every time I try to export from C3D it crashes. I'm using the "export civil 3d drawing" tool in the output tab. Any suggestions or tips? 

I've tried purging, auditing, and creating a new drawing using a wblock. I've also tried using these commands and still C3D always crashes. https://knowledge.autodesk.com/support/civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/Expor...

[Anonymous]

I was able to fix a stubborn file with the command: geomarkervisibility=0

You still have to explode every block, purge and use the WBLOCK command, but that geomarkervisibility=0 fixed the most stubborn file.