Show Posts

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

Messages - orellius

Pages: [1]
General / Re: [resolved] Orthophoto export Google Earth KMZ red X
« on: December 04, 2018, 01:55:21 AM »
See up top, I just resolved this myself by updating Google Earth, now the ortho loads in just fine.

General / Re: Orthophoto export Google Earth KMZ red X
« on: December 04, 2018, 01:41:34 AM »
Yes thanks, I will send it ASAP. 100 MB file but ill use our company's file sharing service and send a link, referencing this forum post.

General / [resolved] Orthophoto export Google Earth KMZ red X
« on: December 03, 2018, 10:47:26 PM »
EDIT: I've resolved this myself just by updating to the latest version of Google Earth Pro. Mine was a version from July 23, 2018. Now I am on October 31, 2018.

I've done my own internets searching and even on this forum, I know there are some posts about it before but none seem to help me at all.

I process UAV survey flights and export ortho in KMZ. If I open in Google Earth it's just a red X. This never used to be the case, it always worked for me, but I've had this issue for a little while and have no idea with what version upgrade it broke and stopped working.

I do not believe it has anything to do with my PC hardware limitations, and also nothing to do with the actual dimensions or size of the KMZ file. When this WAS working, I was able to successfully load KMZ files in that were 100 MB, 1 GB, and even more. Yes, larger ones might take a bit to load but they always worked. Now, I can't get any of them to work.

I've taken suggestions that I've found online and have had no luck. The file I'm trying to open today is only 100 MB. But I've also drawn in a polygon boundary and shrunk the area to a very small region 5 MB file, and no luck. I've tried exporting the entire region but changing the pixel density to 10cm (down from 1.5 cm) and still get a red X. Essentially no matter what actual boundary dimensions, file size, or pixel density, I get a red X.

I've also tried turning off the "save network links" and some of the layers in the KMZ file itself, as suggested online and on this forum, and no luck. What am I missing? I used to be able to provide KMZ files to all my clients, now I cannot.

thanks for any help

General / New 1.4.0 datum transformation options help
« on: February 02, 2018, 07:30:49 AM »

I've spent many hours troubleshooting what the heck is going on, I was about to report this as a bug but it might not be so I came here. Might be a new feature, that is just going to bug me!

To start with, I'm no Geomatics Engineer, but I've been working for various geomatics/survey equipment resellers for almost 15 years so have a pretty good understanding, just looking for help.

Been using Photoscan Pro a few years. Ever since before 1.4.0 I could either generate a DEM/ortho in UTM or 3TM inside Agisoft, and view it there, and do GCP checks,  fly my mouse over the ortho and check coordinates/elevations, etc. Then I could export in UTM/3TM and import to other software and everything was just as accurate as it was in Photoscan.

I could also generate DEM/Ortho in WGS84, and at the export stage choose UTM/3TM, and again have no issues importing to other software and it still being in the right place.

Now in the newest build of 1.4.0, I can no longer generate it inside photoscan, in just for this one example, NAD83(CSRS) 12N (EPSG 2956). If I do so, all the data is shifted by up to a meter in XYZ. See screenshot included showing the difference in GCP checkshots compared to the surveyed coordinates. It shows the difference table as well, which is consistent across the board.  Notice though the accuracy Photoscan is reporting for my checkshots and photos, which is good. This has worked fine for years, now it doesnt. If I export this same data in Photoscan 1.3.5 my data is accurate.

I've narrowed it down to something relating to the new export options for datum transformation, but I dont know enough about that part to know what is actually happening. The problem I see is I figured out how to actually export the data properly (only if I generate it in WGS84, then export it). I have to choose an advanced export option (see screenshot). It is defaulting to EPSG:1946 at export which has a shift/rotation. If I choose "none" if gives an error. If I choose EPSG:1842 it has zero shift/rotation and my data is good. This advanced button didnt exist before, now it does and it defaults to something I don't want. On top of that, It seems to be defaulting to this if you generate your data in EPSG:2956 in the software, so it's shifted and rotated in the I'm forced to view it in WGS84, then export it elsewhere.

  • Problem 1 is why does generating in EPSG:2956 (and maybe others?) for viewing INSIDE Photoscan have a new shift/rotation that it did not have before, and how do I stop it from doing that?
  • Problem 2 is why is this new version now defaulting to this option at the export phase when going from WGS84 to grid?

It's like my goto option is totally broken now, and my backup plan to do in WGS84 then export elsewhere has an option defaulted that I don't want. Kinda sucks!

Again keep in mind I don't fully understand the new EPSG codes at the export datum transformation option. Honestly it took me hours just to see the new button was there...I hope this is unintentional and will be addressed. I think it should default to what it was before, leave the advanced options for those who want to play with them! 

General / Re: Reducing file size of Orthomosaics
« on: January 05, 2018, 12:31:04 AM »
Sorry reviving this old topic. I've searched around and can't find answer. There's multiple mentions on Agisoft forums of people recommending ECW format for smaller size orthomosaics. But I can't for the life of me find how to export one in that format, PhotoScan doesn't seem to support the file at export stage.

Is this even a feature or are people using some other software to convert to ECW?

General / Re: Large GeoTIFF hangs Windows Explorer
« on: January 04, 2018, 09:42:57 PM »
You sir, are the G.O.A.T.! Even though you did not solve the problem, you lead me right to it. I tried the thumbnail settings and that wasn't it. It made me think though, I had Windows Explorer set to have the "details pane" open, so on the right side you see a preview of items selected. Just simply touching a GeoTIFF freezes it. If i turn off details pane, I can do whatever the hell I want with them with no freezing.

