Latest Contributions by DerrickWestoby

I think it might be related to custom symbology in the reports.   I had reports failing that were using this:  ${location_general | drawingInfo:"currentLayer"| mapSettings:" b2519fd7a45647a0946f50b0535b6ddd":36000| size:175:250:0:0}   And they started running fine when I changed it to this: ${location_general | mapScale:36000| size:175:250:0:0}   Curious if the same is true for others here?  ... View more

Same here. all reports failing ... View more

I'm getting the same issues this morning. I don't think it's a "you" problem.  ... View more

Osama - Is there a way to filter dlpk that are meant for orthoimagery vs lidar point clouds?  It looks like they're all in one bucket in living atlas?  ... View more

Same here.   The issue seems to be resolved ... View more

Are 360 images ONLY supported through oriented imagery?  ... View more

Any & all autonomous dock options.   ... View more

Hey Kevin,  I do some work like this (also with the M300 & P1) and the approach I take can work for quick/low-effort identification of areas, or more involved quantification.  The actual analysis is done by our water resources department, though.   As long as the erosion is visible in the Z/elevation axis, you can create a derivative DEM by calculating the elevation difference between two temporal DEMs.    You can do this with the digital surface models (DSMs) directly from your photogrammetry software, and could have something to look over about 15 minutes after processing of your 2nd temporal dataset is done.  You're going to see a lot of noise and erroneous areas if you're using DSMs, especially next to water features and if there's vegetation present, but it's such a quick process and useful visual that I do the same thing for a lot of our construction projects.     If  you need to quantify the erosion though, you'll need to do some cleanup (and lidar likely would help this, depending on the site).  Again, that's assuming you can detect the erosion in the Z axis.  I don't know of any way to auto-magically identify it in the XY axis, but I'm looking forward to reading other replies and suggestions to your question.   If you have data from two different flights over the same area, I'd be happy to give you a quick step by step over a screenshare.  [email protected]    edit:  I forgot I posted a quick script for this on the global mapper forums, if you want to try.  In the post I talk about how I use it to check derivative surfaces for erroneous points or missing breaklines before finalizing, but it's the same idea for quick identification of change.   I don't have any hydro projects on the computer right now, but here's an example on a new subdivision.  On-site features of interest that have changed are easy to identify visually, and the noise is simple to interpret and ignore.     This isn't a deliverable, this is just what I see when I quickly interpret the "Elevation Change DEM". I ignore areas like "grass mowed" and "car", and focus on areas like "sidewalk", "stockpile" and "home" when updating survey drawings.     On a hydro project, I'd use this to quickly identify areas of interest (erosion region candidates), then I'd work on cleaning up the data and building a true DTM in those areas to quantify the change, before sending on to WR for analysis.  ... View more

Thanks Jimmy, this fixed the issue for me.   The problem did start about a week after using "Optimize Layer Drawing" setting, but method=vertex still didn't work after disabling, it, pushing an update and trying a new submittal.  removing method=sketch from the geoshape question works fine now.   ... View more

In the process of lighting some candles and looking up the chant to summon @Anonymous User the log file whisperer.  ... View more

I have about 10-20 surveys going through Integromat/Make a day now.  This error (on established surveys and feature report templates that haven't changed in months) is one of the ~10 errors that pops up regularly that's always fixed by re-running the report generation.  If it's not resolved, I'll wait 20 minutes and run it again.     I know that's not exactly a "solution", but I'm just trying to point out that it might be a server side issue that will self resolve.  I added a sleep module between the webhook and report generation hoping the issue would resolve, but that doesn't seem to have changed anything either.   Long story short - make sure it's not a server side issue before you spend 3 days troubleshooting.    Failed -    The 10:15 run that threw an error is the screenshot above.   10:19 was after restarting the scenario.  No changes to report template, feature service, survey submission, etc.  successful    ... View more