Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - toxicmag

Pages: [1] 2 3 ... 6
1
Hello guys  :)

i'd like to create a mesh (mainly along sidewalk and road surface) while forcing the triangle creation to stick to pre-defined breaklines.

I really would like to do this in Metashape directly, but there doesn't seem to be a way to include breaklines into the meshing process.
And even if it would work in Metashape another issue comes the "rounded edges" "photogrammetric curve"

Two questions related to this:

1) Do you know any improvements of Metashape with regard to this?
2) Do you have any recommendations for any other workflow?

Thanks a lot, guys.

Alex

2
Me neither, Limpopo_River...
I see no different behaviour in the selection - whatever i choose.

Did you find out by now?

Greetings

Alex

3
General / Re: Area calculation - Only getting perimeter measure
« on: April 16, 2021, 03:25:09 PM »
Thanks Alexey, thanks Paulo, thanks ALL...   :)

Once again this forum shows us why Agisoft is the company to go with.
Great developers, great users, open for code/console orders/scripts...

Nice one - looking forward to try out.

:)


Have a good weekend and stay healthy!

Alex

4
General / Re: Area calculation - Only getting perimeter measure
« on: April 15, 2021, 08:54:36 AM »
... switch the type of the polygonal shape to Outer Boundary...

Hi Alexey,

currently the only option to switch that type to "outer boundary" is in DEM or Ortho, not in other views.
So one needs to generate a DEM and or Ortho first, even though it's not necessary.

Maybe an idea to create a ticket for the developers to implement this menu item in model view?

Greetings

Alex

5
General / Re: Area calculation - Only getting perimeter measure
« on: April 14, 2021, 07:16:26 PM »
Hey Alexey,

thanks for this workaround   :)

To clip a mesh with the help of a polygon is a question we were considering right before i wrote.   :)

Anyway - if someone knows a more straight forward way (even though it might be outside Metashape) i would be very happy to try it.


6
General / Re: Area calculation - Only getting perimeter measure
« on: April 14, 2021, 06:11:47 PM »
Hey Metashape friends,

are there any news here?

What are your smart procedures to fulfill this kind of task?
The easier the better - to also maybe have the client measure his areas himself.

Tried a lot already:

+ Metashape (and Viewer) itself (via Pointclouds, Meshes, DEMs)
+ Cloudcompare
+ Potree (would be ok)
+ Meshlab
+ exported 3D PDFs (would be awesome)

None of these options works in an easy way.

Sure, tools like Pix4D cloud, oder ArcGIS Pro can easily do it. Also QGIS can be used for it...
But nothing "simple" to give to the client yet.

What are your latest ideas on that?

Cheers and thx in advance

Alex

7
Hi Alexey,

i just checked the "tiled" file option and it worked.     :)

I'd like to search later what this option does, because the funny thing is that the console said: generating 67339x47398 raster in 1x1 tiles.
So after all it still is just 1 tile (file is ~2.2GB) and it doesn't mean to get several tiles like when you use the split option in many tiles.

THX a lot Alexey!

 :D

8
Hello Alexey,

expected filesize will just crack the 2GB border.
Selecting "write BigTIFF file" does not help.

LZW files end up at 4GB

2021-03-30 13:46:05 ExportOrthomosaic: image_format = TIFF, path = E:/2021-03-16_XXXXXX/2021-03-30_Ortho_1.31cm_JPG97.tif, projection = Planar, resolution_x = 0.013170599999999999, resolution_y = 0.013170599999999999, save_alpha = off, save_world = on
2021-03-30 13:46:05 Exporting orthomosaic...
2021-03-30 13:46:05 generating 67339 x 49492 raster in 1 x 1 tiles
2021-03-30 13:46:07 libtiff error: Strip/tile too large for JPEG
2021-03-30 13:46:07 Finished processing in 2.037 sec (exit code 0)
2021-03-30 13:46:07 Error: TIFFWriteScanline: unexpected error: E:/2021-03-16_XXXXXXXX/2021-03-30_Ortho_1.31cm_JPG97.tif
>>>

9
Dear Support-Team,

export of an Orthomosaic just gave me the following feedback (s. screenshot attached).

I changed some parameters and it seems to be only buggy when exporting into default GSD given by the entire project itself and JPG.

summary:
#  JPG compression does NOT work at default (native) GSD (here: 1.31cm/px)
#  If i change the GSD values just slightly the export works fine
#  LZW compression works
#  JPG works at all other GSDs

10
Bug Reports / Re: Fails to import pointclouds from ReCap
« on: March 26, 2021, 07:05:26 PM »
Any news on that? 

Having the same issue with LAS (and LAZ) coming from Cloudcompare. Tried exports of standard LAS/LAZ format in CloudCompare and also version 1.3 / 1.4.
Metashape 1.7.2 (12070) 64bit version is crashing instantly not even showing the import dialogue (choose CRS etc.). It happens also in version 1.7.0 build 11637.

Checked on two devices (Desktop 32 core AMD Ryzen; 128GB RAM; Notebook i7 with 64GB RAM) and always the same crashes.

BTW: E57 of exactly the same pointcloud works fine.

Would be great to get this done.


11
General / include breaklines (polylines) in meshing process
« on: March 24, 2021, 09:44:46 AM »
Hello guys  :)

i'd like to create a mesh (mainly along sidewalk and road surface) while forcing the triangle creation to stick to pre-defined breaklines.

I really would like to do this in Metashape directly, but there doesn't seem to be a way to include breaklines into the meshing process.
And even if it would work in Metashape another issue comes the "rounded edges" "photogrammetric curve"

Two questions related to this:

1) Do you know any improvements of Metashape with regard to this?
2) Do you have any recommendations for any other workflow?

Thanks a lot, guys.

Alex

12
SOLVED:

It's mandatory to keep all folders of each camera as they are (including the folders with calibration images).

Then all data needs to be copied to a single main folder.

Add this folder into Metashape => "add folder" in Multicamera option.

13
General / Re: Dual RedEdge (Red & Blue) // Band interpretation by Metashape
« on: February 28, 2020, 04:28:44 PM »
Hi Alexey<

it's my own dataset and i can share it with you. Or better just some outtakes because of the data size.

I'm gonna write to you directly, Alexey.

Greetings

Alex


14
Hi Metashapers,

when importing 10 bands of the RedEdge-MX Dual Camera System the proposed workflow of Micasense works quite well.
https://support.micasense.com/hc/en-us/articles/360002693373-Process-MicaSense-sensor-data-in-Agisoft-Metashape

When i toggle through the bands i see that the bands are sorted differently than the naming of Micasense. Quite confusing... And after reflectance calibration (with panel and sun sensor) it even gets more strange.

What is the proper workflow to deal with it in Metashape?
Is there a quick guide or something similar available? I didn't find any hint towards this topic.

Thanks already now.

Alex

15
General / Re: Classify Ground Points Settings
« on: January 05, 2020, 05:57:45 PM »
Also you can try the ClassifyPoints operation and enable all the available classes and compare the classification results to the Ground Points classification.

Dear Alexey,

what about this feature request (maybe it's already possible but i do not see it)   => 

For the Ground Classification Tool you always define a FROM-class and a TO-class. What about adding "selection" into the FROM-class pulldown menue and let the classification only take part within the selected points? It'll help a lot in manual classification work. As of today the process always runs through the whole densecloud. Even if you do a "manual fake definition" (like i.e. rails) for a small area and work the ground classification process then FROM "rails" to "ground points" it goes through the whole dataset and takes too long.

Pages: [1] 2 3 ... 6