Agisoft PhotoScan 1.2.0 pre-release

[Airgo]

Hello,
if I convert the initial coordinate system (WGS84) to DHDN,Gauss-Krüger, Zone4 and export calculated contours to shape files the projection of the shape file is still the initial coordinate system (WGS84).
Best regards,
Mathias

[Alexey Pasumansky]

Hello Mathias,

Have you generated DEM and contours after coordinate system transformation do before it?

[Pascal]

Hi Alexey,
ooopps, sorry, thank you for your help.
Regards.
Pascal

[Airgo]

Hello Alexey,
seems that I did not recalculate the DEM, just the contours.
If I recalculate both of them coordinates are right.
Sorry for inconvenience,
Mathias

[Mohammed]

Hi Agisoft Team,

I build Spares point cloud for interior scene and build the Mesh from Sparse then i tried to build the orthomosaic but it give me an Error: Zero resolution unlike the previous version?
Thanks
Mohamed

[Mark Florquin]

Hello,

I've noticed extra options for the import mask from background function. I'm using a greenkey background for scanning people.

When I import masks from background, I get inverted or incorrect masks sometimes. This usually happens if a person wears blue or red.

Tried all the new options available (union, difference,...) but none seem to mask correctly.

My workflow now is to generate masks in photoshop, deleting the green after selecting by color, then  making an alpha.

Ideally, I'm looking for an option for masking by color in photoscan. Is this a good idea? Or can the current "mask by background" function be revised so it works reliable all the time?

Thanks for looking into this!

Mark

[Alexey Pasumansky]

If I want to export an orthophoto in older version the pixel size was automaticaly estimated. Now in version 1.2 If I want to build an orthophoto the pixel size is zero in any case.

Hello Jakub,

We were able to reproduce this problem and it will be fixed in the next update.

[Alexey Pasumansky]

I build Spares point cloud for interior scene and build the Mesh from Sparse then i tried to build the orthomosaic but it give me an Error: Zero resolution unlike the previous version?

Hello Mohamed,

As mentioned above, we've found the problem and will fix it shortly.

[bisenberger]

The Interpolation option in the Build DEM window only has the Enabled (default) option when Mesh is selected as the Source data.

For the mesh I wanted to use to create the DEM I had used the Dense cloud option for the Source data, Disabled for the Interpolation option, and Ground for the Point classes. This left holes in the mesh. I ran Smooth Mesh on the result and wanted to test the DEM creation with the smoothed mesh. Since Build DEM only has Enabled for the Interpolation option, the holes in the mesh were filled in the resulting DEM.

[bisenberger]

When right clicking Orthomosaic in Workspace and selecting Export Orthophotos selected photos become unselected.

It works as expected when selecting  from Tools>Export>Export Orthophotos... pulldown.

[bisenberger]

Can the color representation of the DEM be exported as an image for use in a GIS?

[jl]

Hi, I'm hoping you can help me with the vertical datums feature, which will be a huge help.  I have a project referenced in WGS84 Lat/Lng and meters HAE, and would like to export it ideally in a state plane with NAVD88 feet.

I see that when I use the 'Convert' button in the reference pane, and pick the WGS84 + EGM96 geoid height, the z values all change to reasonable geoid heights in meters.  The value of "chunk.crs.wkt" changes to be a COMPD_CS with VERT_CS/VERT_DATUM components that make sense.  However, I can't seem to build my own PhotoScan.CoordinateSystem object with a vertical datum component.  Even trying to create a new CoordinateSystem with the WKT that was chosen automatically fails (with a non-pythonish error in the binding):

Code: [Select]

>>> PhotoScan.CoordinateSystem(PhotoScan.app.document.chunk.crs.wkt)
Traceback (most recent call last):
  File "<console>", line 1, in <module>
SystemError: NULL result without error in PyObject_Call

What I would ideally like to do is build a CoordinateSystem with something like the following, to get state plane data in US Survey Foot units in all three axes, and use it with chunk.exportDem.

Code: [Select]

COMPD_CS["California zone 4 NAVD88 ftUS",
  PROJCS["NAD83(NSRS2007) / California zone 4 (ftUS)",
    GEOGCS["NAD83(NSRS2007)",
        DATUM["NAD83_National_Spatial_Reference_System_2007",
            SPHEROID["GRS 1980",6378137,298.257222101,
                AUTHORITY["EPSG","7019"]],
            TOWGS84[0,0,0,0,0,0,0],
            AUTHORITY["EPSG","6759"]],
        PRIMEM["Greenwich",0,
            AUTHORITY["EPSG","8901"]],
        UNIT["degree",0.01745329251994328,
            AUTHORITY["EPSG","9122"]],
        AUTHORITY["EPSG","4759"]],
    UNIT["US survey foot",0.3048006096012192,
        AUTHORITY["EPSG","9003"]],
    PROJECTION["Lambert_Conformal_Conic_2SP"],
    PARAMETER["standard_parallel_1",37.25],
    PARAMETER["standard_parallel_2",36],
    PARAMETER["latitude_of_origin",35.33333333333334],
    PARAMETER["central_meridian",-119],
    PARAMETER["false_easting",6561666.667],
    PARAMETER["false_northing",1640416.667],
    AUTHORITY["EPSG","3496"],
    AXIS["X",EAST],
    AXIS["Y",NORTH]],
  VERT_CS["EGM96 geoid height",
    VERT_DATUM["EGM96 geoid",2005,
      AUTHORITY["EPSG","5171"]],
    UNIT["US survey foot",0.3048006096012192,
        AUTHORITY["EPSG","9003"]],
    AUTHORITY["EPSG","5773"]]
]

Thanks,
John

[Airgo]

Hello,
did you change the way the sparse cloud (align photos) is computed.
I achieved better results (less misaligned photos) with 1.1.6 than in 1.2.
Regards,
Mathias

[Mohammed]

Hello,

I Align camera using another software then export Camera position as Bundler V0.3 it worked fine with PS V1.6 but it doesn't work with new Version it give me error in consel pan?

Thanks,,

[pastouf]

What is difference between DEM from Dense Cloud or Mesh???

It's only saved time?