Agisoft Metashape
Agisoft Metashape => General => Topic started by: Dmitry Semyonov on August 06, 2015, 09:50:50 PM
-
Pre-release version of Agisoft PhotoScan 1.2.0 is available for download.
This pre-release is considered as unstable and is not recommended for production use.
Please let us know if you have any problems using this version.
Please post problems and/or questions concerning other PhotoScan version in separate topics.
This topic will be removed when the final 1.2.0 version is released.
Note
Project files created with 1.2.0 version can't be opened with earlier versions.
EDIT:
PhotoScan 1.2.0 build 2198 was finally released. Thank you for useful feedback.
Please use the links on the main PhotoScan page for download:
Download Installers (http://www.agisoft.com/downloads/installer/)
-
• Added Invert Selection command for cameras.
Hallelujah!
Thank you.
-
• Added Smooth Model command.
Wow! How does your implementation work? is it just Gaussian based? Bilateral?
Great news!
-
Could you walk us through how orthomosaic seam line editing works?
THanks
-
Hello mwillis,
The procedure can be briefly described as follows:
- after building the orthomosaics open it in the Ortho tab by double-clicking on the corresponding line in the Workspace pane,
- choose Draw Polygon instrument on the toolbar,
- draw a polygon,
- select polygon with the left-click then right-click on it and choose Assign Images in the context menu,
- specify the image (or images) to be used for the current fragment,
- repeat previous steps any times you wish on different areas,
- when all the changes have been made press Update Orthomosaic button on the toolbar to apply the changes (it will take some time).
-
Hello Mfranquelo,
This feature uses Laplacian smoothing.
-
Hello,
great work Agisoft Team, a milestone for Photoscan!!!
I have noticed that theres is a problem with Export orthophotos (Tools --> Export --> Export Orthophotos). This function causes Photoscan crash.
One question regarding to seamline editing:
If I choose one Photo to assign to created polygon, some small areas are not covered (white gaps) even if the choosen photo contains texture informations of these gaps.
Thanks a lot!
Paul
-
Hello Paul,
Could you please provide the screenshots of the Build Orthomosaic and Export Orthomosaic windows with the parameters used? As we cannot reproduce the issue.
Maybe you can also make a screenshot of the image assignment for the polygon area and of the image used itself?
-
I suppose that the holes in the images available for the editing of the seam line come from missing 3D information when orthoretificating of the original photos. Or am I just writing nonsense?
Well, nevertheless, with this new feature, PS will really became unbeatable!!!!!
-
Hello Alexey,
please find the attached the situation that caused a crash. Note that all input images are geotagged (Orthomosaic is rectyfied and scaled +-10m).
-
Please find attached the white gaps during seam line editing.
I have noticed that this happens only in noisy regions where terrain normals dont seem to match with image orientation.
@ Patribus: The used model is watertight closed, no gaps.
Thanks
Paul
-
Hi alexey,
about the seamlines photos, they are only in orthogonal projection, so, if you got a bad building geometry, all photos are with artifacts due to projection. Can add a option to choose a planar projection?
Thanks
-
Paul, yes, i know,
I do also see these white features, but always where there are 'problems', e.g. 1. a tree appears in the image, but is not described in/by the model, 2. features in water, which lead to very noise point cloud/model 3. dark regions in the images (shadow, for instance), etc. At it seems, the regions of images which cannot be assigned to a region in the model - be it because that region in the image is bad, or because the model is bad or missing for the respective region, PS creates a hole in the image.
This seems to be consistent with my observation.
@Paul, in your model the dark zones correspond exactly to the problem region.
If you want, i can give you examples of one map I did.
Cheers
-
Is it jsut me or is the import a mesh with UVS dropping the UVs?
Ive imported a few obj with UV and it wont show them in the mesh menu, and also generating texture (keep UV) produces no result
-P
-
Maybe Bilateral would've been better! Although whats important is to take the first step! Well done! It was a feature hugely requested. As a suggestion I find the laplacian filter to be "too strong" even just applying one pass.
I've been playing with the new version at it seems like the project file gets corrupted very easily... I've sent a few times the error report. I keep trying to open the project file but it keeps crashing before opening the model. It wasnt corrupted until the last stage of exporting the model.
Best.
-
I've been playing with the new version at it seems like the project file gets corrupted very easily...
I feel the same.
-
I have noticed that theres is a problem with Export orthophotos (Tools --> Export --> Export Orthophotos). This function causes Photoscan crash.
I feel the same.
-
Orthophotos export and Keep UV options will be fixed in the next pre-release update.
-
Hello Mfranquelo,
Could you please send the corrupted project to us to support@agisoft.com? (if it's psx, than also the associated .files folder)
-
Orthophotos export and Keep UV options will be fixed in the next pre-release update.
Hiya
Do you have a time estimate for the next release with the keep UV option?
Need to work out if worth waiting or reinstalling older version and re-running
Cheers!
-P
-
Great! Yes it is a .psx file with the filename.files
I've sent them via WeTransfer (it'll take about 3 hours though, my uploading speed is crap...) :-[
I've also noticed that after optimizing the sparse point cloud the pixel accuracy seems to have way lower number than before on the new version. Has something changed ? Texture blending time also seems to take more... Maybe it is just this project, I could try with older ones.
-
Laplacian looks promising! As I've observed its strength is dependant on the number of polygons?
Best,
Manuel.
-
Hello Mfranquelo,
According to the project data orthomosaic should be present in the workspace, but there are no corresponding files in the folder. So could you please describe your workfow starting from the orthomosaic generation?
-
I might have deleted that file.
I was playing with different outputs like orthomosaic, a feature I've never used in head scans.
-
Hello Mfranquelo,
Do you mean that you have removed some data from .files folder? Recommended workflow suggests removing elements from the project via Workspace pane in PhotoScan GUI. Altering project data manually from the file browser may lead to the unexpected problems.
-
I might... can't really remember since I was testing. If I removed something I am sure it is output files. Is it possible to change some kind of .xml so it doesnt read the orthomosaic data? I was wondering if the project must be started from scratch or rescued.
Any notes on the pixel accuracy values (reference tab) or why the blending process in texture generation is taking so long now?
Thank you for the changes! Agisoft really feels like a vivid creature evolving :)
-
Hello Mfranquelo,
You can remove orthomosaic line in the doc.xml file inside frame.zip file. Hope it helps.
Texture generation time shouldn't be different from the previous version with the same parameters. Are you sure that Color Correction option is not turned on?
-
I noticed that in the Align Photo step an increase of highest and lowest,But there is no such option in the Batch Process tool. And I want to know what does highest/lowest mean?
Another question is new version of the save project is the default psx format, I want to know when I run the python script in the new version, whether the use of distributed processing?
-
Is there any step of the use of GPU in the new version?
-
Great it works now :-) (I've removed that line)
Colour correction is not enabled, however it is a different project. It is very similar to the rest I was working on and the difference on the "blending" process was pretty high. I'll test the same file with 1.1.6 and 1.2 and report back.
Thank you!
-
Hello pjenness,
I think the next 1.2 update will be published this week.
-
Hello ppkong,
Highest and lowest options will be available in other related dialogues in the next 1.2 update.
Lowest is just one step below the current Low option (meaning downscaling of the original photos by eight times by each side), whereas Highest option uses upscaled images by factor two.
GPU processing is not used on any other steps except Depth Maps Estimation, and Python scripts do not support network processing.
PSX is default format for PhotoScan Professional, as it is required for DEM/Orthomosaic/Tiled Model generation and also for distributed processing.
-
Great stuff! Two questions; first, is it possible to export the drawn polygons with Z-value? Second, is it possible to cut the DEM before making the contours as to not get the "bad" edges included in the contours/DEM?
-
Hi Agisoft,
great work on new release!
Now in the Point Cloud Parameters appears
Point Cloud
Points 107,829 of 108,104
RMS reprojection error 0.188834 (0.938147 pix)
Max reprojection error 3.31482 (8.29758 pix)
Mean key point size 4.95552 pix
Effective overlap 2.619
What are the meaning of values in parenthesis for RMS reprojection error and Max reprojection error relative to first value?
And what does mean key point size represent?
Thanks in advance,
-
New export Orthophotos option is very exciting! (Way better and faster than my flakey python script!)
Could there be an option to export each orthophoto with the same full dimensions of the entire orthomosaic?
Currently each orthophoto has its own region boundaries, to make the smallest image dimensions.
It would mean that each orthophoto had a lot of empty space, but also that they could be so easily stacked in layers in photoshop using "load files into stack" for manual blending and colour correction.
Otherwise photoshop just aligns them all by top left corner which isn't so useful.
-
Hi Agisoft,
great work on new release!
Now in the Point Cloud Parameters appears
Point Cloud
Points 107,829 of 108,104
RMS reprojection error 0.188834 (0.938147 pix)
Max reprojection error 3.31482 (8.29758 pix)
Mean key point size 4.95552 pix
Effective overlap 2.619
What are the meaning of values in parenthesis for RMS reprojection error and Max reprojection error relative to first value?
And what does mean key point size represent?
Thanks in advance,
Hello pap1956,
PhotoScan matches images on different scales to improve robustness with blurred or difficult to match images. The accuracy of tie point projections depends on the scale at which they were located. PhotoScan 1.2 uses information about scale to weight tie point reprojection errors.
In the Reference pane settings dialog tie point accuracy parameter now corresponds to normalized accuracy - i.e. accuracy of tie point detected at the scale equal to 1. Tie points detected on other scales will have accuracy proportional to their scales. This helps to obtain more accurate bundle adjustment results.
In the chunk information dialog two reprojection errors are provided: the reprojection error in the units of tie point scale (this is the quantity that is minimized during bundle adjustment), and the old style reprojection error in pixels (for convenience).
The mean key point size value is a mean tie point scale averaged across all projections.
-
Thank you for the explanation,
now if we want to have the RMS reprojection error in ground units ( in this case meters) what do we have to do?
-
It seems like "camera type" in the camera calibration dialog is not being saved in 1.2.
i made a project with fisheye lens and placed several markers. then saved and reloaded the project. the markers were all offset from their original position (in the 3d view), and the camera type had reverted back to 'frame'.
-
+ 1 also found this problem with a previous project done and saved with Fisheye model. When I save in new release and open again, camera model changes to Frame....
-
Very nice work by PS team. I created DEM and then orthomosaic. It always makes the DEM from top. How can use coordinates of markes for XY plane. I want to make orthophots of the building sides and not roof.
-
Hello,
Thanks for reporting on the camera type issue, we'll check it and fix as soon as possible.
To generate orthomosaic in planar projection it is still necessary to reconstruct mesh, based on DEM only geographic projection is possible (since there's no information about vertical surfaces in DEM).
-
Hello
We are using network computation with 3 computers... But whenever we want to connect the 3rd computer this message shows up:
registration failed: Key rejected
Is it possible that we have used the same key twice for our installations?
-
Hello r0xx,
Each node/server instance of PhotoScan in the network should be activated with the separate license key.
-
hi alexey, sorry, "projection" isn`t the word. I refer to use photos without orthorectification (original photos) over the mesh to avoid malformations... but this on the orthomosaic editing feature (assign images) like pix4d.
-
Great work guys! I can't believe now I can see the elevation inside the program. No need to export it to Global Mapper. The Contours generation are also welcome. It would be a dream come true for more volume calculation methods like for example defining the elevation of the plane.
-
From what I have seen so far ortomosaic done via DEM has region with images that are not aligned correctly, If I choose mesh the result is an orto with a little tilt as seen in the image "XY". The projection chosen is not planar is Stereo 70. Do I have to choose other settings?
The camera location page in the report has the weird error.
I have uploaded the alignment error JPG done with DEM. If I choose mesh instead of DEM I get good alignment but the projection is tilted.
-
Hello gheflorian,
Such errors in the report usually indicate that relation between camera labels and position coordinates is incorrect.
-
now that I am looking closely even the DEM is not perfectly orthogonal. Am I missing something?
-
Hello gheflorian,
In case the georeferencing is incorrect, DEM and mesh will be also tilted relatively to the coordinate system axis.
-
I didn't yet try to georef. the project. I just inserted the photos and log file from the flight. In previous versions I didn't have to georef in order to extract a good ortho.
-
Hello!
will there be Python API support for network processing in this version?
-
Hello gheflorian,
In case the georeferencing is incorrect, DEM and mesh will be also tilted relatively to the coordinate system axis.
There was something odd with the project because I'm running Win 10 and Photoscan did not run with Admin mode. Now everything seems fine after realignment.
So now we can basically make a quick DEM and generate orthophoto without the need to make dense point cloud. That saves a lot of time. Almost 8 hours for those that need only that. Great job!
-
will there be Python API support for network processing in this version?
Hello sc,
Unfortunately, version 1.2 wouldn't support Network processing via Python API.
-
Hello!
I can't seem to duplicate chunks in this release (Standard edition).
I've tried with old projects and making new ones and it just immediatly returns an error saying "Can't duplicate chunk" (no
particular error info in console just "Finished processing in 0 sec (exit code 0)")
I have also tried re-installing but still the same error.
Anyone else had this problem?
Best, Magnus.
-
Hello!
Great new version :)
Is there any available tutorial for the new features and workflow in version 1.2.0 ?
Thanks
-
Hello Magnus,
It's a knows issue, unfortunately, but will be fixed in the next pre-release update.
-
Hi,
Well done with this release there are some welcome updates!
I've tried the seamlines editor and it worked great.
I'm very interested and looking forward to the updated manuals so we can understand the changes and how they work.
I've run a couple of test projects and noticed differences with the number of matched point and camera calibrations. Has there been a change in the processing methods?
-
Hallo
I Try to upload some data to mapbox.
Now every time apears the error attached.
I think its cose of the API token. Can anyone tell me which API is required?
I tried both (privat and public) and it don't work.
Thanks in advance
-
Hello r0xx,
Each node/server instance of PhotoScan in the network should be activated with the separate license key.
We deactivated the license on this computer and checked the keys again. After we changed it, it works fine. Thanks!
-
Hello ristag,
For Mapbox upload you need to create a new secret token with uploads:write scope. None of default tokens have sufficient permissions.
-
Hello ARF,
PhotoScan 1.2 includes some changes in image alignment algorithms for improved accuracy. Please see this post for some details:
http://www.agisoft.com/forum/index.php?topic=4149.msg21391#msg21391 (http://www.agisoft.com/forum/index.php?topic=4149.msg21391#msg21391)
-
The new mesh smoothing function seems to please many users. Would it be very complicated to apply the same algorithm to dense clouds ?
-
Hi Thank you for tyhis gr8 update!
When i tried to duplicate Chunk it crash? plz try to fix it.
Thanks,,
Mohammed
-
Hello nadar,
Smoothing feature for dense cloud wouldn't be included in the version 1.2.
-
Hello Mohammed,
Please check that you are using latest build of the version 1.2. If so and there are any problems with duplicating, please describe how it could be reproduced.
-
Hi Alexey,
I just wanted to tell you how happy I am with version 1.2. It work brilliantly and it's so incredibly fast!!
-
Hello nadar,
Smoothing feature for dense cloud wouldn't be included in the version 1.2.
Could you please give some explanation on how mesh smoothing is implemented . Does it analyse the 3D position of each planar facet, or doest it smooth the position of the points defining the corners of each face ?
-
It is a laplacian based implementation nadar, you can have a look at it in google :-)
-
Is it possible to have both versions 1.1 and 1.2 installed?
-
It is a laplacian based implementation nadar, you can have a look at it in google :-)
I know what a Laplacian filter is in 2D raster image processing. I assume for a 3D grid , it will use a 3x3x3 kernel or something like this. I deon't understand how it works on a irregularly spaced dataset such as a point cloud. If you have good references...
-
Trying to generate an orthophoto in this release is giving me trouble... In previous versions, after generating a mesh I could export an orthophoto in pieces. now you must first generate an orthophoto within photoscan and it does not allow to generate it in multiple pieces... It keeps running out of memory now, and I am quite stuck.
Maybe I am missing something.
I am running 128gb of ram and upon monitoring the usage it looks like it didnt go beyong 50% of Ram usage.
The Chunk is roughly 6800 photos and is quite large but I have tried Chopping the chunk down with no luck...
Also, I have just upgraded to windows 10 which may have been a bad idea as now while processing in photoscan, the computer grinds to a near halt and cannot do much else at the same time.
Any help would be greatly appreciated.
-
_________Saving raw orthphoto__________________________
I 'm making 50 orthophotos using PSv1.2 . I can save only one raw orthophorto per chank. I wan to have all raw orhotophotos saved, so that I can edit the required area and again export it. How can I do it. At the moment I'm making one project per orthotophoto which is not economical.
-
Hello Ingsayyad,
Are you using Export Orthophotos option? Is so we suggest to use filename templates, like {filename}.{fileext}
-
I can export all images in the format you mentioned. But how can I have use these images for the next time to make my orthophoto. Is there any option of importing orthophoto and editing it in Photoscan.
-
Hello SuperNewb,
In the version 1.2 orthomosaic is not kept as a single piece. However, each orthopohoto related to the individual cameras are kept as single blocks (are not tiled). So could you please specify whether there are oblique images (probably incorrectly aligned)?
-
Hello Ingsayyad,
Maybe you can describe the workflow you would like to follow, as I don't quite understand what for you need to import orthorectified images back to PhotoScan.
-
Alexey, can you please have a look at the pythonscript split_in_chunks_dialog.py?
It looks like in V 1.2.0 the script does not work...
http://www.agisoft.com/forum/index.php?topic=3783.0
Thanks in advance!
-
@ Alexey Pasumansky
1: I made an orthomosaic A (raw).
2: Now I edit it and made my final orthomosaic A.
3: I can export it (my final orthomosaic A) as jpg etc.
3:Now I made another raw orthomosaic B in the same project/chunk and similarly I exported it too.
4: Now if I have to edit orthomosaic A, I have to produce it again in the project. which make no sense.
5: How can I save orthomosaic A (from step 2). so that I can import it any time in the project to edit it if required.
-
Is it possible to have auto fill function for markers in orthophoto generation. At the moment I 'm typing markers ,require resolution etc. and if I forget some thing etc. I have to type all info again. If there will be last saved info, you can just change them.
-
Hello Ingsayyad,
Thank you for clarification on your workflow.
At the moment we are not planning to implement multiple orthomosaics per chunk, so it seems that the only solution is chunk duplicating to keep several mosaics in the same project. To reduce the space required for the project you can remove depth maps and dense clouds from the copies of the original chunks, leaving only Elevation or Mesh model, depending on the one used for the orthomosaic generation.
-
Is there a possibility to display a DEM and/or contour lines within Photoscan ?
-
Hello nadar,
After building DEM you need to double click on the Elevation line in the Workspace pane. For contour lines display in the opened view please use Show Contours toolbar button.
-
Hello
Some jpeg images do not display in the previsualisation windows (bottom part of the image list in workspace pane). The first images of the list display correctly, but after 10-20, a message "previsualisation not available" is displayed. This is quite annoying, because I usually use this window to find the image I want to use to place a GCP.
The problem was not observed in previous version
-
Hello nadar,
Preview images in the Workspace pane are taken from the thumbnail list in the Photos pane. So you can open Photos pane and wait until all the thumbnails are loaded.
-
Hi Alexey
Thank you very much for this one!
• Added Load Project, Export Cameras, Close Holes and Reset Region commands to Batch Process
dialog.
Much appreciated.
I am following every update and found some significant drop in tie points in your last night build.
I am having harder time to get the quality mesh from the same set of images comparing to the previous builds.
Please check the images below.
1.1.6 build 2038 (https://goo.gl/QS9Au6)
1.2.0 build 2136 (https://goo.gl/Zi6LLZ)
1.2.0 build 2143 (https://goo.gl/okO61V)
There is one more little favour to ask.
In version 1.1.6 build 2038 "Numpad 0" centred the view.
In version 2.0.0 build any "Numpad 0" centres the view but also resets the view.
If that is intentional would it be possible to give back the old "Numpad 0" somewhere like a "." on a Numpad for example.
To be honest it is the matter of choice, therefore in 1.1.6 if I wanted centre my view and reset the view I hit Numpad 0 and Numpad 7 but still had a choice to do one or another.
Looking forward to hear from you.
Regards
Marcin
-
Hello Marcin,
Thank you for reporting.
Are you using the same tie point limit and accuracy values for all the tests?
-
Thank you for a prompt reply.
I can confirm all the settings are the same and tests conducted on the same workstation.
1.1.6 build 2038 (https://goo.gl/e478Xx)
1.2.0 build 2136 (https://goo.gl/VbXrDH)
1.2.0 build 2143 (https://goo.gl/0mj02w)
Regards
Marcin
-
Hello mwillis,
The procedure can be briefly described as follows:
- after building the orthomosaics open it in the Ortho tab by double-clicking on the corresponding line in the Workspace pane,
- choose Draw Polygon instrument on the toolbar,
- draw a polygon,
- select polygon with the left-click then right-click on it and choose Assign Images in the context menu,
- specify the image (or images) to be used for the current fragment,
- repeat previous steps any times you wish on different areas,
- when all the changes have been made press Update Orthomosaic button on the toolbar to apply the changes (it will take some time).
Hello Alexey,
I tried this workflow hoping that roofs will be computed with higher accuracy.
So I marked a roof with the polygon and assigned an image to it where the whole roof is visible.
But the jagged roof edge is still there.
I have attached a screenshot.
Regards,
Mathias
-
With latest release, when I classify Dense point cloud , I get 3 classes (never classified, ground (brown pts) and low points) as normal.
I save project and when I open it and try to build mesh using only ground points, only never classified class is active, all other are greyed out....altough I can see brown points in model view
??
-
Hello Alexey,
I tried this workflow hoping that roofs will be computed with higher accuracy.
So I marked a roof with the polygon and assigned an image to it where the whole roof is visible.
But the jagged roof edge is still there.
I have attached a screenshot.
Regards,
Mathias
yes, is pointless choose photos if all of them are jagged due to orthorectification, we need choose photos WITHOUT orthorectification.
-
Hello Mathias,
Have you used Assign image option? As there are small areas with black borders inside the shape that look like the automatically created seamlines.
-
Hello pap1956,
We will fix that in the next update, thank you for reporting.
-
Hello tutoss,
Such option will be considered for the next updates.
-
thanks Alexey!
-
After several tests, definitely you need the option to import point clouds (*.las), and also the option of importing DEM, is basic and minimum for this new version. In addition for professional users the possibility dataset processing with image position and orientation very precise GNSS/IMU, setting really robust block with error detection and possibility of eliminating erroneous observations by numerical results.
-
Hello mwillis,
The procedure can be briefly described as follows:
- after building the orthomosaics open it in the Ortho tab by double-clicking on the corresponding line in the Workspace pane,
- choose Draw Polygon instrument on the toolbar,
- draw a polygon,
- select polygon with the left-click then right-click on it and choose Assign Images in the context menu,
- specify the image (or images) to be used for the current fragment,
- repeat previous steps any times you wish on different areas,
- when all the changes have been made press Update Orthomosaic button on the toolbar to apply the changes (it will take some time).
Hello Alexey,
I tried this workflow hoping that roofs will be computed with higher accuracy.
So I marked a roof with the polygon and assigned an image to it where the whole roof is visible.
But the jagged roof edge is still there.
I have attached a screenshot.
Regards,
Mathias
For clean roof lines, I first filter the building out of the dense point cloud before meshing and building orthomosaic. This method works well for small houses,sheds, and cars to keep their edges clean.
-
With the Python API and the default of PSX for the new files, I'm having troubles opening a PSX project. Let's say I have a project: "superproject.psx" and in order to open it, I have to open: "superproject.files/project.zip" as opening the .psx results in an completely empty project. Opening the project.zip, making changes, and then saving corrupts the project.
What am I doing wrong??
Thanks!!
-
Dear Neshmi,
Are you using version 1.2 to open PSX file saved in the version 1.2?
-
Yes.
With Python if i do:
doc = PhotoScan.app.document
doc.open("myfile.psx") it will come up completely empty, but doc.open("myfile.files/project.zip") works. However, if I save the project (doc.save()) it will corrupt the archive.
-
Hello neshmi,
Thanks, we'll check that.
-
Thanks! Alexey!
-
After several tests, definitely you need the option to import point clouds (*.las), and also the option of importing DEM,
+ 2
-
Is it possible in the next release, to get an option to "Decimate Mesh" with iterations?
We have made tests with a mesh of 65 mio faces (see attached image 1) and reduce it to 6500 faces (testing for best results with small number of faces).
What we get in the result is, when you decimate the mesh only in one step from 65mio to 6500 it is much more inaccurate (more sloping corners, inaccurate breakelines -> see attached image 2)
We then decimated the mesh with more steps like 65mio -> 32mio -> 16mio -> 8mio...and so on at the end to 6500 (13 steps of decimation). It gets a way better result/ accuracy in corners/ breakelines (see this in attached image 3).
We may dont have to get to 6500 faces, buts it's for now the best test of model accuracy.
Thanks at all for a superb piece of software.
Regards,
Ben.
-
Hello Mathias,
Have you used Assign image option? As there are small areas with black borders inside the shape that look like the automatically created seamlines.
Hello Alexey,
yes I used the Assign image option. The small areas with black borders appeared after the Update Orthomosaic command.
Mathias
-
when i try to batch export orthoimages with the latest 1.2. i always get this error at the process orthoimage step:
2015-09-02 17:00:02 Error: Can't initialize renderer
2015-09-02 17:00:02 Error: Null orthomosaic
attached the batch process
-
In the new Build DEM function, there is the resolution field that appears to be editable but i can't seem to change it. Three questions on this:
1) How is the default value determined? Is it based on dense cloud quality, image resolution, ???
2) Is this supposed to be an editable field?
3) Will there be a smoothing or simplification function for a DEM?
Also, any chance the display of the coordinate information could also appear when in the model tab as it now does in the Ortho tab?? This would be great.
On more thing. Could you add functionality to the new polygon command in the Ortho editor to draw orthogonal lines? Perhaps when you hold the shift key it will snap to orthogonal?? This would be ideal to generate perfectly square or rectangle clip areas of an DEM or Ortho.
Great work on the updates, this version is fantastic so far!
Kevin
-
Hello Kevin,
Build DEM uses max possible effective resolution to generate DEM, it's calculated based on the average effective resolution of the input images and dense cloud quality option used.
Note that in the Export DEM dialog you'll be able to define the export resolution that may be lower than original.
-
when i try to batch export orthoimages with the latest 1.2. i always get this error at the process orthoimage step:
2015-09-02 17:00:02 Error: Can't initialize renderer
2015-09-02 17:00:02 Error: Null orthomosaic
attached the batch process
if i do the orthoimage processing manually im able to export the block via batch.
-
Hello zwnk,
We are checking this issue, thanks for reporting.
-
after switched to process the mesh, instead of the dtm,the batch process runs smooth.
-
Hello Alexej,
what are the shapes supposed for?
I expected them (especially the polylines) for drawing breaklines in the orthofoto. The polyline knows its 3D-Data (in the measure-dialog) but they export as 2D-Polylines in the shape-file.
The contours as well export only 2D.
It would be nice to export them as 3D-Polylines in dxf.
Best regards,
Mathias
-
is there a possibility to toggle between selection mode (rectangle, ellipse, freehand) and navigation mode (arrow). This would made editing much easier. (similar to pressing space bar in Photoshop always toggle to pan mode -very convenient)
-
Hi Alexey
Thank you for the latest update.
It seems the Tie Points are back to normal!
Is it possible to get old 1.1.6 "NumPad 0" behaviour back by any chance as well?
Regards
Marcin
-
Hello Alexey,
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.
It is a bug? Or how can I find out the real pixel size in the project?
Regards,
Jakub
-
is there a possibility to toggle between selection mode (rectangle, ellipse, freehand) and navigation mode (arrow). This would made editing much easier. (similar to pressing space bar in Photoshop always toggle to pan mode -very convenient)
Hello nadar,
Have you tried using Space? It should switch between the navigation mode and the last selected selection instrument.
-
Is it possible to get old 1.1.6 "NumPad 0" behaviour back by any chance as well?
Hello Marcin,
The Reset View feature behavior has been changed to TopXY view, so the hot-key also works in that way.
-
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.
It is a bug? Or how can I find out the real pixel size in the project?
Hello Jakub,
What pre-release build you are using? Could you please check that it's the latest one?
-
I notice That there's a new option in the Gradual Selection it's (Projection Accuracy). could you explain what is it?
and also i dont understand what is Image count do?
Thanks
Mohamed
-
Hello Alexey,
Prof. edition, build 2149 (64 bit). The problem is still visible.
Jakub
-
Is it possible to get old 1.1.6 "NumPad 0" behaviour back by any chance as well?
Hello Marcin,
The Reset View feature behavior has been changed to TopXY view, so the hot-key also works in that way.
Hi Alexey
Can we have an option on The Reset View feature not to change to TopXY please.
As mentioned previously if I wanted to change the view to TopXY, I could press 7 standing for The Predefined Top View.
I do hope you will consider my request positively please.
Regards
Marcin
-
Hello Alexey,
I cannot start a server in the last beta release,
I use the method described in the help files, but
the server window are immediately closed with an 'unrecognised parameter' error message.
may be do you modified the network processing ...
Think you.
Regards.
Pascal
-
Hello Pascal,
Actually you can use the same line like in the version 1.1 to start the server.
-
Prof. edition, build 2149 (64 bit). The problem is still visible.
Hello Jakub,
I can suggest to recalculate the project (build dense cloud, build orthomosaic) instead of using the older version PSX file.
-
Thank you for this quick reply, but the problem appear when I launch the server (using an appropriate shortcut) not a job.
As the server cannot be launched, the nodes cannot connect to it and thus I can't launch a job or connect the monitor .... I think that saving the project in the new format cannot help very much.
thanks.
Pascal
-
Hello Pascal,
And what is the information given in the terminal window after you try to start the server?
-
here is the screenshot of the windows I get (when I launch the shortcut in a shell).
thanks.
Pascal
-
Hello Pascal,
It seems that "C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe" is used twice in the command line.
-
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
-
Hello Mathias,
Have you generated DEM and contours after coordinate system transformation do before it?
-
Hi Alexey,
ooopps, sorry, thank you for your help.
Regards.
Pascal
-
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
-
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
-
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
-
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.
-
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.
-
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.
-
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.
-
Can the color representation of the DEM be exported as an image for use in a GIS?
(http://www.digital-mapping.net/forums/Photoscan/2015/DEM_elev_color.jpg)
-
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):
>>> 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.
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
-
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
-
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,,
-
What is difference between DEM from Dense Cloud or Mesh???
It's only saved time?
-
is there a possibility to toggle between selection mode (rectangle, ellipse, freehand) and navigation mode (arrow). This would made editing much easier. (similar to pressing space bar in Photoshop always toggle to pan mode -very convenient)
Hello nadar,
Have you tried using Space? It should switch between the navigation mode and the last selected selection instrument.
Thanks. Works fine. Will save me loads of time and stress !
-
Hello bisenberger,
We'll check the hole filling issue regarding the DEM genration from mesh.
As for the orthophotos export from the selected cameras, are you sure that selection isn't discarded when you right-click in the Workspace pane?
-
Hi, Alexey Pasumansky
-Could i ask were's Keep Uv option in build texture map?
Thanks,,
Mohamed
-
We'll check the hole filling issue regarding the DEM genration from mesh.
Hi Alexey,
Error build DEM for Mesh
Error: Zero resolution
regards,
Diego
-
As for the orthophotos export from the selected cameras, are you sure that selection isn't discarded when you right-click in the Workspace pane?
Yes, that is when it happens.
-
Hello Alexey,
I tested the last Photoscan release and I experienced some lag (the display freeze during one second every two seconds approximatively) in model and photos display.
This appends only after having opened a mesh model, before doing this all was ok.
This is a little bit annoying in big project when you have to navigate between photos or to do selection in cloud model.
May be you can do something to fix it.
Thanks.
Pascal
-
Hi Alexey,
I notice that while i merge chunks, the Shaded mode disappeared!, and the number of faces is gone!!!!
Is i do some thing wrong?
Thanks
Mohamed
-
Error build DEM for Mesh
Error: Zero resolution
Hello Diego,
Have you checked it after updating to the build 2145? Probably you'll also need to rebuild mesh.
-
Hello Mohamed,
Thank you for reporting.
We'll fix that.
-
Error build DEM for Mesh
Error: Zero resolution
Hello Diego,
Have you checked it after updating to the build 2145? Probably you'll also need to rebuild mesh.
Hi Alexey,
I'm using the latest version 1.2.0 build 2154.
The problem presents the imported mesh, and I can not rebuild the mesh again, because it is a lidar DTM and is edited and ready to orthophoto. in version 1.1.6 orthophoto with mesh works perfect, so the possibility of requesting a function to import the DEM, or at least to define the resolution of the DEM when it is built starting from an imported mesh.
See attached image
Regards,
Diego
-
Hello Diego,
Thanks for mentionning about imported mesh, we'll try to reproduce it and fix as soon as possible.
-
Hello Alexey,
I received one information from your team few months ago (see below). Do you plan to implement it?
"As for the use of external GeoTIFF elevation information for the orthophoto generation, we are working on additional orthophoto related features for the next version release (v. 1.2) and input of the elevation TIFF will be likely implemented there (maybe not in the first pre-release for the version)."
Regards,
Jakub
-
Hi
Lots of nice new features, but on the create report, keep getting only a portion of the models as the ortho on the first page, tried it at differnt settings, ie, xy, top etc, any ideas, maybe me thats missing something
cheers
-
Hello Alexey,
the 'lag' I observed in the model view seems not to be dur to the mesh, it appears also with
a sparse cloud, but not immediately after opening a project just some minutes after ...
I restarted the pc and there is no other heavy programs running.
It appends also on light projects (less than 40 images),it appends also if I move the photoscan's windows (stop moving during 1 sec and move again, this do not append with windows from other programs)
May be do you have an idea?
Thanks.
Pascal
-
so I have loads of white gaps in my ortho, cant work out why, still trying to figure the workflow, any ideas, cheers
-
Alexey,
Would it be possible to implement a shortcut/keybinding to Show/Hide the seamlines in the Orthomosaic editor?
It's kind of tedious having to click it everytime, unless there's a keybinding for it already.
-
Hello,
i have seen that you have now put many geoid models to use in Photoscan Coordinate systems. I have downloaded EGM2008_2.5 geoid file and put into Geoids folder in PhotoScan pro. Now I would like to define a WGS84 + egm2008 geoid height GCS similar to WGS84 + egm96 already present. I exported the WGS84 + egm96 GCS to prj file and edited it to replace egm96 to egm2008 and authorty records for VERT_CS (3855) and VERT_datum (1027). see attached WGS84 + egm2008.prj file.
However when I import this prj into PhotoScan Coordinate System I get error see screen shot....
Can you help on this problem?
Thank you...
PS. when will you put CGVD2013 geoid on download?
-
Hello pap1956,
Thanks for reporting.
Unfortunately, there was a bug related to the incorrect reading of the PRJ file. We'll fix it in the next update.
-
Hello Diego,
Thanks for mentionning about imported mesh, we'll try to reproduce it and fix as soon as possible.
Thanks Alexey, excellent support, now works perfect.
Best regards,
Diego
-
Hello,
in latest relaese 2158, I am generating a report using Current View projection option and I get not Enough memory error....
Generating in TOPXY projection is no problem....
see attached screen capture....
Regards,
-
I noted a minor bug. After building a project that used masked images, I noted that the chunk's "Show Info" listed "Constrain features by mask No". It should read Yes. This results happens on any project with masks.
Thanks for the great work.
-
Hi Alexey,
I notice that while i merge chunks, the Shaded mode disappeared!, and the number of faces is gone!!!!
Is i do some thing wrong?
Thanks
Mohamed
Dear Alexey,
The Problem fixed so the Shaded mode appear and Number of Polygons,
But Unfortunately the problem appear in Dens pointcloud so after i merged two chunks the Number of Dens PCloud is Zero!!
Thanks
Mohamed
-
Hi Alexey,
i have not seen this covered yet so I thought I would ask.
Is there a way to select the mosaic cells that photoscan has generated? It is very tedious to click out a polygon everytime to assign new image projections.
I imagine there is a hotkey somewhere for this but I have missed it.
Thanks
-
Network Processing bug.
Hi,
I've been trying to run a big project with network processing with the beta version (am using build2158)
Nodes manage to connect to the server, but on the server end I get the following in the terminal:
accepted connection from 163.1.22.50:50684
thread started
Error: no workitem
It does let me continue though, so I tried to start a build dense cloud for the project, which it sent only to one of the nodes, and on that node the terminal displays:
registration failed: unexpected error
Within the network monitor it then continues to display "Working" and the elapsed time starts counting up, but there is no cpu usage on the node machine.
Just gone back and tried with the previous version (1.1.6) and it does seem to work without these error messages.
Lastly, I've just noticed something... when starting the server (running from the new version) it displays:
Starting network server (version 1.1.6 build 2038)
family: 2
socktype: 1
protocol: 6
family: 2
socktype: 1
protocol: 6
thread started
waiting for incoming connections...
waiting for incoming connections...
i.e. The old version number... Is this because it hasn't been updated?
Cheers
-
Hello dcm39,
All PhotoScan instances (node, server, client) should be of the same version and build number.
-
Ah, quite right. It seems that the server was running build 2154, not 2158 as I had thought.
Thanks!
On a different note, on one of the machines, I'm getting the following error (in launching the client):
Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40807)
I can get rid of it by overriding the photoscan.sh script to force it to use the system libraries instead of the ones provided. However, the system libraries are older and don't work properly with the 3d display (only get markers, not pointcloud). It seems that although the Qt libraries are provided, it is using a system one as well?
I'm using Mageia linux, 64-bit. Running ldd | grep -i qt shows that it is correctly referencing the 4 libraries in the install directory.
Any suggestions?
-
Another network processing problem. I'm distributing processing onto two servers, one of which has a GPU, the other does not. I have only a single user profile on our system.
Starting the node, the one with the GPU gets the --opencl_gpu_mask 1 and the node without gets --opencl_gpu_mask 0.
With processing running (fine distribution to both machines), we get:
[CPU] estimating 238x257x96 disparity using 238x257x8u tiles, offset -52
opencl not found
processing job: BuildDenseCloud
timings: rectify: 0.015485 disparity: 0.08769 borders: 0.01633 filter: 0.02417 fill: 1e-06
[CPU] estimating 242x251x96 disparity using 242x251x8u tiles, offset -53
timings: rectify: 0.01503 disparity: 0.078616 borders: 0.009516 filter: 0.009682 fill: 0
ie. "opencl not found" errors, only on the machine without a graphics card. These errors flood back to the server, but they don't seem to affect the processing.
I suspect that this is to do with the user profile. There seems to be interference between instances run from the same user profile.
-
Computer locks up when attempting to trim a mesh with 52 million faces.
No problems creating the mesh or decimating down to 5 million faces.
PhotoScan Standard Edition Version 1.2.0 build 2158 (64bit)
Windows 7
Intel i7-3770 3.40 GHz
16GB RAM
AMD Radeon HD 7770 GPU 2GB memory
AMD driver 14.501.1003.0
Added:
Updated graphics driver to latest version from AMD website 15.200.1062.1004
With the large mesh the system appears to be moving data in and out of C drive which is a 100 GB SSD with 18.3 GB free. System has two other large internal drives, both of which have lots of free space.
Trimming the decimated 5 million face mesh works fine.
-
Hello,
I encountered a problem with the last beta release, photoscan freezes (not responding during about thirty seconds) every minute regardless the action I do.
May be this is related with the lag observed (and reported ) before, but now it is really impossible to work with such issue.
All my pc is up to date (windows seven recently updated, graphic drivers too). The projects I tested are not big and during the freezes, the processor is not used. Do you have an idea?
Thanks.
Pascal
PS: after a quick reprocessing of partial set of photos no freeze was observed for the moment, does this mean that all the old calculation are to be reprocessed if some additional work is needed? I will try to re-launch a problematic chunk with the last Photoscan version, and I will let you know ....
-
Hi, is there (or will there be) the possibility to export polylines or polygones as dxf?
shapefiles are OK for maps or "top-down" view but they are not workable if you work for example with wall facades or buildings.
Thanks,
G.
-
Giancan, just import the shapefiles and export as DXF in any GIS?
-
Hello,
Can you specify exact format for importing tiff DEM please? 16 bit or 32 bit? My experience is that Agisoft has lot of crashes after DEM import.
Best,
Jakub
-
Hello dcm39,
On a different note, on one of the machines, I'm getting the following error (in launching the client):
Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40807)
I can get rid of it by overriding the photoscan.sh script to force it to use the system libraries instead of the ones provided. However, the system libraries are older and don't work properly with the 3d display (only get markers, not pointcloud). It seems that although the Qt libraries are provided, it is using a system one as well?
I'm using Mageia linux, 64-bit. Running ldd | grep -i qt shows that it is correctly referencing the 4 libraries in the install directory.
Any suggestions?
The problem may be related to the usage of Qt plugins from another Qt version. Also the problem could be caused due to the windows manager using Qt.
Unfortunately, the problem is not common and we cannot suggest good solution for the problem at the moment.
Another network processing problem. I'm distributing processing onto two servers, one of which has a GPU, the other does not. I have only a single user profile on our system.
Starting the node, the one with the GPU gets the --opencl_gpu_mask 1 and the node without gets --opencl_gpu_mask 0.
With processing running (fine distribution to both machines), we get:
[CPU] estimating 238x257x96 disparity using 238x257x8u tiles, offset -52
opencl not found
processing job: BuildDenseCloud
timings: rectify: 0.015485 disparity: 0.08769 borders: 0.01633 filter: 0.02417 fill: 1e-06
[CPU] estimating 242x251x96 disparity using 242x251x8u tiles, offset -53
timings: rectify: 0.01503 disparity: 0.078616 borders: 0.009516 filter: 0.009682 fill: 0
ie. "opencl not found" errors, only on the machine without a graphics card. These errors flood back to the server, but they don't seem to affect the processing.
I suspect that this is to do with the user profile. There seems to be interference between instances run from the same user profile.
OpenCL error may appear only if opencl_gpu_mask is not set to zero.
-
Computer locks up when attempting to trim a mesh with 52 million faces.
No problems creating the mesh or decimating down to 5 million faces.
PhotoScan Standard Edition Version 1.2.0 build 2158 (64bit)
Windows 7
Intel i7-3770 3.40 GHz
16GB RAM
AMD Radeon HD 7770 GPU 2GB memory
AMD driver 14.501.1003.0
Added:
Updated graphics driver to latest version from AMD website 15.200.1062.1004
With the large mesh the system appears to be moving data in and out of C drive which is a 100 GB SSD with 18.3 GB free. System has two other large internal drives, both of which have lots of free space.
Trimming the decimated 5 million face mesh works fine.
Hello David,
2 GB video RAM may not be enough for visualization of high-poly models in solid/textured views. Shaded option is less resource demanding. Additionally I can suggest to switch "Enable VBO support" option in the Preferences window.
Which view option you are using?
-
Hello,
I encountered a problem with the last beta release, photoscan freezes (not responding during about thirty seconds) every minute regardless the action I do.
May be this is related with the lag observed (and reported ) before, but now it is really impossible to work with such issue.
All my pc is up to date (windows seven recently updated, graphic drivers too). The projects I tested are not big and during the freezes, the processor is not used. Do you have an idea?
Thanks.
Pascal
PS: after a quick reprocessing of partial set of photos no freeze was observed for the moment, does this mean that all the old calculation are to be reprocessed if some additional work is needed? I will try to re-launch a problematic chunk with the last Photoscan version, and I will let you know ....
Hello Pascal,
Do you have similar issues on the same projects with the version 1.1.6?
Recalculation of the old projects is not required, so I can suggest to check the system with anti-virus just for case.
-
Hi, is there (or will there be) the possibility to export polylines or polygones as dxf?
shapefiles are OK for maps or "top-down" view but they are not workable if you work for example with wall facades or buildings.
Thanks,
G.
Hello giancan,
We'll try to add DXF support and also add planar projection option for DEM generation.
-
Can you specify exact format for importing tiff DEM please? 16 bit or 32 bit? My experience is that Agisoft has lot of crashes after DEM import.
Best,
Jakub
Hello Jakub,
DEM should be in 32-bit floating point format TIFF file.
If you have any sample file that crashes application regularly, please send it to support@agisoft.com.
-
Alexei,
for the DEM import crash problem, I get it whenever I try to import a geotiff DEM 32 bit floating point in strip orientation format.
But if I try to impotrt a DEM in Tiff tiled orientation format, I have no problem....
Thanks,
-
Hello,
Great job, this new version brings full of good things !
About seamlines, is it possible to export shape (or dwg, dxf...) ?
Customers sometimes requests this.
Thanks
Maxime
-
Alexei,
for the DEM import crash problem, I get it whenever I try to import a geotiff DEM 32 bit floating point in strip orientation format.
But if I try to impotrt a DEM in Tiff tiled orientation format, I have no problem....
Thanks,
Hello Pap1956,
Thanks for the information, we've tracked the cause of the issue and will fix it asap.
-
About seamlines, is it possible to export shape (or dwg, dxf...) ?
Customers sometimes requests this.
Hello Maxime,
Thank you for the suggestion. We'll probably implemet it in one of the upcoming 1.2 updates.
-
Great !
-
Hello
We are using network computation with 3 computers... But whenever we want to connect the 3rd computer this message shows up:
registration failed: Key rejected
Is it possible that we have used the same key twice for our installations?
Hi, I have the same problem.
In the last months i worked with a lot nodes using the same license for all computers. Now i'm trying to use the last version of PS but it works for only one node. For the others, it doesn't accept the license.
-
Hello mrlc,
According to the license agreement PhotoScan license keys are node-locked, so on every node/computer separate license key is required for PhotoScan activation.
-
Dear Agisoft,
it seems that every time I try to export a panorama, the computer freezes (after around 15seconds) and it doesn't seem to recover even after some hours... so I have to hard reset. In the previous version, it was taking quite some time but i didn't experience any freezing.
Is there any settings to check or is it just a bug of this pre-release?
Also it seems that psx files create a number of folder and subfolder, differently from psz where all was contained in a zip archive. It seems also that some operation are not available with the psz format, so I am obliged to save my files in psx... with all their folders. Are you planning to leave this file format as it is now (with folders outside the file) or will you allow the user to choose whether s/he wants to create single-file psx or folders-psx?
Thanks
-
Hello giancan,
In the Save As dialog you can decide between PSZ and PSX formats. The latter one is required for DEM/Orthomosaic/Tiled model generation and also for network processing.
As for the panorama issue, please specify the number and resolution of the images in the Camera Station, the export resolution of the panorama and RAM available on the computer.
-
Dear Alexey,
I know how to save psx, I'm just wondering if there is a way to avoid the creation of folders and subfolders with the psx file.
About the panorama, I have 16Gb memory and trying to export panorama in a group of 128 images.
The default resolution in the wnidow is 30374x15187... actually I hadn't check it so I understand this may be the issue. But still, in the previous version I had not this problem and I managed to export from the same project.
Cheers,
G.
-
Hello Alexei,
with latest teease, I retried importing a DEM in Tif strip orientation format. It does import OK but now the DEM displays in just 2 colors: blue for nodata value (-32767) and red for valid values instead of different shades of color according to elevation difference. See attached screen....
-
Hello pap1956,
Can you please send any sample TIFF that can be used to reproduce the problem to support@agisoft.com?
-
Hello again,
in french language reporting option, please note following requests:
- in 1st section, replace topographiques by au sol and carrés by 2 see attached;
- in Camera Calibration section, eliminate par in Fig.2
Attached are screen captures....
-
In v 1.2 we need to generate a masaic before the export...
is there any possibility to crop the Orthomosaic in the workspace by selecting a shape before exporting / uploadimng the Orthomosaic?
I think this would be verry useful for many users.
Thanks for any hint!
-
Hello,
Is it possible to export Orthomosaic with contour lines?
that would be very helpful for me and my customers.
Thanks
-
Hello pap1956,
Thank you for your comments on GUI, we'll consider your suggestions.
-
is there any possibility to crop the Orthomosaic in the workspace by selecting a shape before exporting / uploadimng the Orthomosaic?
Hello ristag,
You can draw a polygonal shape on the orthomosaic that will be used for the export area definition. But don't forget to specify boundary type for the polygon (select it, right-click and choose boundary type - can be either inner or outer). Export process will automatically use the shape to exclude unwanted area.
-
Is it possible to export Orthomosaic with contour lines?
Hello Davis,
You can export them separately, as orthomosaic is a raster, and contours are vector data. Later you can combine them in the external application.
-
Hello,
I have some problems with my Python sript (build 2167) :
When it saves my project with this command :
doc.save(os.path.join(dossierProjets, dossier + ".psx"),compression = 6,absolute_paths = False)
files are correctly saved (.files and .psx) but all steps made after do not work. They seem to work because PhotoScan computing, but when he finished there is nothing in workspace and nothing in folder.
Besides, accuracy_cameras requests now 3 vectors. I suppose it's x, y and z ?
Is it the correct syntax ? : chunk.accuracy_cameras=[0.5, 0.5, 0.5]
In buildDem command on Python api, you can choise the PhotoScan.PointsSource :
Points source in [SparsePoints, DensePoints]
But can we build DEM from Mesh ?
My other problems will probably be solved with the first.
Thanks
Maxime
-
Hello Maxime,
Camera accuracy definition seems to be correct in your example. Using different values will result in different accuracy along each axis.
To build DEM from the model you need to use PhotoScan.DataSource.ModelData as a source.
And please provide more info on the save project issue. Can it be reproduced using the commands in the Console pane one by one, or the complete script should be executed?
-
Hello,
I have some questions dealing with (new) parameters in PhotoScan 1.2.0
In optimize camera alignment dialog there is p3 and p4. Are these parameters additional terms (likep1 and p2) to create an aproximated function that describes the nonsymetric distortion function?
The other thing is fit aspect (before 1.2.0). What happens if its checked or not? Is it the aspect ratio between pixel in x direction an y? My idea was that optimzing this parameter forces the adjustment to create square pixels? I havent found anything in the manual...
Gradual selection:
What does projection accuracy mean?
Any help and advice is welcome!
Thanks
Paul
-
Thanks alexey, the Orthophoto-export with bound works well!
-
Hello Maxime,
Camera accuracy definition seems to be correct in your example. Using different values will result in different accuracy along each axis.
To build DEM from the model you need to use PhotoScan.DataSource.ModelData as a source.
And please provide more info on the save project issue. Can it be reproduced using the commands in the Console pane one by one, or the complete script should be executed?
Hello Alexey,
I do not know to use the console pane one by one, I use only .py files.
Find below my script.
When I put the save command (doc.save(os.path.join(dossierProjets, dossier + ".psx"),compression = 6,absolute_paths = False)) just before aligment, all other commands work, but at the end of the process, there is nothing (see attached file "window").
When I put the save command (doc.save(os.path.join(dossierProjets, dossier + ".psx"),compression = 6,absolute_paths = False)) just before buidDem command, all commands executed before are OK but there is no Dem (see attached file "window_2")
Regards
Maxime
-
He there,
it seems that in this new version the DEM (and potree as far as I can see) creation ignores any edits to the dense cloud.
If I cut part of the cloud or clean it up from undesired points and create DEM or export it as potree, what I get is the cloud before all my edits.
Cheers,
G.
-
Hello Giancan,
We were unable to reproduce the problem on the latest build of 1.2 version.
Dense cloud export saves the same points you see in the model view (providing that they are inside the bounding box).
DEM generation based on the dense cloud may interpolate the missing areas, if they are visible from at least one camera. So could you please check whether you see the results of interpolation for DEM based on the cropped dense cloud?
-
Hi Alexey,
Unfortunately with the update build 2172 now I get an error when you run the script, something changed, you can help.
dist = calib.error(T.mulp(points[point_index].coord), proj.coord).norm() ** 2
Error = AttributeError: matrix * vector: vector length does not match matrix row size minus 1
Thank you
-
The issue definitely shows up when exporting to potree. All points are exported from the dense cloud although I surely delete some of them from the dense cloud.
In the dem, this is more difficult to show but I will try to capture some screenshots to demonstrate it.
-
Hello Diego,
In the latest build we've slightly changed the representation of the sparse cloud points via Python.
Now point.coord is a 4-dimensional vector. If the fourth element is zero, it means that the point is actually a ray (applicable for points detected for single camera station). Otherwise regular points have 1 as fourth element.
.mulp() function accepts 3-dimensional vector on input, so when working with the sparse cloud points coordinates they should be treated accordingly to the new representation.
I've sent you updated script via e-mail.
-
I have some questions dealing with (new) parameters in PhotoScan 1.2.0
In optimize camera alignment dialog there is p3 and p4. Are these parameters additional terms (like p1 and p2) to create an aproximated function that describes the nonsymetric distortion function?
The other thing is fit aspect (before 1.2.0). What happens if its checked or not? Is it the aspect ratio between pixel in x direction an y? My idea was that optimzing this parameter forces the adjustment to create square pixels? I havent found anything in the manual...
Gradual selection:
What does projection accuracy mean?
Hello Paul,
P3 and P4 are tangential distortion coefficients with the higher degree items.
Aspect defines the relation between pixel size in x and y directions. Unchecking the aspect in the optimization dialog will keep the same ration between pixel size (and therefore between Fx and Fy).
Projection accuracy is related to the size of the matching points (that are not actually points, but some region).
-
I do not know to use the console pane one by one, I use only .py files.
Find below my script.
When I put the save command (doc.save(os.path.join(dossierProjets, dossier + ".psx"),compression = 6,absolute_paths = False)) just before aligment, all other commands work, but at the end of the process, there is nothing (see attached file "window").
When I put the save command (doc.save(os.path.join(dossierProjets, dossier + ".psx"),compression = 6,absolute_paths = False)) just before buidDem command, all commands executed before are OK but there is no Dem (see attached file "window_2")
Hello Maxime,
I think it is related to the PSX treatment. After saving the project file in PSX format it is being re-loaded to the project space both in GUI and via Python. So you need to relink chunk variable to the document. If you've assigned doc = PhotoScan.app.document, it will work when trying to access the doc variable after saving. But previously assigned variables like chunk = doc.chunk will be now pointing to the isolated chunks outside the project.
-
Thanks Alexey, it's running now :)
Just a remark :
In PhotoScan Python Reference, for buildOrthomosaic, we can choise surface between OrthoSurfaceDem and OrthoSurfaceMesh.
It seems that neither works. (my syntax : surface=PhotoScan.OrthoSurfaceDem or surface=PhotoScan.OrthoSurfaceMesh)
error message : AttributeError: 'module' object has no attribute 'OrthoSurfaceDem'
But if one puts nothing, it works and it takes DEM.
Maxime
-
Hello Maxime,
I think you need to use: PhotoScan.DataSource.ElevationData or PhotoScan.DataSource.ModelData in .buildOrthomosaic() function.
-
Split in chunks script doesn't work with current version.
http://wiki.agisoft.com/wiki/Python
-
Hello,
buildding Orthomosaic from mesh gets slow after 3% and freezes after 10%.
Dense point cloud has 38Mio points, mesh 2,4 Mio faces. 8GB RAM, 100GB free Disc space (which is still 80GB while freezing).
In 1.1.6 the orthofoto export works without problems.
Regards,
Mathias
-
Hello bisenberger,
you need to comment or remove the following line:
doc.addChunk(new_chunk)And also change the following arguments in the Build Mesh function:
source = PhotoScan.DataSource.DenseCloudDataand
source = PhotoScan.DataSource.PointCloudData
-
Hello Mathias,
Are you using the same parameters, maybe you can post the screenshots and attach the processing logs?
-
Hello Alexey,
I was using the same parameters (standard options).
Hers is a screenshot and the logfile. During the first attempt my computer crashed.
Mathias
-
What is the right flow to create the google map title.
Impossible to have real zoom.
Align
Dense Cloud
Mesh
Texture
Tile
Orthomosaic
Calcul and export Ok, but index.htm doesn't work (only google maps, no orthophoto with multiple zoom???)
Thanks
-
Dear Alexey,
as I mentioned earlier, in this beta version I experienced some problems when creating dem or orthomosaic from dense cloud. Indeed, although I "clean" the dense cloud, when I create a new DEM or ortho in different coordinate system, the results ignores the editing I did to the dense cloud, and instead it uses the original cloud.
Cheers,
G.
-
Hello Giancan,
Still we are not able to reproduce the problem: we got dense cloud in one coordinate system, then we crop the cloud and build DEM in another coordinate system: the resulting DEM is based only on the cropped part of the cloud (though it may be interpolated to the bounding box limits).
-
Hi
We still run the 1.1 version. The update to 1.1 seem to have removed the possibility to generate large tiled models with manual control of mesh such as generating method (we need heightfeild) and the number of polygon in the mesh. Today the mesh is based on arbitrary and mesh resolution cannot be decided manually. Previously we could export for example collada using the already meshed model.
Question:
Is it possible to add a manual choice for the 1.2
- manual control over the tiled model generation such as heightfield or arbitrary and also number of triangles in the mesh. The mesh should be built at high and then decimated to create a sharper mesh. And only autogenerate the tiled texture based on generic and a resolution by choice.
We use agisoft for city projects and love it but the removal of manual control of the tiled models will soon force us to look at other programs.
Thanks for a great program!
Fredrik
-
Dear agisoft,
While i export the DEM i found some extra part exported with it, how i remove it in PS? its annoying me while i tried to generate contour!! the previous version 1.1 hasn't that issue.
Thanks
Mohamed
-
Haven't read all the posts here, apologies if it's already been reported.
- I LOVE the selection tools. VERY useful. Thanks!
- the batch process doesn't seem to be working. It will spend all of the time calculating but not write out any files. I would like to see this working - of course - and also a batch process across numerous files. ie: 1) set up alignment and area to process for x files 2) determine the batch parameters and then 3) launch > it would then work through one file after the other
Thanks again. Great to see this work being done!
-
Hi all,
is it possible have an import mask like 1.1.6? In detail I prefer have the option to skip "Error: Can't load image: D:\fake path/_MG_5348.png" with a blank mask...
-
sorry double post.
-
Hello,
I did install the latest beta, photoscan-pro_1_2_0_x64_2181beta, and get this extremely strange colours on the orthophoto!! For some reason, photoscan have not been able to create a complete mesh in the area also, but it is extrapolated.
The seamlineeditor is very promising!
The possibility to save batch-jobs is great :D
but when I close and reopen, the path; {projectfolder}/{chunklabel}.LAS
from the xml-line:
<param name="path" value="{projectfolder}/{chunklabel}.LAS"/>
is replaced by adding the full absolute path like this:
d:\data\X8projects\{projectfolder}/{chunklabel}.LAS
and I have to manually edit the batch job to: {projectfolder}/{chunklabel}.LAS
Thanks, looks exciting!
But for now I revert back to my latest working version: photoscan-pro_1_1_3_x64_2018
-
Hi Mohamed: it looks like you have created the mesh with the extrapolation option enabled.
Dear agisoft,
While i export the DEM i found some extra part exported with it, how i remove it in PS? its annoying me while i tried to generate contour!! the previous version 1.1 hasn't that issue.
Thanks
Mohamed
-
Dear Agisoft,
i Align only 16 images and it give me an Error Not enough Memory its very weird whit this new update i tried to Align in Medium also and give me same Error!!! Plez help most of my projects saved in PSX.
Thanks,,
-
Hello tornado2011,
Is it possible that you have accidentally installed 32-bit version of PhotoScan?
As for your request regarding the contour lines and extrapolated geometry, we'll try to add an option to generate contours only inside the polygon shape marked as border.
-
Hello tornado2011,
Is it possible that you have accidentally installed 32-bit version of PhotoScan?
As for your request regarding the contour lines and extrapolated geometry, we'll try to add an option to generate contours only inside the polygon shape marked as border.
Dear Alexey ,
Thank you for your quick replay!
i fixed the problem thanks!
I hope you do it also with the DEM the extra poly very annoying! i hope also to add the altitude information in the contour lines!
Thank you,
Mohamed
-
Dear Agisoft,
Another important issue with the new update related to generating Orthophoto. as you can see in the new update when i tried to build the orthophoto i found some weird lines color it never happen before so i install the previous version 1.1.6 and its gone?so plz try to fix it ASAP!
Thanks
-
I am having problems with the Measure Shape tools on a DEM. I have a stockpile that i drew a shape around, and used the measure shape command, and the volumes are out to lunch.
However, it seems to be with how the polygon is created. I picked points with the polygon tool, on areas entirely withing the DEM, but when you perform "measure shape", on the planar tab has many of the polygon nodes with an elevation of 0.
It seems like when picking points of the polygon some elevations are to the DEM, while others are Zero. Anyone else have this issue??
Kevin
-
When exporting an orthomosaic the no data area is black is there a way to export with a white no data area?
-
Hi Alexey,
I am getting this error when building dense point cloud on high setting.
"ocl_engine.cpp Line 231: clEnqueueWriteBuffer failed"
It happens once or twice during a medium quality build but during a build on high it is pretty much constantly switching to use the CPU.
The video card being used is a radeon HD 7990 with latest drivers installed... Could it be a temperature issue? what should I be looking for?
Thanks
-
Dear Agisoft,
Another important issue with the new update related to generating Orthophoto. as you can see in the new update when i tried to build the orthophoto i found some weird lines color it never happen before so i install the previous version 1.1.6 and its gone?so plz try to fix it ASAP!
Thanks
Hello tornado2011,
Can you send any sample dataset that can be used to reproduce this issue to support@agisoft.com with the related project data?
-
I am having problems with the Measure Shape tools on a DEM. I have a stockpile that i drew a shape around, and used the measure shape command, and the volumes are out to lunch.
However, it seems to be with how the polygon is created. I picked points with the polygon tool, on areas entirely withing the DEM, but when you perform "measure shape", on the planar tab has many of the polygon nodes with an elevation of 0.
It seems like when picking points of the polygon some elevations are to the DEM, while others are Zero. Anyone else have this issue??
Hello Kevin,
Can you post a screenshot of the DEM in PhotoScan window?
Is it possible that the elevation model has any holes due to the disabled interpolation or lack of the overlap, for example?
-
When exporting an orthomosaic the no data area is black is there a way to export with a white no data area?
Hello bisenberger,
No data area in the exported orthomosaic is transparent in TIFF and PNG formats. But we'll see if it would be possible to implement the background color selection for JPG format.
-
I did install the latest beta, photoscan-pro_1_2_0_x64_2181beta, and get this extremely strange colours on the orthophoto!! For some reason, photoscan have not been able to create a complete mesh in the area also, but it is extrapolated.
The seamlineeditor is very promising!
The possibility to save batch-jobs is great :D
but when I close and reopen, the path; {projectfolder}/{chunklabel}.LAS
from the xml-line:
<param name="path" value="{projectfolder}/{chunklabel}.LAS"/>
is replaced by adding the full absolute path like this:
d:\data\X8projects\{projectfolder}/{chunklabel}.LAS
and I have to manually edit the batch job to: {projectfolder}/{chunklabel}.LAS
Hello eriks,
Thank you for reporting. Issue with the import of the batch jobs will be fixed in the next 1.2 update. As for the color issue, were you using color correction option? If the problem is reproducible, then probably you can provide the dataset that can be used for our internal investigation to support@agisoft.com?
-
I am getting this error when building dense point cloud on high setting.
"ocl_engine.cpp Line 231: clEnqueueWriteBuffer failed"
It happens once or twice during a medium quality build but during a build on high it is pretty much constantly switching to use the CPU.
The video card being used is a radeon HD 7990 with latest drivers installed... Could it be a temperature issue? what should I be looking for?
Hello SuperNewb,
Looks like the problems with the drivers. If the clean installation of the latest ATI drivers doesn't help. Probably you can try installing the previous driver version.
-
Thanks Alexey,
I used DDU to clean out my old drivers and used the 14.4 version of catalyst drivers for AMD. It looks like my troubles have all gone away... Woohoo, I thought this was going to be a lot more trouble.
-
Attached is a screenshot of a stockpile i was trying to determine a volume of, along with the measure report.
I created a dense cloud, then a DEM from it (with interpolation on), and then created the polygon around the pile. Many of the nodes show a zero elevation for some reason.
I also created contours on the DEM, and they look fine.
I have tried it on a number of different projects as well, and will more often than not see the zero elevation for many of the nodes.
Kevin
-
Hello Kevin,
Thank you for providing additional info. We'll try to reproduce the problem and fix it in the next update.
-
Dear Agisoft,
Another important issue with the new update related to generating Orthophoto. as you can see in the new update when i tried to build the orthophoto i found some weird lines color it never happen before so i install the previous version 1.1.6 and its gone?so plz try to fix it ASAP!
Thanks
Hello tornado2011,
Can you send any sample dataset that can be used to reproduce this issue to support@agisoft.com with the related project data?
Hi Alexey,
Its hard to send the data and project file its very heavy and i notice that this issue just happen with big number of images as u see i took more than 2k images, see the attached file i tried to test it in anther project and the problem existing again (left snapshot) while in the right snapshot i deleted some images and reprocess again the highlights is gone ! please check this issue ASAP!
Thanks,,
Mohamed
-
Hi!
The problem still exist in the new update?! the brightness area only happened with big number of images while when i reduce them there's no brightness! ( see previous message snapshot)!
Thanks
-
Hello tornado2011,
Is it possible that some of the original images has much different brightness compared to other images?
-
Hello tornado2011,
Is it possible that some of the original images has much different brightness compared to other images?
Hi Alexey,
No it isn't all the images are in good light condition
and in the V1.6 i used all the 2k images and the result was very good!
Thanks!
Mohamed
-
Occasionally when running batch process nothing has been created when it finishes. When it happened last time I had it set to create dense cloud>build mesh>build texture. When it finished all I had was the original tie points.
-
Hello Mohamed,
Unfortunately, without being able to reproduce the problem, we can't investigate, what's wrong. So if there is any possibility to provide the dataset for testing, we would appreciate that. Probably, you can use only a smaller area (top on the screenshots) and if there's the same issue, then you do not need to send the complete dataset.
-
Occasionally when running batch process nothing has been created when it finishes. When it happened last time I had it set to create dense cloud>build mesh>build texture. When it finished all I had was the original tie points.
Hello Bill,
Was the procedure marked as completed in the Batch Job dialog? Do you have the related log file for the batch?
-
As I can see in the main paig of the Web you can download the 1.2....
is 1.2 the final version? right now?
-
Occasionally when running batch process nothing has been created when it finishes. When it happened last time I had it set to create dense cloud>build mesh>build texture. When it finished all I had was the original tie points.
Hello Bill,
Was the procedure marked as completed in the Batch Job dialog? Do you have the related log file for the batch?
Each procedure was marked as completed. Unfortunately I didn't have the write to log enabled (it must have got changed when I updated). I have it set now so if it happens again I will send it.
-
The Append command is not working.
-
Hello skndol,
Yes, it's final release of 1.2.0, but we still have this thread opened for feedback on the version.
-
Hello Bill,
Regarding Append, are you trying to append .psx file to the existing psz?
-
I had an older psz file that I saved as a psx. I'm trying to append a new psx to it.
hmmm... I just tried it again and it worked this time.
-
.psx file handling has greatly improved, the time it takes to open or change chunks within a psx is almost instant now, good job!
Is it still advised to save to psz before doing any changes to a project or is it possible to do more stuff in a .psx file now?
-
I had an older psz file that I saved as a psx. I'm trying to append a new psx to it.
hmmm... I just tried it again and it worked this time.
Hello Bill,
If you face it next time, please inform us the sequence of the steps that should be performed to reproduce it.
-
.psx file handling has greatly improved, the time it takes to open or change chunks within a psx is almost instant now, good job!
Is it still advised to save to psz before doing any changes to a project or is it possible to do more stuff in a .psx file now?
Hello sc,
PSX format is now a default format for PhotoScan Pro (although you still can save in PSZ), so you can work with it without any limitations and need to resave it in another format.
-
Hello Mohamed,
Unfortunately, without being able to reproduce the problem, we can't investigate, what's wrong. So if there is any possibility to provide the dataset for testing, we would appreciate that. Probably, you can use only a smaller area (top on the screenshots) and if there's the same issue, then you do not need to send the complete dataset.
Hi Alexey ,
Thank you for your respond!
I'm already used a small area like you said and i found the problem was solved but after i used the whole images the problem back again! so i guess its happen with big images! see snap shot! the data size is 14GB so its difficult to send it to you!
Thanks Mohamed
-
Possibility to export orthomosaic from actual view (or mode planar in old version) has disapeared?
Or it's in other option?
I want to export "orthoplan"
Thanks
-
Hello pastouf,
Current view option can be applied to mesh-based orthomosaic generation (Build Orthomosaic). It would be available in Planar projection tab. For geographic projection TopXY view will be applied by default.
-
Hi Alexey,
I see that the "Reference Settings" dialogue has changed in the recent updates. With the new changes, I find myself unable to lower my overall error when optimizing to GCPs.
Normally in my workflow I optimize cameras only first to remove as much scene warping as possible. Then I uncheck all cameras and optimize to my GCPs using the default 0.005 GCP accuracy. This always worked nicely for me but now I can not get my error down using the same method...
I also see that there are new boxes in the "optimize" dialogue. I have played with checking and unchecking different boxes and still can not get my error down.
with my current project, I expected a 5 to 10cm average error but I can not get the error below 18cm now.
Could you explain what all the new options mean in both the "Reference Settings" and "Optimize" Dialogues?
Thanks and keep up the good work.
(Edit) I took the GCP accuracy down to 0.0005 and after optimizing got my expected error back to normal.
Also I see the manual has been updated to version 1.2 and covers most of my queries.
-
Hello pastouf,
Current view option can be applied to mesh-based orthomosaic generation (Build Orthomosaic). It would be available in Planar projection tab. For geographic projection TopXY view will be applied by default.
Many thanks,
But why build orthomosaic before export?
I don't understand why you have separate this multiple option?
For a batiment, i want export each face, so i am obliged to build orthomosaic each time.
In older version, i don't have this pb.
(sorry for my poor english)
In french :
Pourquoi avoir séparé les options de construction?
Je dois construire l'orthomosaic avant un export.
Pour un batiment ou je dois exporter chaque face, cela rajoute plusieurs calcul.
Chose qui n'était pas obligatoire dans les versions précedentes.
-
Hello pastouf,
Exporting orthomosaic option just saves already built mosaic.
So now it is not necessary to rebuild the mosaic if you wish to export it in lower resolution, save in a different file format, use different geographic projection. Also building the orthomosaic prior to export allows to review it in PhotoScan window and edit seamlines, if necessary.
-
Hello Alexey,
I am unable to open pox files via the open dialog.
psx files are greyed out. Just psz files are not greyed.
The only way to open my projects is via the used documents commond in the file menu.
Working on Mac 10.10.5
Best,
Mathias
-
Hello Mathias,
Seems like a localization issue. We'll fix it in the next update, but currently you need to switch to English language.
-
I found some minor confusing documentation issues in the (amazing !) Python API build 2198:
1. (page 15,16)
buildDem(source=DensePoints,...
...
source (PhotoScan.DataSource)
...
2. (page 16)
buildOrthomosaic(surface=OrthoSurfaceDem,....
...
surface (PhotoScan.DataSource)
...
declaration is:
class PhotoScan.DataSource
PointCloudData, DenseCloudData, ModelData, ElevationData
=> what is "densePoints"
=> surface points to the wrong enum
=> I could not find "SparseCloudData": is "PointCloudData" == "SparseCloudData" ??
Thanks, Ruedi
-
Hello Ruedi,
Thanks for pointing on this. We'll make the corrections in the function description.
You are right that source argument for the .buildDem() function should be either PointCloudData, DenseCloudData or ModelData whereas for .buildOrthomosaic() you can use either ModelData or ElevationData.
The meaning is the following: DEM can be generated from sparse cloud, dense cloud or mesh model, and orthomosaic can be projected on mesh model or DEM (cannot be projected on either of the point clouds).
-
About seamlines, is it possible to export shape (or dwg, dxf...) ?
Customers sometimes requests this.
Hello Maxime,
Thank you for the suggestion. We'll probably implemet it in one of the upcoming 1.2 updates.
Hello,
More precisely , customers demand a shape giving in each attribute cell the image name.
Also, it will be great to export seamlines in order to import it in other chunk/project.
For exemple, we do RVB and NIR photos in same flight with 2 different caméras. We succeed to align all pictures in same time (1 chunk) and also generate dense cloud and DEM with mixed pictures. After, we separate RVB an NIR to generate othomosaiques. Thereafter, we have to retouch seamlines twice making sure they go to the same place betwen RVB and NIR. It take a lot of time.
Bad seamline exemple attached in false colors image (RVB and NIR mixed).
Best regards
Maxime
-
Hi Alexey,
I found a bug in the version 1.2.0 Build 2198, do not save me some markers, after applying markers keep the project and apparently so good, close and open the project and markers are not marked. My temporary solution was to export the markers to keep his job and then import it, but just do not save.
Regards,
Diego
-
Hello Diego,
Please provide some additional details, you are placing marker projections?
-
Hello Alexey,
Yes, is marker projections, Project 960 large-format photographs and 76 marker projections, measuring points and keep what worked for now was to save the project in *.psz
Regards,
Diego
-
Hello Diego,
I'm trying to reproduce the problem, but still cannot. Are there any special steps to be performed?
-
Hello Diego,
I'm trying to reproduce the problem, but still cannot. Are there any special steps to be performed?
Hello Alexey,
Thanks for your attention, I could reproduce the problem with the following builds 2127, 2149, 2181 y 2198, I find nothing special in the proceedings, My only solution was to work measure all marker projections and save *.psz format, after all adjustments successfully, I saved as *.psx to perform tasks that require the use of this format.
Best regards,
Diego
-
So the steps are like the following: add photos, align photos, put marker projections, save as PSX. Then open project, correct?
-
Hello Alexey,
It is correct. I noticed today with a project, when I saw that many points that were measured were not marked.
Best regards,
Diego
-
Hello,
deleting dense cloud points don't seem to correctly update the total number of points displayed in the lower left corner
edit: I have not been able to reproduce this
-
Hi,
I have two sets of JPG images one before editing and other after editing i Align and mesh the first set then after i changed the path and choose all camera its only effect in one selected camera! so could you check it.
Thanks,
Mohamed
-
Hello Mohamed,
Change Paths operation is case sensitive, so if the extension of the original image set is "jpg" and of edited images "JPG" it wouldn't work.
-
For export in PDF 3D, is it possible to add logo?
For communication it's better. 8)
-
Hello pastouf,
At the moment such functionality is not supported, but thanks for the suggestion.
-
in tools -> exports -> shape ?
what is possibility to export in shapefile.
option is never actived?
-
Export Shape option is only available if there are any drawn points, polylines or polygons in the Ortho view.
-
what is ortho view?
i try all view and selected with polygon, but never option is actived?
if it's option that i think, it's terrible...
-
i find, it's terrible....
-
It's not terrible. Obviously you're using it wong.
After you've build an Orthomosaic, if you double click on the Orthomosaic in the WORKSPACE sidepanel to the left in Photoscan you can create polygons in the ortho viewer. WIth export shapefiles you can export these polygons..
-
Using the Raster Calculator feature, by just clicking on the "B3- Blue" channel in the Raster Calculator
It immediately shows "Invaid Expression". But this error does not appear on B1-Red and B2-Green.
This should be a bug.
I understand that we should just input B1, B2 or B3 instead of "B3- Blue", but clicking the "B3- Blue" button automatically inputs "B3- Blue", which makes users confuse, it should just input B3 .
-
Hello rexsham,
Thanks for reporting. It will be fixed in the next update.
-
Hello Alexey,
It seems that I found a script doing the same as in Diegos, therefore I have the same error.
Could you also help me out with that?
Hello Diego,
In the latest build we've slightly changed the representation of the sparse cloud points via Python.
Now point.coord is a 4-dimensional vector. If the fourth element is zero, it means that the point is actually a ray (applicable for points detected for single camera station). Otherwise regular points have 1 as fourth element.
.mulp() function accepts 3-dimensional vector on input, so when working with the sparse cloud points coordinates they should be treated accordingly to the new representation.
I've sent you updated script via e-mail.