Latest Contributions by TonyViveiros

‎06-08-2020

Yes...the Classify LAS By Height tool. I've created a LAS dataset from UAV processed aerial imagery (Pix4D). I've classified the ground (using Classify LAS Ground) and would now like to use the Classify LAS By Height tool to classify vegetation (regenerating trees) as low, medium or high vegetation (LAS codes 3,4 and 5). However, it's unclear to me what units the height_from_ground values in the Classify LAS By Height tool uses.

‎06-08-2020

Hello, How is the height unit (e.g. m, cm, ft, etc.) specified within the Classify LAS By Height tool? Thanks. Tony

‎09-09-2019

Hello Owen Evans‌. Is is fair to say that the ability to publish the new ArcGIS StoryMaps to groups will exist before mid-2020, when the ability to use the classic Story Maps templates ends? Thanks. Tony

‎07-29-2019

Thanks Owen Evans for pointing out that additional approach to sharing the new ArcGIS StoryMaps with AGOL groups. Most folks where I work, including myself, lack the permission to share content with the organization or externally with everyone. So, if you're looking to improve StoryMaps capabilities, I would suggest also adding the ability to publish to AGOL groups. Tony

‎07-26-2019

I managed to figure this out. You can share the new story map types created with the new builder to an AGOL group by selecting the check box in the AGOL contents for that story map item. Doing so brings up the Share icon which you can then use to share the storymap with AGOL groups.

‎07-26-2019

Is sharing a 'new' ArcGIS StoryMap with an ArcGIS Online Group possible? If not, is this functionality expected soon? It seems sharing story maps created with the new builder is possible only with the Organization and publicly. Tony

‎05-21-2019

Hi Philip, Thanks for the explanation. I can understand how storing data in not relevant questions would be be a problem and considered a bug. Tony

‎05-17-2019

Thanks for the tip Doug. That worked. Tony

‎05-17-2019

Hello Philip, I don't quite understand why this functionality was considered a bug. I've written the url scheme to pass the parameters from collector to s123 because I wanted those values to get stored in the feature service. My survey is a lot more cluttered now because this ability was removed. For example, we have a check s123 workflow that is used to audit forest renewal assessments. With a previous release of s123, the auditor would identify the trees on the site being assessed and compare those against what was originally assessed. Doing so only brought up the original surveyed tree numbers (passed via url) and a question for the auditor to record their tree numbers for the species selected. Now I have to show all originally assessed tree number values up front as partially illustrated below. This complicates the survey as most of the time only a few species exist at the site yet all these 0 values now get displayed on the survey for trees not present. This workflow is further described in the following ArcNorth News story. Any suggestions on how I could simplify my survey to the way it was previously when this 'bug' existed? Thanks. Tony Viveiros

‎05-16-2019

Hello...is passing field parameters from Collector to S123 no longer possible for fields with a relevant expression? This no longer works for me. I also checked previous surveys that worked but now do not (I haven't changed anything). I'm using S123 3.3.64 but also tested with 3.4.96 without any success. Thanks.

‎05-16-2019

Hello...is passing field parameters from Collector to S123 no longer possible for fields with a relevant expression? This no longer works for me. I also checked previous surveys that worked but now do not (I haven't changed anything). I'm using S123 3.3.64 but also tested with 3.4.96 without any success. Thanks.

‎01-13-2015

The current 10.2 release of ArcGIS Diagrammer does not work with ArcGIS Desktop 10.3 and will be the final Diagrammer release according to the link here. ArcGIS Diagrmmer functionality is needed for ArcGIS Desktop 10.3.

‎01-07-2015

Topology rules that check for 3D issues in feature classes with z-values are needed. For example, '3D gaps' that exist in polygon data because of vertices with differing z-values are not identified with existing 2D topology checks. Additionally, 3D polygon features without any 2D topology problems (e.g. gaps and overlaps) can exist on different planes because of differing z-values. 3D topology checks that identify these types of issues in 3D data would be useful.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by TonyViveiros

Re: Classify LAS By Height Units

Classify LAS By Height Units

Re: Sharing ArcGIS StoryMaps with Groups

Re: Sharing ArcGIS StoryMaps with Groups

Re: Sharing ArcGIS StoryMaps with Groups

Sharing ArcGIS StoryMaps with Groups

Re: S123 Custom URL Scheme and Relevant Expressions

Re: S123 Custom URL Scheme and Relevant Expressions

Re: S123 Custom URL Scheme and Relevant Expressions

S123 Custom URL Scheme and Relevant Expressions

Re: Understanding Survey123's custom URL Scheme

ArcGIS Diagrammer Functionality for ArcGIS Desktop 10.3

3D Topology Rules and Checks

Re: Sharing ArcGIS StoryMaps with Groups

Re: Sharing ArcGIS StoryMaps with Groups

3D Topology Rules and Checks

ArcGIS Diagrammer Functionality for ArcGIS Desktop...