Topics

31

General / PointBox launch

« on: January 12, 2016, 11:33:23 PM »

Hello friends:
GEOBIT is pleased to announce PointBox, an online pointclouds publishing tool allowing you to interact in very agile and easy way with large point cloud models in the network.

With PointBox you can show your work by means of an attractive and user friendly interface and send your customers and friends, links for them to visualize your point clouds from anywhere through Internet connection.

Please, enter www.pointbox.xyz sign up and create your portfolio.

The viewing platform is at an advanced stage of testing and we believe that it already works rather satisfactorily. However you may still have some minor flaws we'll address as soon as we can. Be patient if you suffer from any kind of problem and, please, let us to know about it. We need your feed back

The display engine is based on WebGL technology, an already well-established standard for displaying 3D data on the Internet. Therefore, for your enjoyment it is necessary that both your browser and your graphic's hardware supports this technology. If you receive error messages that refer to the lack of these features, we regret to say that you can not enjoy the cloud display in your computer.

Show us your masterpieces!, enjoy sharing!

Best regards!

32

Feature Requests / "Pixel size" in Build Orthomosaic not usable when model is scaled with bar

« on: November 20, 2015, 01:39:40 PM »

Please, let user to set ortho unit/pix also when the model has been scaled by scale bars and not by control points... More than a feature request is a "why on earth I can't ...?" 
Thanks, folks

33

General / amazing work

« on: September 11, 2015, 06:04:33 PM »

I've seen this movie and suspected our beloved Photoscan was involved...
https://vimeo.com/134957666
I was right: look at this "making of..." at 2:27 and later at 3:35
https://vimeo.com/aixsponza/seed-makingof
I would have liked they had mentioned
Congrats to authors!

34

Feature Requests / import camera accuracy

« on: August 10, 2015, 09:23:58 PM »

Hi: I'm working in some hardware hacks that have allowed me to write 2miliseconds accurate timestamp in my drone photos and do precise GPS postprocess calculations. This gives me a good estimation of accuracy of the image coordinates.
As long as this accuracy varies from one photo to another during the flight it could be a good idea to allow us to assign weight to each geo-tag according to its calculated accuracy.
So please enable import of a-priori individual precission for each photo and use them as weights in the adjustment. Thanks

35

Python and Java API / may not be a bug but simply a change

« on: November 03, 2014, 12:06:28 PM »

well I was happy using a python script Alexey published for leveling the bounding box but now it is not working any more with 1.1
Can you tell me what should I change in order to make it right?

Console: Traceback (most recent call last):
  File "C:/temp/reset_bound.py", line 4, in <module>
    chunk = doc.activeChunk
AttributeError: 'PhotoScan.Document' object has no attribute 'activeChunk'

******************************************************Python script********************
import PhotoScan, math

doc = PhotoScan.app.document
chunk = doc.activeChunk

if chunk.transform:
       T = chunk.transform
else:
       T = PhotoScan.Matrix().diag([1,1,1,1])

v = PhotoScan.Vector( [0,0,0,1] )
v_t = T * v
v_t.size = 3

if chunk.crs:
   m = chunk.crs.localframe(v_t)
else:
   m = PhotoScan.Matrix().diag([1,1,1,1])
m = m * T

s = math.sqrt(m[0,0]*m[0,0] + m[0,1]*m[0,1] + m[0,2]*m[0,2]) #scale factor
R = PhotoScan.Matrix( [[m[0,0],m[0,1],m[0,2]], [m[1,0],m[1,1],m[1,2]], [m[2,0],m[2,1],m[2,2]]])
R = R * (1. / s)

reg = chunk.region
reg.rot = R.t()
chunk.region = reg
**********************************************************end*****************************

36

General / Pany GM1 ... banned for aerial! seriously

« on: October 21, 2014, 02:00:14 AM »

Yes, believe me! wonderfull cameras most senses, they're great for terrestrial job. but DON'T EVER put on board of a UAV, just trust me. Don't waste your money. It took me a while to understand why because photos looked beautifully sharp, but even sharpness can hide the worst evil.

Kind regards

GEOBIT

37

General / model lower than ground control

« on: June 24, 2014, 12:48:09 AM »

Hello:
I've done a project (aerial work) in wich an average deviation of -0.07m in dense cloud with respecto to ground control points (targets) is annoying me.
It seems that Photoscan underestimates elevations of all automatic matchings causing an error lowering results by some amount. Note that none of the ground control points exhibits a deviation with the opposite sign, and that makes it unlikely that the error came from a bad adjustment of the bundle block.
In this project all photos suffer from noticeable defocusing due to a bad focus set but they still  appeared to be useable.
Does someone have experienced something like this?

JMR

38

Bug Reports / chunk normals inverted during merging.

« on: October 21, 2013, 05:57:38 PM »

