We are pleased to announce the release of the Smart Construction Dashboard periodic update with the following dates and details.
Wednesday, February 8, 2023
No. | content | Target function | over view |
1 |
bug fixes | Data layer | When executing “Apply Vertical offset ” to Design file in a project which uses CRS, the vertical position of the Designs was not displayed correctly. |
2 |
improvement | machine list | Improved machine list speed performance. |
3 |
improvement | Data layer | By reviewing the data loading process,The time it takes to display point cloud data after it is uploaded has been reduced by an average of 40%. |
4 |
improvement | Data layer | When importing a LandXML file created by CAD software that contains perimeter lines, boundary lines were sometimes displayed in unexpected areas. We have now corrected this problem so that boundaries are not created for auxiliary perimeter lines. |
5 |
improvement | viewer | The position and direction of zooming when clicking the "Home" icon on the map can now be set for each project. |
6 |
bug fixes | Measurement | When creating annotations and changing the display order, the changed order could not be saved correctly. This has now been corrected so that it can be saved correctly. |
7 |
new function | Data layer | The coordinate system of uploaded las, dxf, and tiff files can now be changed. This allows for the addition or modification of missing or incorrect coordinate system information in uploaded files. |
8 |
bug fixes | Measurement | In the measurement function, when selecting a polygon to display the gradient, the gradient display and gradient heat map for some areas were incorrectly displayed. |
9 |
bug fixes | viewer | When the target design plane was changed, the construction history data was sometimes displayed in the 3D Viewer with the information of the previously set target design plane. This time, we have corrected the problem so that the construction history data corresponding to the newly set target design plane information is displayed correctly. |
10 |
other | Measurement | In the measurement function, when a line segment is created and "Distance between points" is added, the horizontal distance between the vertices was previously displayed. This time, when "Distance between points" is added, the function has been modified to display the three distances between the vertices: diagonal, vertical, and horizontal. |
11 |
improvement | Data layer | In the past, when selecting topographic data to be referenced when creating a measurement, only the date was displayed. This time, we have improved the display to show the data file name in addition to the date. |
12 |
new function | Data layer | When registering data (las, dxf, tiff files), the coordinate system can now be specified. |
13 |
Integration of clauses | Help function | The Terms of Use and Terms of Service have been integrated. |
14 |
bug fixes | Data layer | When past ortho images were selected and displayed in sequence, the ortho images were not switched correctly. Fixed so that selected ortho images are displayed correctly. |
15 |
bug fixes | Data layer | Fixed an error that occurred when registering a 0-byte file. |
16 |
bug fixes | Data layer | The list of coordinate systems (CRS) to be set for a project (site) sometimes included some coordinate systems that were not available for a given location. This has been corrected so that they are displayed correctly. |
17 |
bug fixes | Data layer | When registering files with capitalized file extensions, file uploads sometimes failed. This has been corrected so that the file can be uploaded correctly. |
Friday, February 17, 2023
No. | content | Target function | over view |
1 |
bug fixes | Data layer |
When registering survey data, if the data contains blank areas, the point cloud can be complemented. Each of these has been corrected to work correctly. Translated with www.DeepL.com/Translator (free version) |
2 | bug fixes | Measurement |
When calculating the progress rate by specifying an area in the annotation, the heat map showing the progress rate was changing according to the selected area. |
3 | bug fixes | Data layer |
Download of ortho data consisting of multiple files sometimes failed. Fixed so that it could be downloaded correctly. |
Thursday, March 23, 2023
No. | Content | Target function | over view |
1 |
new function | Data layer | From the header menu ("?" icon in the upper right corner of the screen) mark icon in the upper right corner of the screen), You can now check product information and inquiries from the header menu |
2 | bug fixes | Data layer |
When importing historical data for initial registration work, some of the target design data was mistakenly imported as survey history data. |
3 | bug fixes | Data layer |
When DTM data was registered and custom projection settings were made, an error would occur during import. |
4 | bug fixes | Data layer |
In some cases, data could not be displayed correctly on the 3D map in Chrome on Mac. |
5 | bug fixes | Data layer |
Design data with sublayers could not be downloaded. Fixed so that it could be downloaded correctly. |
Wednesday, March 29, 2023
No. | Content | Target function | over view |
1 |
new function | machine list | Users (leaders and above in the jobsite setting) who are invited to a project (jobsite) can now perform the following operations -Remote support (viewing) of construction equipment. -Transfer project files (SL3 files) to the construction equipment. |
2 | bug fixes | Data layer |
When viewing survey data created in LandXML format in a mesh view, split lines were sometimes displayed on the data. |
3 | bug fixes | Report |
When creating a PDF report, an error would occur if there was measurement data created with "Polygon" and "Construction Area". |
4 | bug fixes | Data layer |
When loading survey data in LandXML format, an error occurred and the data could not be loaded. This has been corrected so that the data can be imported correctly. |
5 | bug fixes | Data layer |
Asbuilt data range was narrower than the original data and could not be acquired correctly. This has been corrected so that the Asbuilt data can be acquired correctly. |
Comments
0 comments
Please sign in to leave a comment.