Topics

1

General / Cameras positions and EO for multi-cameras layouts

« on: August 03, 2023, 05:15:46 PM »

Hey every one,

I can't find a way to import cameras (Inpho Project File) in a multi-cameras layouts chunck.

My data is maid of RGB files and NIR files in separated folders. When I import my RGBs photos, I can import locations and EO contanied in an Inpho file. But when I create a multi-cameras layouts chunck, this same Inpho file cannot be imported succesfully.

I also tryed to export the references imported from the Inpho file in a RGB chunck to a multi-cameras layouts chunck but without much more success.

Does anyone have an idea to solve or subvert this ?

2

General / Normals in laz export

« on: July 18, 2023, 04:31:19 PM »

Hello there,

I'm pretty interested in exploiting normals calculted in AM for future analysis, such as ground segmentation, with PDAL.

As far as I know, laz spec are not designed to embed normals data. But it is possible to export those from AM point cloud interface.

Because I can't find where and how are they stored, does anyone can help me on this ?

Cheers

3

General / Exporting camera calibration to Inpho

« on: September 22, 2021, 12:35:30 PM »

Hey there,

While I was controling an export of a camera calibration in Inpho format made on a 1.7.4 release, I noticed significants differences between the floatings displayed on the camera calibration tool (which are the same as stored in an Agisoft xml export) and the values stored on the Inpho txt file.

The following values are the adjusted ones of a CityMapper. The distortionlessness of this sensor is traducted by the lack of k1,k2,etc and p1 and p2 values.

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>
<calibration>
  <projection>frame</projection>
  <width>10336</width>
  <height>7788</height>
  <f>15963.115384616023</f>
  <cx>-1.3333000000002044</cx>
  <cy>-4.7148000000001868</cy>
  <date>2021-09-22T08:40:25Z</date>
</calibration>
The table below is the export of the same calibration (adjusted) in Inpho.

Code: [Select]

$CAMERA
  $TYPE : unknown
  $DATE : 10:43:20 22/09/2021
  $BRAND : Custom
  $KIND : CCDFrame
  $CCD_INTERIOR_ORIENTATION :
     299.114       -0    5166.17
       0.0000000000    -299.114    3888.79
  $CCD_COLUMNS : 10336
  $CCD_ROWS : 7788
  $PIXEL_REFERENCE : CenterTopLeft
  $FOCAL_LENGTH :    53.3681
  $PRINCIPAL_POINT_PPA :     0.000000     0.000000
  $DISTORTION_TYPE :  Polynomial
  $RADIAL_COEFFS :
                      0             -7.25205e-19                  6.26401e-22                  7.52744e-24
                      -1.34583e-26                  0                  0                  0
  $DECENTRE_COEFFS :
                      3.46799e-19                  1.68792e-19                  0                  0
  $GPS_ANTENNA_OFFSET :     0.000000     0.000000     0.000000
  $CAMERA_MOUNT_ROTATION :     0.000000

As you can notice, principals points coordinates ($PRINCIPAL_POINT_PPA) are set to 0 and radials ($RADIAL_COEFFS) as well as tangentiels ($DECENTRE_COEFFS) distortions are not set to 0.
Actually, I was expecting the exact opposite result.

Is this way of converting values is the regular one ? Along my research on this topic I noticed ways to convert values but the difference here seems to be too significant.

Best regards
Gabriel

4

Python and Java API / python script differences between 1.7.3 and 1.7.4 releases

« on: August 31, 2021, 02:55:53 PM »

Hey there,

I've been using on the 1.7.3 release a python script to orient cameras based on a csv containing EO. Here is this script (by the way, thanks to Alexey and Paulo) :

Code: [Select]

import Metashape

chunk = Metashape.app.document.chunk
crs = chunk.crs
T = chunk.transform.matrix

origin = None
for camera in chunk.cameras:
if not camera.type == Metashape.Camera.Type.Regular:
continue
if not camera.reference.location:
continue
if not camera.reference.rotation:
continue

pos = crs.unproject(camera.reference.location)
m = crs.localframe(pos)
rot = Metashape.utils.opk2mat(camera.reference.rotation) * Metashape.Matrix().Diag([1, -1, -1])
R = Metashape.Matrix().Translation(pos) * Metashape.Matrix().Rotation(m.rotation().t() * rot)

if not origin:
origin = pos
chunk.transform.matrix = Metashape.Matrix().Translation(origin)
T = chunk.transform.matrix

camera.transform = T.inv() * R
chunk.updateTransform()

The problem is, since I moved from 1.7.3 to 1.7.4, this script don't works any longer.

Is there any change in the way to script python commands ?

5

Bug Reports / XML Blocks Exchange import issue

« on: January 05, 2021, 02:25:27 PM »

Hey !

I'd like to import cameras positions and calibrations data produced by ContextCapture so I managed to get an XML Blocks Exchange file as well as the concerned cameras. I precise that I've loaded NGF-IGN69 geoid model (EPSG::5119) which is used as coordinate system in my project.

As an example, here is a part of the XML Blocks Exchange :

