Latest Contributions by LindsayRaabe_FPCWA

When running a Model Builder tool that contains one of the built in Logical tools (e.g. If Row Count Is), it would be great if the tool still returned the green "Completed" result instead of the yellow "Warning" result due to a precondition not being met. Ultimately, branches of a model can both be valid results, but you will always get a "Warning" because one of them didn't run. It would be preferable if the overall model result was still in it's "Completed without warnings" state to prevent user confusion. Warnings should be reserved for unexpected outcomes (e.g. emtpy datasets when you expect data to have been generated). In my example model below, you can see a perfectly legitimate tool with 2 differnt Custom Message options will always return the Warning result.    ... View more

When downloading offline areas in Field Maps, it would be useful to see how long an offline area has been on the device. Over time, areas can become more unstable and users may want to remove and download new copies to recieve changes made to the map since it was downloaded.  IDEA: Include a datestamp value showing when the offline area was created/downloaded in addition to when it was last sync'd.      ... View more

When using Field Maps, the screen timeout is annoying when using Field Maps for navigation whilst driving. It's one of the most common questions/complaints/requests we get from users who have shifted from using older (and more basic) apps like OziExplorer which keeps the screen on by default. This is especially important when using your device whilst driving and you're legally not supposed to interact with the device while operating the vehicle (an in lieu of the Apple Car Play/Android Auto requests still not being implemented).  IDEA:  Implement a manual toggle switch (at the top of the screen?) to permit the user to keep the screen on if desired, or; Permanently disable the device screen timeout settings when using Field Maps so that it is always on unless you press the devices lock screen button.  ... View more

So, somehow I've managed to survive for years without coming across this issue....until now! The Statistic fields in Dissolve and Pairwise Dissolve do NOT honour "Create multipart features" option in these tools. If you leave "Create multipart features" unchecked, and are dissolving 3 polygons where 2 are adjacent and a 3rd is not adjacent and all contain an ID value to be concatenated as a Statistic field (e.g. A and B adjacent with C not adjacent), instead of producing 2 output polygons with a statistic fields that shows (polygon 1) A/B and (polygon 2) C, you get 2 polygons but both contain A/B/C in the concatenated field (as if they were a multipart polygon)! Visual example below (more reading here too).    IDEA: Include an option (second checkbox or other method) to control whether the statistic fields should be calculated as per the singlepart output or original multipart functionality. Bonus points if it's enabled by default!   P.S. Please update the documentation and tool tips of these tools to clearly state how these things work!    ... View more