FreeCAD Trails Workbench (Transportation and Geomatics)

[Joel_graff]

[Joel_graff]

Test for create contour feature.

Did you ever get LandXML figured out for surfaces?

[HakanSeven12]

Did you ever get LandXML figured out for surfaces?

No I thought you'd do it.

[HakanSeven12]

Hi,
The workbanch will not be displayed after manual installation. Is there a bug in the InitGui.py?

class GeomaticsWorkbench ( Gui.Workbench ):
^???????

No it works. I remove and reinstall it.

[Joel_graff]

No I thought you'd do it.

It's going to be quite a while before I have time to do that, I'm afraid.

If you're interested in getting something going sooner, I can help you set up the data structures, based on what I did for alignments. It's not hard to parse the XML, but you'll have to decide how the internal dataset that your workbench uses will be structured - whether it will follow the XML schema or if it'll be unique. I opted for a unique structure because the internal alignment data doesn't map 1:1 to the XML data.

[Joel_graff]

Hi,
The workbanch will not be displayed after manual installation. Is there a bug in the InitGui.py?

class GeomaticsWorkbench ( Gui.Workbench ):
^???????

You might want to post the error message you're getting along with your system information.

System information is available under Help -> About FreeCAD - click the 'Copy to clipboard' button, then paste the clipboard text into your post.

I don't know how Hakan has structured his workbench, but if you're running Python 2.7, there's a good chance that's the problem.

[HakanSeven12]

I don't know how Hakan has structured his workbench, but if you're running Python 2.7, there's a good chance that's the problem.

My workbench works with python 3.6

[HakanSeven12]

It's going to be quite a while before I have time to do that, I'm afraid.

If you're interested in getting something going sooner, I can help you set up the data structures, based on what I did for alignments. It's not hard to parse the XML, but you'll have to decide how the internal dataset that your workbench uses will be structured - whether it will follow the XML schema or if it'll be unique. I opted for a unique structure because the internal alignment data doesn't map 1:1 to the XML data.

Your workbench already have an Import XML function and you can add surface parse in it.Because landxml files can includes alignments and surfaces together. So its not sensible use two workbench for XML import.

If you can return a list of triangles vertexes we can create a mesh with that vertexes.

[Joel_graff]

Your workbench already have an Import XML function and you can add surface parse in it.Because landxml files can includes alignments and surfaces together. So its not sensible use two workbench for XML import.

It's really a bit more complex than that.
'
The XML parser I created can be re-used, but once you import that XML data, you need to parse it for your purposes. As you suggest, you need a list of triangles, so that's up to you to convert the XML data you need to do that.

So there's several parts to making the XML import / export modules work:

1. Create a 'surface importer' which uses the LandXML module to import LandXML data and parse it. This converts the XML data to a format that's useful to you in your workbench.

2. Create a 'surface exporter' which takes your internal data and builds the corresponding XML for use in other applications.

3. Ensure that the importer / exporter follow the LandXML schema (v1.2) for surfaces. This means you'll likely have to handle XML elements and tags you don't use, at least for exporting, to ensure your LandXML conforms the the schema and is readable by other applications.

Personally, I think you'll be better off if you get familiar with the XML schema for surfaces / survey data, if you aren't already. It will help make your workbench better because it will help you think about features / functions you might not yet have considered. It also helps ensure that what you do internally can be easily exported for use in other software. Really, if you can't export your data to LandXML and ensure it's 100% compatible with the schema so it can be used in other applications, you are only making your job more difficult later on.

All of my XML-related code is contained here:

https://github.com/joelgraff/freecad.tr ... roject/xml

The LandXML schema documentation is here:

http://www.landxml.org/schema/LandXML-1 ... .2Doc.html

I will certainly help you with the process, but I suspect it's a bigger job than you might think

[HakanSeven12]

It's really a bit more complex than that.
'
The XML parser I created can be re-used, but once you import that XML data, you need to parse it for your purposes. As you suggest, you need a list of triangles, so that's up to you to convert the XML data you need to do that.

So there's several parts to making the XML import / export modules work:

1. Create a 'surface importer' which uses the LandXML module to import LandXML data and parse it. This converts the XML data to a format that's useful to you in your workbench.

2. Create a 'surface exporter' which takes your internal data and builds the corresponding XML for use in other applications.

3. Ensure that the importer / exporter follow the LandXML schema (v1.2) for surfaces. This means you'll likely have to handle XML elements and tags you don't use, at least for exporting, to ensure your LandXML conforms the the schema and is readable by other applications.

Personally, I think you'll be better off if you get familiar with the XML schema for surfaces / survey data, if you aren't already. It will help make your workbench better because it will help you think about features / functions you might not yet have considered. It also helps ensure that what you do internally can be easily exported for use in other software. Really, if you can't export your data to LandXML and ensure it's 100% compatible with the schema so it can be used in other applications, you are only making your job more difficult later on.

All of my XML-related code is contained here:

https://github.com/joelgraff/freecad.tr ... roject/xml

The LandXML schema documentation is here:

http://www.landxml.org/schema/LandXML-1 ... .2Doc.html

I will certainly help you with the process, but I suspect it's a bigger job than you might think

After I finish this workbench, I can do something for that

I have a question for you how can I get tangent vector at a station?