Messages

1

General / Re: Geometry going wrong in 'samey' areas

« on: October 01, 2015, 11:30:28 AM »

They 2046 x 2046. There a 6 photos in a hexagonal configuration (and a sky facing fish eye lens which I ignore... wonder if using that would help... ). There is a some lovely yaw pitch roll info but yes  I have to ignore that. It often fails to align the camera that is right beside the side of the road, facing straight into the hedge - which is kind of understandable - but there are usually 11 other pictures from more or less the same spot.

I've had to shelve sorting it out with Photoscan for now as I'm pushed for time.

Anyone know if there are any future plans to include yaw pitch and roll is the processing?

2

General / Re: Geometry going wrong in 'samey' areas

« on: September 30, 2015, 03:02:54 PM »

Thanks - I'll give it a go!

3

General / Re: Geometry going wrong in 'samey' areas

« on: September 30, 2015, 02:26:39 PM »

Hi James,

Thanks for that info. I stumbled across a couple of the forest canopy threads too and had a read of those. We used an external company to do the survey. The used a Leica Pegasus. It's not fish eye or wide angle - I'm setting the "Camera Type" to Frame within the camera calibration settings. This is what the survey company said about frequency "Max frame rate is 8fps - we usually cap it at 5m spacing".

It's not the shape of the hedges that's a problem. I don't think we're that bothered about them.. A hedge is a hedge for this purpose.  It's more that it loses alignment with the real life geometry - so the road isn't where the road should be. It's too high, too low or rotated. I would think I had something wrong with the way I am feeding the data to it - but most of the time it works - I just get some long bland stretches that go haywire.

4

General / Re: Geometry going wrong in 'samey' areas

« on: September 29, 2015, 03:10:57 PM »

Update:

I've now allowed it to use the masks while aligning photos - that's helped quite a bit but I am still hoping to perfect further. My survey data is a ground based survey. I've so far avoided using Ground Control Markers - I've been reading http://adv-geo-research.blogspot.co.uk/2014/03/agisoft-photoscan-crash-course-v-102.html and wonder if GCM might help my sections that are going wrong?

5

General / Geometry going wrong in 'samey' areas

« on: September 29, 2015, 01:38:35 PM »

I'm not sure if that's what's happening but here's the situation..

