https://communities.bentley.com/products/geotech-analysis/f/forum/204531/modelling-cpt-data-in-svdesignerI used a feature to import borehole data from gINT. It assumed captions for fields and tables that are not actually in my gpj (BOREHOLE etc where I have POINT and PointID). Also, I would have liked to select which PointIDs were imported, we don&#39;t alwaysen-USTelligent Community 12https://communities.bentley.com/thread/614752?ContentTypeID=1Sat, 17 Oct 2020 10:40:28 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:34f79a59-5611-4239-bf5b-272100ff1471Phil Wade<p>My POINT table doesn&#39;t have the caption set to BOREHOLE, but SVDESIGNER thinks it does.</p> <p>OK&nbsp;it can&#39;t import CPTu, but it can import dissipation tests.&nbsp; Something for the future?&nbsp; This was a major reason an end user didn&#39;t buy.</p><div style="clear:both;"></div>https://communities.bentley.com/thread/614681?ContentTypeID=1Fri, 16 Oct 2020 16:24:14 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:aca4ed79-6b79-4728-a5ec-c26727e06bcaFaseel Khan<p>Regarding the gINT import, our import dialog does support choosing which fields and tables to associate with what data, so they don&#39;t need to be in a specific name. I&#39;m not sure if the user missed this or if something isn&#39;t working right there.</p> <p>&nbsp;</p> <p>SVDesigner can import and display CPTu data - it currently only handles this PWP aspect of CPTs at discrete sample points, not soil properties or anything like that. It doesn&#39;t get used in modeling other than that it can be included in the SVFlux analysis for calibration validation purposes. That is, the user can compare the analysis output PWP to the measured PWP from CPTs. There are no examples currently.</p><div style="clear:both;"></div>