topic Re: Error Invalid Extents on New Model Define City Extent in InfraWorks Forum

Error Invalid Extents on New Model Define City Extent

Anonymous — Thu, 17 May 2012 09:33:49 GMT

IM 2013.

Using coordinate system: RSA-LO29/01

Extents needed (Y over 2 million):

Min … 86690,-2916160
Max … 87790,-2915140

result is .. error: Invalid Extents

The given extent does not intersect the defined boundaries of the model coordinate system! Valid extents must be in the range of [-194843; 0] - [194843; 1.00019e+07]

...

but...

IM does allow the import of data using these values .. just cant set the City Extent..

Re: Error Invalid Extents on New Model Define City Extent

Anonymous — Fri, 18 May 2012 04:42:29 GMT

The solution for users in RSA is to use the Lo-xx-WGS coordinate system to define the City Extent.

Only use the RSA-LOxx/01 coordinate systems for importing IMX from C3D designs (when the reverse sign method is applied in C3D)

Re: Error Invalid Extents on New Model Define City Extent

Anonymous — Tue, 26 Mar 2019 10:35:36 GMT

Hi,

We are also in South Africa and tried this, but the error persists.

It is happening to all of our IW projects based in SA and is proving troublesome.

We eventually managed to get it it export to FBX via one of the "test" coordinate systems, however the scale is very strangely out when taking the FBX into any other programme.

Is there anything else we can try?

Re: Error Invalid Extents on New Model Define City Extent

Karsten.Saenger — Tue, 26 Mar 2019 12:48:01 GMT

Hi @Anonymous,

what coordinate system (CS) are you using exactly?

I recently noticed some CS issues with South African CS's, see post https://forums.autodesk.com/t5/infraworks-forum/working-with-infraworks-in-south-africa/td-p/8651592

Regards,

Karsten.

Re: Error Invalid Extents on New Model Define City Extent

bim — Tue, 26 Mar 2019 12:55:28 GMT

[...] truncated

Re: Error Invalid Extents on New Model Define City Extent

Anonymous — Tue, 26 Mar 2019 12:57:30 GMT

Hi Karsten,

We are using the Hartebeeskhoek94 set of coordinates, usually LO29, although all of them through LO19 to LO33 give the same issue.

We are usually accustomed to having to turn maps around as all of our maps import upside down. Thank you for the link, I'll forward it to my team and see if it resolves their issues.

We've been experiencing tons of interoperability issues between IW and Revit because of the CS being upside down, I'm hopeful this will work. Will keep you up-to-date whether this resolves our troubleshooting.