Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geomodeling tools read capacities #55

Open
mbeaufils opened this issue Sep 23, 2022 · 2 comments
Open

Geomodeling tools read capacities #55

mbeaufils opened this issue Sep 23, 2022 · 2 comments
Labels
Use case Use case description to identify APIs roles

Comments

@mbeaufils
Copy link
Collaborator

This is to list the different formats the geomodeling tools are able to handle as inputs.
The idea is that APIs results should be as close as possible as formats expected by the geomodeling tools.
List per geomodeling tools is expected.
Geomodeling tool encompass geological modeling, hydrogeological modeling, geotechnical modeling, geotech synthesis model provision.

@mbeaufils mbeaufils added the Use case Use case description to identify APIs roles label Sep 23, 2022
@Syoichi-Nishiyama
Copy link

2 products of our geomodelling software released for the Japanese market mainly accept the following data formats:

◆GEO-CRE(https://www.oyogeotools.com/products/geo-cre.html)
Pointcloud: *.asc *.csv *.xyz *.pts .txt(x,y,z x,y,z,r,g,b)
Geometry:
.3dm *.3mf *.3ds *.amf *.dxf *.dwg *.igs *.iges *.lwo *.dgn *.fbx *.obj *.PLY *.skp *.sldprt *.sldasm *.stp *.step *.stl *.wrl *.vrml *.zpr *.glb(Use plugin) .ifc(Use plugin)
Geometry+physical properties:inp(AVS/EXPRESS UCD format)
voxel:
.csv(x,y,z,p1,p2…pn)

◆OCTAS Modeler(https://www.oyogeotools.com/products/octas_modeler.html)
Pointcloud:.txt (x,y,z x,y,z,r,g,b).las
Geometry:*.dxf(polymesh)  *.wrl
Geometry+physical properties: .inp(AVS/EXPRESS UCD format)
voxel:
.csv(x,y,z,p1,p2…pn)

//OYO team//

@neilchadwick-dg
Copy link
Collaborator

Seequent's Leapfrog is becoming dominant amongst larger organisations in the UK. I've not used it for a couple of years, but my recollection is that it accepts a very wide range of inputs. For example, it can accept AGS files for borehole data which can then be used to derive a model. Pretty sure it can also take in surfaces of various types. They can also output to IFC (pre-Geotechnical additions!). We are currently talking to the about potential import/export of AGSi.

APIs are also in place or being developed for Oasys analysis software. My recollection that it was a bespoke JSON format, but I don't have any further details to hand (it was still evolving when I left Arup, the Oasys parent company).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Use case Use case description to identify APIs roles
Projects
None yet
Development

No branches or pull requests

3 participants