Hi All,
I flew a M3E smart oblique mission (nadir + -45° and -135° obliques) for a 350+ acre site. I know I could cut this into smaller missions in the future, but I really need to process this data.
This mission was flown in two overlapping perpendicular lawnmower patterns, so I can't just break this up by the sequence they were shot. Is there any way to process this many photos as one map, or to process just the locations of them and then select what I want to be rendered?
Thanks in advance!
John
DO NOT DO THAT. I don't know where people starting thinking this was a good idea but we are going to add filtering to the uploader to not allow it.
This setting, whatever app is enabling it, creates way too much overlap and makes the processing times take forever. It is expensive for us and expensive for you. And it sucks.
If you want to look at that data put it into TerrainDrop or something.
댓글을 남기려면 로그인하세요.
Hey Zane,
It's clear from your reaction that 5,800 images in one dataset is extreme, or simply not feasible from your perspective. The reason for my post was that I know it's larger than a typical dataset, and I can see that you have defined a 4,000 image limit to the DJI workflow and a 5,000 limit to the Classic workflow. I haven't seen any explanation of why you chose those limits.
As someone who's not a programmer, nor an administrator of a cloud-based platform for processing, I do not know the complexities of this type of processing. All I know is what clients ask for. I rely on the kind folks like you who represent this type of paid software service to help me.
Thanks for the recommendation of TerrainDrop. Unfortunately, they support even fewer images per dataset than MapsMadeEasy (only 2,000), so I'm not sure if it will be useful in this case.
Can you offer any other constructive suggestions about how to solve this problem?
Anyone else in the community know of other software that could help?
Thanks!
John
The 5800 isn't a problem. We simply don't support that. We only allow up to 4000 images to be uploaded at one time.
The thing we have been seeing all the sudden that is problematic is this look forward and look back data collection.
You could probably just process the straight down images from that dataset and have not issues with the outputs. It would be one third of 5800.