Code: [Select]

        <Photo>
          <Id>55610</Id>
          <ImagePath>D:/IMAGES/Left/09_137_124824_203_Left.jpg</ImagePath>
          <Component>1</Component>
          <Pose>
            <Rotation>
              <Omega>-44.2294659638294</Omega>
              <Phi>-8.98957986763937</Phi>
              <Kappa>-81.0641551920933</Kappa>
              <Accurate>true</Accurate>
            </Rotation>
            <Center>
              <x>705884.750718091</x>
              <y>7061439.17630715</y>
              <z>773.699714511843</z>
              <Accurate>true</Accurate>
            </Center>
            <Metadata>
              <SRSId>0</SRSId>
              <Rotation>
                <Omega>135.77379</Omega>
                <Phi>8.97211999999996</Phi>
                <Kappa>81.04876</Kappa>
                <Accurate>true</Accurate>
              </Rotation>
              <Center>
                <x>505872.457</x>
                <y>5610891.335</y>
                <z>773.346</z>
                <Accurate>true</Accurate>
              </Center>
            </Metadata>
          </Pose>
          <NearDepth>587.593386139714</NearDepth>
          <MedianDepth>1131.75971060136</MedianDepth>
          <FarDepth>1382.12451767816</FarDepth>
          <ExifData />
Here is now the export of the estimated view reference pan of Metashape after importing XML :

Code: [Select]

09_137_124824_203_Left.jpg
x : 705884.750718
y : 7061439.176307
z : 817.664289
omega : -179.987093
phi : 0.012384
kappa : 0.000929
Regarding planimetrics data, the three lasts decimals are skipped, which is right.
The altimetric value seems to be modified, it passes from around 773 to 817m. Omega, phi and kappa data are also modified. Basically, cameras orientations are inverted upward instead of being downward (see attachment).
Cameras calibrations groups (obliques and nadirs) are also skipped.
For further investigations, I could also attached the XML concerned.

Could you precise how data are converted from the XML Blocks Exchange to the Metashape so I could figure if the issue comes from natives data, transformations applied, or my workflow.

Thanx by advance.

6

Agisoft Viewer / Adding logo on Agisoft Viewer

« on: August 07, 2020, 11:33:20 AM »

Hey there,

As public institution we are can give freely access to some datas under certain circonstances. In the case I'm talking about, it is a 3dtiles of an entiere village. The only thing we ask for is that the name of our institution is quoted.
Because we'll like to use Agisoft Viewer to share those datas, is there a way to add a logo on the Agisoft Viewer ?

Cheers
GGR

7

General / adding accurary, resolution etc in batched exports

« on: February 26, 2020, 04:43:00 PM »

Hi everyone,

Because time has come for me to think about storing rationally the different projects I do, I'm wondering if it's possible to add extra informations to the titles of the exports.

Like the commands {chunklabel} or {projectname} allows to export specific datas, is there something like this about the accuracy, resolution, number of vertices and so on ? I use the batch process from the interface, but someday I'll have to learn how to pyhton scripting, so if you know how to script this I'm interested in.

If anyone have any idea... Thank you for your time.
Gabriel

8

Feature Requests / exporting point cloud filtered by confidence

« on: February 19, 2020, 05:21:40 PM »

Hello everyone,

First of all I'm really glad to have discovered the possibility to calculate the point confidence of a point cloud. This is really great improvement in Metashape, it makes its products more reliable !

Now my question is, is there a way to export the filtered dense cloud from the interface ?

Thanks by advance !

9

General / Lowpoly/Highpoly, looking for cage process

« on: December 03, 2019, 04:59:37 PM »

Hello community,

Because everyone is not fitted as people dealing with hundreds of pictures, I'm trying to make my meshes lighter.

I noticed that it is possible to build virtuals cages around a lowpoly based on the normals of a highpoly so a high quality texture can fit on a lowpoly mesh.

I tryed with AM Pro 1.6.0 (build 9487) to generate normal maps from an highpoly and "bake" it on a lowpoly (decimated with the dedicated tool in AM Pro). It worked so I pushed on and imported the texture built on the highpoly but the result had been kind of an awefull patchwork. So basically I failed cause the normal map did not suit with the lowpoly mesh. I also tryed generate different normal maps with various mapping mode such as "keep uv" etc but without any kind of results.

I read that specifics paid softs can do so, but I'm wondering if anyone tryed and managed to do the same thing on AM.
If someone could share some of the processes that he use it would be most greatfull !

10

General / .path encoding files

« on: October 15, 2019, 02:53:09 PM »

Hello everyone,

Does anyone know to which value refere the four last columns of an export in .path format ? As attachement, you'll find a example of my auto-generated track (I kept the 10 firsts entries).

Is it kind of a translation of the yaw/pitch/roll or kappa/phi/omega format ? And if it is, do you know the way to convert those values ?

Thanks by advance
Gabriel

11

Bug Reports / FBX generating issue

« on: September 26, 2019, 02:48:05 PM »

Hey there !
I'm using a 1.5.4 Metashape professionnal version and I try to generate meshes in fbx format in order to be opened with AutoCAD 2018 (v. O.49.0.0).

My export settings are, local coordinates, no shifting. No cameras, neither markers or normals. Textures in jpeg and the raster encoded in binary encoding.
Because I tryed to open the generated file on CloudCompare or Blender and it worked fine, I wonder if the issue can from Metashape or AutoCAD.

I anyone had a similar problem ?