As I mentioned this plagued me for years. For a while I had the issue. Then it went away for a while. Then it came back. Went away, came back, lol. It's because I had the details pane on for a time, then off, then on. haha

Cheers!  :D

General / Large GeoTIFF hangs Windows Explorer [solved]
« on: January 04, 2018, 08:06:24 PM »

I've been having this issue for a couple years and never found a solution. I've scoured the interwebs on several occasions and did find a bunch of people having the same issues, with TIFF files, but all of them are old cases and only involve people on Windows Vista and Windows 7, for which Microsoft released a patch, but that does not affect Windows 10.

I'm certain some of you have seen this so I'm hopeful someone has a suggestion.

Agisoft Photoscan Professional + Windows 10 x64
HP Zbook 17 G2 | 32 GB RAM | Core i7 | SSD drive(s) | Quadro K5100M GPU

Large GeoTIFF files tend to hang/freeze Windows explorer. Like if you browse to a folder with TIFF images, just simply clicking your mouse (single click) to select the TIFF, it hangs Explorer, becomes unresponsive for quite a while. Trying to select a group of them with dragging a box around them, hangs explorer. Trying to drag them to another location, say to copy them somewhere else, hangs explorer, basically ANY interaction with it hangs explorer.

By "large" TIFF files I mean under 4 GB, I use the auto-split in Agisoft at the export stage and it breaks them down in to sections of varying sizes, typically 500 MB to 2 GB because Windows does not like greater than 4.5 GB TIFF. Well it seems to not like smaller ones either. These are orthomosaics from UAV mapping.

I'm actually thinking this is a main reason I have lag issues scrolling in/out in Global Mapper software, which I am currently evaluating before purchase. Loading these same TIFF images into that software provides a non-smooth experience when zooming in and out. Might be associated with how Windows is dealing with the files in the background. Internet research points to paging file settings (which I've tried), how Windows is allocating memory when interacting with the files. But all of this is relating to Windows Vista, and no patch or user cases I found of people discussing Windows 10.

Any thoughts?

Thanks in advance!

Bug Reports / Re: Photoscan 1.3.3 & 1.3.4 problems
« on: December 08, 2017, 07:23:55 AM »
In the meantime a download link to v1.3.2 might help, I don't seem to have mine now and it worked fine before these versions.

Bug Reports / Photoscan 1.3.3 & 1.3.4 problems
« on: December 08, 2017, 07:23:06 AM »
Ok I'm 90% sure these problems did NOT exist in 1.3.2, but only in 1.3.4 and 1.3.3. However, unfortunately, I deleted my 1.3.2 installer and I can't find a replacement that isn't a torrent hack or something that I don't trust, so I can't downgrade and go back and check.

I ran 1.3.2 for a long time because when I installed a newer version I ran into this issue where I process the photos (align) and point cloud in WGS84, then process the ortho/DEM in UTM/3TM (UAV data) and I can't zoom in on or even view the ortho or DEM. I can double click the point cloud, zoom, pivot, fly around, no issues. But the DEM or Ortho if I double click, nothing is there on the display. If I double click the DEM and the screen is blank, also so is the menu bar, it literally disappears. Screenshot attached. I highlighted in the screenshot the totally blank toolbar. I tried re-processing the DEM/ortho in WGS84 and it's still blank. So I don't think it's a UTM/CSRS projection issue. I think it's a version issue.

It's funny because the toolbar completely goes blank, only if I double click a DEM or ortho. At that point the software is unresponsive totally to mouse scrolling (zooming) and clicking on the toolbar, the only thing to bring back software response and the visible toolbar is to double click back on the dense cloud, then I have full zoom/pivot and the tool bar. Other than that the software is unresponsive.

I also investigated the forums and searched, and found some topics that somewhat resembled my issue (though not exactly the problem) and the solution was to update drivers or run the "-- opengl angle" on the exe and that didn't seem to help. Drivers are updated, etc.

I know for a fact that I tested this before. I have 2 hard drives on my laptop, 2 separate installs of Windows 10. One was running v1.3.2, other was upgraded to 1.3.4. If I opened the same project in 1.3.2, no issues. If i opened in 1.3.4 on other hard drive, I could not see or zoom on the ortho or DEM. I had since, and some point, upgraded to 1.3.3, and now I dont have 1.3.2 to test, and still have the same issues. For a few months I was avoiding updating due to the issue I saw. But now we've sold some more UAVs and have customers downloading trial Photoscan software and I'm still having issues. So are they.

I am the pilot and demo person for a large UAV reseller and soon to be Photoscan reseller, hoping for a fix soon. I had zero issues for almost 3 years, now the software is unusable. 

HP Zbook 17 G2
512 GB Samsung SSD
i7 CPU
Quadro K5100M GPU

General / Re: CPU and GPU benchmarks
« on: January 15, 2015, 04:50:52 PM »

General / Re: CPU and GPU benchmarks
« on: January 13, 2015, 09:30:09 PM »
Is there any new word on the GTX980's? I just see that one user had success, and some were going to be doing some benchmarks. Anandtech doesnt seem to have GPU on the charts for Photoscan, just CPU.

Anyway, I am spec'ing out a workstation for the company and am looking at 2-3 GTX980's, or 2 K6000, or 2 TITAN. (with 64-128 GB RAM, and 1-2 Xeon's)

Just need to know if there are any known issues. Any suggestions as well?


Edit: I forgot to include links, my comments are in reference to multiple threads (one on the new GTX cards, and one on the 1.1.0 pre-release testing, and thought I would post it in the benchmarks thread)

Pages: [1]