I'm modelling big long stretches of road. I'm using python script to set the settings and batch up the photos, set the reference and camera calibration etc. The models seem pretty good through villages. As I move into big long boring stretches with hedges on both sides and nothing much to differentiate (I'm guess this might be the problem) - the models geometry stops matching the real world..

I was having problems with rotation of my models but then had it pointed out that yaw pitch roll isn't used. So I started providing photos from both sides of the road. If I check the model window before I start Alignment - I can confirm I've got all the photos for both sides of the road - nothing odd or different going on from the models that look pretty good in the built up area. I'm only modelling relatively small chunks at a time with around 600 photos in each. Using 10000 tie points, high accuracy and "reference" pair selection

So my hypothesis is that it's struggling because of lack of interesting features.. Does this sound likely and is there anything I can do to help it out?

6

General / Re: Some rotation in my model..?

« on: September 24, 2015, 07:50:13 PM »

Is that your long term plan or will you introduce using the yaw pitch roll?

7

General / Re: Some rotation in my model..?

« on: September 24, 2015, 07:44:31 PM »

Ah right. OK thank you.

8

General / Some rotation in my model..?

« on: September 24, 2015, 06:04:56 PM »

I've spent quite a lot of time getting to grips with Agisoft and have been making some good models. I'm using data from a road based survey. I am supplying the model with x,y,z and yaw pitch and roll. I've also supplied it with camera calibration and told it to fix calibration. I don't use the "optimise alignment" process as I don't want to to change any alignment and I I set tie points to 10,000.

I'm reasonably happy that my input values are correct - when I use these to make a model using alternative software (e.g. a trial license of Acute3d), then the resultant model is perfectly aligned with the LiDAR data.

However, the Agisoft model seems to be suffering some rotation - on one side of the road the mesh is about 20cm higher that the LiDAR data, and on the other side of the road, it's 20cm lower.

I tried using different Yaw, Pitch Roll values as a test and the resultant model was the exactly the same. Does it actually use Yaw Pitch Roll?

9

Python and Java API / Re: Masks and Memory

« on: September 24, 2015, 12:30:12 PM »

Ah! I think I've solved it. One of the sets of 100 photos didn't have a mask. It wasn't causing the Python to fail and it wasn't causing a problem with the obj export - however I have just made an empty mask for the last 100 photos and the *.psz file now saves!

Thanks for your time.

10

Python and Java API / Re: Masks and Memory

« on: September 24, 2015, 10:37:39 AM »

Hi Alexey,

Yes It's 64 bit and yes the masks are applied correctly when I switch the masks on to view the area masked out - the output obj file looks great and all the bits I want to exclude, are excluded - it can happily export the obj file - it just won't save the .psz file.

I am running (in standalone mode) on 3 machines at the moment - I've just tried this on one machine. I am going to try on one of the other machines later this morning when it's free - to make sure it's not a problem with one of the machine's hardware.

Thanks,

Hannah

11

Python and Java API / Masks and Memory

« on: September 23, 2015, 04:25:13 PM »

I have a chunk with 600 photos. This is made up of 6 sets of 100 photos. Each set of 100 photos has a different directory and a different mask. I have written some Python that gets the correct mask and applies to the photo. This seems to work fine and I check each photo and it has the correct mask - however when I try to save I get an Agisoft message saying "Not enough Memory". This isn't the physical limits of my PC as the task manager says I'm using about 6GB of the 32GB available. What's going on?

Here's the Python in case that is doing something obviously silly:

mask_list = list()
current_path = ""

chunk = doc.chunks[0]
#create a list of the 6 masks
for j in range(len(chunk.cameras)):
      camera = chunk.cameras[j]
      
      if current_path != os.path.dirname(camera.photo.path):         
         current_path = os.path.dirname(camera.photo.path)
         mask_name = os.path.join(os.path.dirname(camera.photo.path),"mask.png")
         print(mask_name)
         m = PhotoScan.Mask()
         m.load(mask_name)
         mask_list.append(m)
      
#apply the 6 masks depending on photo path
for i in range(len(doc.chunks)):
   print(i)
   current_path = ""
   mask_index = -1
   chunk = doc.chunks[ i ]
   for j in range(len(chunk.cameras)):
      camera = chunk.cameras[ j ]
      if current_path != os.path.dirname(camera.photo.path):      
         current_path = os.path.dirname(camera.photo.path)
         mask_index += 1   
      
      camera.mask = mask_list[mask_index]
   
      
print("applying masks finished")

12

Python and Java API / Re: loadReference again

« on: September 21, 2015, 05:16:33 PM »

Aha! Great. Thanks very much!

13

Python and Java API / Re: loadReference again

« on: September 21, 2015, 05:07:31 PM »

HI Alexey,

Thanks - I am using absolute path in the format as follows (I've checked and confirmed the file is definately there!)

checkloaded = chunk.loadReference("Z:\\Circuits\\sampleRef.txt",'csv')

I've attached a sample. If I manually import this file as described in my first post, it works fine - so I know that the file labels in the file match the names .

Thanks for your help.

14

Python and Java API / Re: loadReference again

« on: September 21, 2015, 04:30:44 PM »

Hi Alexey,

My square brackets were removed by formatting here I think. So if I just try to apply to a single chunk by doing this:



chunk = doc.chunks[-1]
checkloaded = chunk.loadReference("path.txt",'csv')   
PhotoScan.app.update()


or

chunk = doc.chunk
checkloaded = chunk.loadReference("path.txt",'csv')
   



It still doesn't do anything - it returns true but nothing is updated when I manually check?

15

Python and Java API / loadReference again

« on: September 21, 2015, 04:20:53 PM »

At the moment I am loading the reference data manually. I'm setting a chunk active, clicking the reference pane and selecting "import".

The reference file is held in a .txt file in csv format.

I tried a script that looks like it should work. The return value of "loadReference" is true - but the X,Y,Z values of the photos never updates if I checked the reference pane.

The script is simply:

print("Script started")

for i in range(len(doc.chunks)-1):      
   chunk = doc.chunks
   checkloaded = chunk.loadReference("path.txt",'csv')
      
   PhotoScan.app.update()
   print(i, checkloaded)


print("Photos imported")

Anyone see where I am going wrong?