Geotechnical Work Addon

[Joel_graff]

it is not only lp on windows, mos linux coin pivy have the same problem.

@joel that would be great if we could just not use on systems whivh do not have it. Most people do not use tons of data if starting with trails.

If we would do this and the recoursive download of submodules with the addon manager trais would install just as simple as any other work bench.

Ok, I'll dig into the code and see what I can do to maybe switch it off. The issue is, it's tied to a specific build of pivy, so if I can determine that, I can probably build a switch that works - though I don't know that I can reliably determine that independent of the platform... Otherwise, I need to switch it off for anyone using v0.18.

As for the submodules, I agree on the recursive suggestion. I don't think it introduces problems for projects that don't have submodules, so I would argue it's harmless to use it when it's not needed.

[bernd]

it is not only lp on windows, mos linux coin pivy have the same problem.

@joel that would be great if we could just not use on systems whivh do not have it. Most people do not use tons of data if starting with trails.

If we would do this and the recoursive download of submodules with the addon manager trais would install just as simple as any other work bench.

Ok, I'll dig into the code and see what I can do to maybe switch it off. The issue is, it's tied to a specific build of pivy, so if I can determine that, I can probably build a switch that works - though I don't know that I can reliably determine that independent of the platform... Otherwise, I need to switch it off for anyone using v0.18.

As for the submodules, I agree on the recursive suggestion. I don't think it introduces problems for projects that don't have submodules, so I would argue it's harmless to use it when it's not needed.

how about write some small method which uses the new coin features. Put in a try: except: If it works everything is fine if not set some variable and use this every time some new features of coin are used. Might not be samrt but should work.

BTW: See https://forum.freecadweb.org/viewtopic.php?f=24&t=49575 I would like to get this somewhere without making another fork Your AddOn would perfectly fit ... I may play and fix more of the old geodata tools.

[Joel_graff]

how about write some small method which uses the new coin features. Put in a try: except: If it works everything is fine if not set some variable and use this every time some new features of coin are used. Might not be samrt but should work.

Yeah, a try/catch test would work, but it's not quite kosher from a programming perspective.

Anyway, I've written the switch code. If your pivy version is less than 6.5, it disables the code for SoGeo coin nodes. It should stop the error for you, anyway.

[bernd]

Yeah, a try/catch test would work, but it's not quite kosher from a programming perspective.

totally agree with you here.

It should stop the error for you,

I can swith without errors to trails and OSM import works

Screenshot_20200820_203959.png (248.96 KiB) Viewed 1348 times

[bernd]

Next step would be to make the AddOn manager use the recursive switch or move the additional code outside into Mod and install them separately with the AddOn manager.

BTW what happens if pivy tracker is installed twice, once inside trails and once with the AddOn manager into Mod?

[Joel_graff]

I can swith without errors to trails and OSM import works

Great!

Next step would be to make the AddOn manager use the recursive switch or move the additional code outside into Mod and install them separately with the AddOn manager.

BTW what happens if pivy tracker is installed twice, once inside trails and once with the AddOn manager into Mod?

I'd rather keep them as submodules in Trails. However, I can argue it either way. I like the submodule approach because everything comes as one package and it only requires the --recursive switch to make it work. The flip side is implementation - anyone else wanting to use it should include it in their workbench as a submodule as well.

As for which one takes precedence, it's in the order of import. So if pivy_trackers at the /Mod level is imported after FreeCAD.Trails.pivy_trackers, then it will override the submodule, since both share the same top-level path (pivy_trackers/pivy_trackers).

I could mitigate that by removing the extra pivy_trackers/ level, which would make it uninstallable as a /Mod addon and force it to function only as a submodule.

[bernd]

IMHO it is up to you which way to go.

Just a remark from my side. I even know how python imports work but found it cumbersome when I first started with trails. When I first tried to install trails I installed it via AddOn manager and than read here and there and than I thought aah I need to install pivy tracker, thus AddOn manager and install pivy tracker but this was totally wrong. The time beeing I know how things work out in trails but someone with no python knowledge will be confused.

There need at least to be some hints in readme. Even if AddOn manager would do the recursive download. If pivy tracker stays in AddOn manager as separate module, there should be a hint in trails that pivy-tracker should not installed separatly but will or should be installed inside trails. As long as AddOn manager does not do the recoursive upload the readme should mentions the git clone command or which submodules to copy where.

People might ask and get confused anyway, but than we could just post a link on the readme. Posting a link to the readme could be done by far more people than you and hakan.

If trails would install more easily it will for sure be used be some more people because this is great stuff

Ahh, some small PR ... https://github.com/joelgraff/freecad.trails/pull/61

[Joel_graff]

People might ask and get confused anyway, but than we could just post a link on the readme. Posting a link to the readme could be done by far more people than you and hakan.

If trails would install more easily it will for sure be used be some more people because this is great stuff

Ahh, some small PR ... https://github.com/joelgraff/freecad.trails/pull/61

It is in the readme:

https://github.com/joelgraff/freecad.tr ... pendencies

Before there were a lot of pictures, it may have been easier to spot. Or not. I really don't know. There's too many pictures there now, so I suspect some should maybe get removed... or reduced to a gallery or something.

Merged the PR - thanks for that!

I'm glad geodata has found new life inside trails. So far, none of that is me. I just want to make sure I don't get in anyone's way.

[bernd]

you are dam right everything is in the readme already ...

I will give it a try on win libpack version too and report back.

[bernd]

is there a special reason why GeoDataWB with upper case chars and not such simple name as geoimport for all these kind of tools?