POST
|
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
06-27-2025
01:03 PM
|
0
|
1
|
582
|
POST
|
I'm getting the same issues this morning. I don't think it's a "you" problem.
... View more
11-05-2024
12:01 PM
|
0
|
0
|
570
|
POST
|
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
09-11-2024
03:45 PM
|
0
|
0
|
1846
|
POST
|
Are 360 images ONLY supported through oriented imagery?
... View more
02-29-2024
08:33 AM
|
0
|
1
|
946
|
POST
|
08-10-2023
09:19 AM
|
0
|
0
|
734
|
POST
|
Good Morning, I have a Survey123 form that has been in use for about 3 or 4 years, mostly with no issues. Part of the form includes the weather.js script provided by @IsmaelChivite in a blog post (this is a more recent blog post. I can't find the original one I used when javascript functionality was first added). Some time within the last month, some users (myself included) noticed that the weather data was no longer being included in the generated feature reports. After some digging, I noticed: * The fields that the feature report draws from are empty when viewing the feature service data page: Even though the data is present on the mobile form when submitting (Verified on 3x different devices. Also, the presence of the value in "Weather" column in the screenshot above shows that at least that field is working, which runs off the same script and pulldata functions) Odd behavior noted: The users/devices that have values not being submitted to the feature service can be identified ahead of time here. The group header/summary reports the field values, if available. Some users, like myself, do not see the field values here: Others do. The people that can see the values in the weather summary are the ones where the values are actually being submitted (everything works as expected) Hand-entered values work as expected and are submitted to the feature service (deleting the calculated value and then clicking the recalculate button does not work, however) : And here is how the values are calculated for the fields: And the summary: Any help would be appreciated. I assume it has something to do with a calculate setting. If you look at the screenshots of the mobile form that works vs the one that does not, the text color of the fields is different. If I remember correctly, that has something to do with an auto-calculate/re-calculate setting, but it's been awhile since I messed with that. It is odd that they are different on different devices though, since everyone is using the same version of the form. Thanks.
... View more
08-10-2023
09:04 AM
|
0
|
1
|
774
|
POST
|
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. derrick.westoby@pbsusa.com 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
07-19-2023
09:07 AM
|
1
|
0
|
813
|
POST
|
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
12-13-2022
09:10 AM
|
0
|
0
|
2206
|
POST
|
Left work yesterday with no resolution. Came in this morning and everything is working again. I wish the lawn would mow itself while I'm asleep, too.
... View more
11-16-2022
08:32 AM
|
1
|
0
|
828
|
POST
|
In the process of lighting some candles and looking up the chant to summon @Anonymous User the log file whisperer.
... View more
11-15-2022
12:48 PM
|
1
|
0
|
865
|
POST
|
Good Morning, I have a survey that's been up and running for about a year now, and I haven't made any changes to it for a couple months. The last successful submission was yesterday. As of this morning, all users are getting an "operation rolled back" error when trying to submit. Log file is attached, but I'm not used to picking through these and nothing is jumping out at me except this (which I'm not sure how to address): { "code": 1003, "description": "Operation rolled back.", "tableId": 0 }, { "code": 0, "description": "Invalid object name 'user_20440.service_62b31b57ac52464886b44afbab1d82df_GENERAL_NOTES__ATTACH__tracking'.", "tableId": 1 }, { "code": 0, "description": "The INSERT statement conflicted with the FOREIGN KEY constraint \"FK_service_62b31b57ac52464886b44afbab1d82df_GENERAL_NOTES_5DE05BDC\". The conflict occurred in database \"db_20440\", table \"user_20440.service_62b31b57ac52464886b44afbab1d82df_GENERAL_NOTES\", column 'globalid'.\r\nThe statement has been terminated.", "tableId": 1 } ] Any help would be greatly appreciated. Thank you
... View more
11-15-2022
12:16 PM
|
0
|
2
|
874
|
POST
|
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
08-09-2022
01:13 PM
|
3
|
0
|
3004
|
Title | Kudos | Posted |
---|---|---|
1 | 06-25-2025 01:37 PM | |
1 | 11-18-2021 11:59 AM | |
1 | 08-06-2019 07:41 AM | |
1 | 11-16-2022 08:32 AM | |
1 | 11-15-2022 12:48 PM |
Online Status |
Offline
|
Date Last Visited |
07-11-2025
11:41 AM
|