Messages

1

Bug Reports / Re: reference information- import csv dialog will not open- unable to load reference

« on: September 22, 2020, 08:47:13 AM »

Update: turns out when asking clicking on 'import reference' there is an option to choose the csv file type. For some reason this computer was using the Mavinci csv as the default file type. Changed this to character delimited csv and all went forward as it should.

Apologies for the false alarm- unsure of how this became the default- good use for the console to see what was happening- lots of little menu items to check took awhile to figure out where that option came from.

Thanks

2

Bug Reports / Update- solved- import csv dialog will not open- unable to load reference

« on: September 22, 2020, 12:26:16 AM »

Hi,
I am running Agisoft Metashap Version 1.6.4 build 10928 (64bit).

I have DSLR images and associated PPK image reference file (.csv format). When I import photos into a chunk I am unable to import the csv to assign location information to those images. When under the reference tab I choose the 'import refrence' button I am able to select the csv with but then nothing happens. The import csv dialog will not open. The console log reports:

2020-09-21 12:02:16 ImportReference: format = ReferenceFormatMavinci, path = C:/Users/NAD(83)-6318.csv
2020-09-21 12:02:16 Finished processing in 0.001 sec (exit code 1)


I assume the problem is that it is looking for a file formatted for Mavinci. I am not aware of a place to change this setting or how this would have been set (I have never used the Mavinci software or loaded any Mavinci files on this computer or any other). Why is this happening and how can I change this so that I am able to load a standard csv?


Note:
I have a second computer running the demo version of Agisoft Metashape 1.6.0 build 9925 (64bit). In the reference tab, when I click on 'import reference' the import csv dialog comes up and I am able to successfully reference the images. On this version the console reports:

2020-09-21 12:39:09 ImportReference: path = C:/Users/NAD(83)-6318.csv
2020-09-21 12:39:09 Finished processing in 0.004 sec (exit code 1)

3

General / Re: Sorting out DJI's bad GPS Altitude tagging

« on: August 31, 2018, 10:37:28 PM »

Thanks very much for posting this workflow. I think you are mistaken on one point however.

This is an old post but hopefully someone will respond if the below does not add up.

By correcting your relative elevation values with a home point barometric elevation value I believe you are potentially introducing rather than doing anything to eliminate barometric elevation variance into your resulting absolute elevation values.

Barometric variation may cause an absolute elevation value to read higher or lower than is true but should not affect the relative accuracy (given that pressure conditions are regionally stable). For a simplified example if the actual elevation is 100m and your barometer reads 200m and then you walk uphill 50m your barometer will read that pretty accurately and give you an elevation of ~250m.

Since the DJI barometer is giving you a relative elevation value (above your control/home point elevation) you should correct it with the best available elevation value for your home point. A good quality calibrated barometric elevation reading may meet this qualification however I would check as to what data it is using to calibrate you may not be getting a value any better than the consumer grade GPS elevation that you are trying to bypass with this whole process (although at least it would be a consistent variance across the dataset since it comes from one reading).

For example at the below link for an iphone app you can see that there are a variety of ways that this particular app may be calibrated.
https://www.ios-altimeter.com/

Suggested sources for best elevation values: a good GNSS reading at the home point, GIS layers such as: National Elevation Dataset or a local Lidar dataset

Note: there are the scripts as mentioned above however this workflow seems like potentially a better option for projects that involve multiple home points

4

General / GCP's and very high error values

« on: October 06, 2017, 04:45:35 AM »

I have run a dataset referenced with 3 GCP's. I used the exif geographic information to align the photos then entered the 3 GCP's. I unchecked the photos and for the rest of the workflow the GCP's were used as the geographic reference. I am seeing very high error values attached to the images as you can see from the attached screenshot (ie. 131970+ meters).

I have compared my GCP coordinates with an earlier previously produced orthomosaic (georeferenced using only the image exif data) in GIS software. They are quite close- generally within 1m. When I compare the GCP georeferenced orthomosaic with the exif georeferenced orthomosaic in GIS they are also quite close as expected.

Since things check out for me I am confused as to where this large error value is coming from. Am I missing something critical here? Can you explain what this value is?

Thanks very much!

5

Bug Reports / Re: "Error reading project"

« on: May 07, 2017, 05:33:12 AM »

Hi, I have been unable to get a repeat of the problem after several trials. I am beginning to suspect a file naming hygiene issue related to another user of the same computer. Apologies and thanks for the quick responses. I will email those files if I am able get a repeat and verify that a problem exists.
Thanks

6

Bug Reports / Re: "Error reading project"

« on: May 02, 2017, 08:48:22 PM »

Thanks Alexey,
I should have clarified that the .files folder is also in the same directory location. I have also tried putting both the .psx and the .files folder in a new folder together. I have looked at the xml file in the frame.zip folder and as suggested above and all the paths seem correct/the folders exist. Also since this priject opened corectly before it was moved the issue of incompletely written/saved files seems unlikely. Do you have another idea as to what the problem may be (this has occurred with multiple project files)?
Thank you.

7

Bug Reports / Re: "Error reading project"

« on: May 02, 2017, 07:06:19 AM »

Hi,
I am having a similar problem. Photoscan 1.3.1 on Linux and using .psx files. I get an 'Error Reading Project' message when trying to open projects that have been moved from one folder location to another (the file opened correctly prior to the move). The console reads 'Error: can't read project: /.../Desktop/041317 River.files/project.zip

I am new to Photoscan, I am assuming there are some dependencies I have somehow broken but I am not finding documentation of this. Can I recover these files or failing that how can I safely move these files in the future?