Land XML Import from Bentley Inrail Suite 2004 Edition

[Anonymous]

Hi,

I've posted a Land XML file to the Customer Files NG (The message header is
the same as this one) which has a single DTM in it.

When I go through the Land XML import process in Land Desktop 2006
everything seems to happen correctly - except that I have no data imported
to the Surface.

Is there any explanation for this failure?

--

Regards,


Laurie Comerford
www.cadapps.com.au

[Anonymous]

Laurie,

The LandXML schema allows for DTM source data as well as the actual DTM Tin.
Bentley (Inroads, etc) is written to handle DTM source data, whereas
AutoDesk Land products cannot. LDT will only import/export the built TIN -
no input data. If the AutoDesk import algorithm was written correctly, this
should not be a problem - but unfortunately, we have what we have. When LDT
encounters a properly formatted LandXML TIN with properly formatted tin
input data ( source data) - points, breaklines (feature lines); etc, LDT
becomes confused; the result is that the TIN surface name is created, but
nothing else.

I opened your LandXML file with an ASCII editor (WordPad will work), and
deleted all the lines between the two headers, including the
two headers, and resaved the file. LDT now imports the TIN correctly -
13,222 points, the triangulation looks like an existing roadway.

The Bentley operator also has the ability to turn off the source data
options when he exports - which will also make for a much smaller file.

Good luck,

sc




"Laurie Comerford" wrote in message
news:5104493@discussion.autodesk.com...
Hi,

I've posted a Land XML file to the Customer Files NG (The message header is
the same as this one) which has a single DTM in it.

When I go through the Land XML import process in Land Desktop 2006
everything seems to happen correctly - except that I have no data imported
to the Surface.

Is there any explanation for this failure?

--

Regards,


Laurie Comerford
www.cadapps.com.au

[Anonymous]

Thanks Steve. That info will come in handy.

John

[Anonymous]

Hi Steve,

Thanks. That resolves the problem for a Land Desktop user. I've also heard
that there is a patch for Land 2006 to fix it there also - but haven't
confirmed that.

For those interested Civil 3D handles the original file without problems.

--

Regards,


Laurie Comerford
www.cadapps.com.au

"Steve Cannon" wrote in message
news:5104876@discussion.autodesk.com...
Laurie,

The LandXML schema allows for DTM source data as well as the actual DTM Tin.
Bentley (Inroads, etc) is written to handle DTM source data, whereas
AutoDesk Land products cannot. LDT will only import/export the built TIN -
no input data. If the AutoDesk import algorithm was written correctly, this
should not be a problem - but unfortunately, we have what we have. When LDT
encounters a properly formatted LandXML TIN with properly formatted tin
input data ( source data) - points, breaklines (feature lines); etc, LDT
becomes confused; the result is that the TIN surface name is created, but
nothing else.

I opened your LandXML file with an ASCII editor (WordPad will work), and
deleted all the lines between the two headers, including the
two headers, and resaved the file. LDT now imports the TIN correctly -
13,222 points, the triangulation looks like an existing roadway.

The Bentley operator also has the ability to turn off the source data
options when he exports - which will also make for a much smaller file.

Good luck,

sc




"Laurie Comerford" wrote in message
news:5104493@discussion.autodesk.com...
Hi,

I've posted a Land XML file to the Customer Files NG (The message header is
the same as this one) which has a single DTM in it.

When I go through the Land XML import process in Land Desktop 2006
everything seems to happen correctly - except that I have no data imported
to the Surface.

Is there any explanation for this failure?

--

Regards,


Laurie Comerford
www.cadapps.com.au