Hi Alexey: I'm testing the beta 1745
I have a project with three chunks. All have been correctly oriented and all dense clouds and models show the right orientation, but the resulting model of a merging command yields to a dense cloud that shows one model (chunks 3) has been inverted without a good reason.
If I switch multiple chunks visible ON, the three originals are right while the merged is partially inverted.
https://www.dropbox.com/s/jj8hrzc9ahcxztp/CHUNK1.JPG
https://www.dropbox.com/s/zqan2dbzjc8dsvr/CHUNK2.JPG
https://www.dropbox.com/s/fqu2ubdd6fz2s0b/CHUNK3.JPG
https://www.dropbox.com/s/97pdrd6w0395ey9/MERGED.JPG
best regards!

39

Feature Requests / scale bars

« on: September 17, 2013, 11:25:27 AM »

1. Exportable to text file just like the rest of ground control actors.
2. Default name should be that of the two markers a scale bar links, for instance "point 1-point 2". A comprehensive link between a scale and the markers it has as end points, should survive to any renaming and/or must be explicit as a property of the scale bar
3. I'd rather prefer the old fashioned tool for picking scales on model window better than choosing two GCP and right click for calling contextual menu.
4. Scale bars could be exportable as segments in some cad formats. That would allow a primitive form of restitution.
Regards! and congrats for my favourite dev.team

40

Feature Requests / bounding box

« on: February 06, 2013, 04:20:42 AM »

• bounding box bottom is too subtle
• once the model is georeferenced, bottom should be aligned to xy plane automatically
• once the model is georeferenced, box rotations about x & y should be locked unless user wanted them free. A contextual menu with lock-toggles for each axis could do while allow panning is not a must here
• render the bottom face differently when is facing up
• ... last but not least. Dear Agisoft team, please, be my heroes!:  Could you please consider using different cursor styles suited to each tool/context?

Best regards
Jos? Mart?nez (Geobit)

41

Feature Requests / lasso selection

« on: November 24, 2012, 05:10:37 AM »

I voted for an irregular form selection tool, so THANKS.
But I just can't manage to do fine with the lasso tool unless you have a very steady hand or a digitizing board instead of a mouse. So I'd be thankful if polygonal selection by entering vertices of a fence was also possible as it works for image-masking

42

Feature Requests / refining markers

« on: November 08, 2012, 10:45:27 AM »

IMHO there is a need for improvements in the gray marker's refining workflow

I hate that they move when I just wanted to validate their current position.

In my opinion, when you click on the marker, you could open a magnifier window with accept and skip icons where the user could reposition the marker by dragging, validate the gray position as is calculated and turn it blue, or skip to close the magnifier letting marker remain in gray status. (Options for magnifier might be: magnification factor, show upsampled and border/contrast enhanced crop, crosshair cursor on button down, automatic target detection by key press... )

Thanks

JMR (was LFA)

43

General / GCP faster (Edited)

« on: November 06, 2012, 10:16:54 AM »

I have not seen this posted before... well may be not that unseen 
My trick to save time when using GPC
1. Align your project without GCP
2. Create blank markers using the right mouse button on the corresponding branch of the object tree. You must create as many as you have in your project. (To save time, I recommend using the same naming scheme for field collection work. (Since pscan 0.9.x you can just go to step 6 as it creates automatically ALL empty markers during import, and then back to 3... sorry, I didn't notice)
3. Choose three of your project GCP that frame your work area.
4. Locate at least two pictures containing each of the three GCP
5. Place markers on each photo selected by using the right mouse button on the image. This makes six unassisted marker placement.
6. (skip if done before) Go to the Control Points dialog, define its coordinate system using the settings button and then import an ASCII file containing: name, x, y, z. for each GCP
7. Click the Update button and observe gray markers for all GCP on their tentative locations.
8. select one marker Filter images by marker and refine the position of each gray marker dragging it to its exact position. Occasionally you can click Update to improve the absolute orientation of the model and thus the remaining gray markers will approximate better to their precise positions.
9. repeat step 8 with all of your GCP.
I hope this hint help you to save some time!

I take this point to suggest AGISOFT team to improve the gray marker's refining workflow. I hate that they move when I just wanted to accept their current position.
In my opinion, when you click on the marker, you could open a magnifier window with accept and skip icons where the user could reposition the marker by dragging, validate the gray position as is calculated and turn it blue, or skip to close the magnifier letting marker remain in gray status. (Options for magnifier might be: magnification factor, show upsampled and border/contrast enhanced crop, crosshair cursor on button down, automatic target detection by key press... )

Regards,

JMR (Geobit.es)

44

Feature Requests / lock bounding box rotations

« on: August 19, 2012, 05:10:16 AM »

I think that bounding box should be optionally liked to ground coordinate system once that absolute orientation is done by means of GCP. Height-field would then be exactly calculated.
My suggestion is to allow user to choose this behavior and also to lock bounding box rotations around x and y so that "gravity" direction kept aligned to z axis ruling the mesh creation as does in the actual terrain modeling. (the third rotation and re-sizing should be kept up to user).
regards and congratulations for last improvements.

JMR

45

General / export points and marker's image coordinates

« on: May 15, 2012, 01:45:08 PM »

I guess there is no way of import/export pixel/image coordinates for feature points nor for markers. Am I wrong?
I think it could be an interesting addition as it would allow us test different feature extraction algorithms or use third party tools to place markers