Latest Contributions by RyanKelso

I have run into this issue as well, trying to update geometry on some features. I tried using as many methods as I could think of to limit the input data to a subset: an expression within the tool dialog, a definition query on the layer, a selection on the input dataset, and a selection layer. None of these worked. My workaround is to run Export Features, set the expression in the tool dialog, and output it to the temporary "memory" workspace, then use the temporary feature class with the Append tool. This works but it's an intermediate step that shouldn't be necessary if the tool worked how it's supposed to.

‎04-16-2021

Updating an app to WAB 2.19 with eSearch 2.17 and I don't see the "Limit search to map extent" checkbox. I figure there's probably a config option for it, but if there is, I'm not seeing it. Am I having a huge 'duh' moment here and missing something obvious? I removed the following from style.css to get it back but feel like I might be missing something. .jimu-r-row.play-section .col-2-3 { display: none; }

‎02-11-2021

It's a feature that some people want and there's nothing wrong with that. The problem is poor (lack of) support/implementation in the API because it's one of those things all-knowing esri doesn't think you need. The solution is a bit hackish because of this, but custom implementation is possible on a layer-by-layer basis if you are ok with using feature layers, which is a problem because IMHO they are not a fully mature feature.

‎02-18-2020

I'm glad you're back, Tom. We love your widget. Thanks for pushing out a new version!

‎11-06-2019

That's too bad about the weighted area algorithm, Mike. Frustrating. I came to the same conclusion that this was broken after the 10.4.1 release. I found a bug report BUG-000123000 that indicates this issue has been fixed for version 10.8. Hopefully they fixed whatever the underlying problem is because I also encountered it with the Contour tool and suspect it's not limited to these two tools only. It's not difficult to resent Esri for their cycle of breaking existing features, letting them fester for a few years, forcing users to upgrade to the latest release if we want fixes instead of releasing patches for older versions, and leaving us to find the next round of broken features... the cycle repeats.

‎09-17-2019

I have encountered this same problem with the out of memory error. I'm also building contour lines and trying to run Simplify Line to shrink the files at get rid of unnecessary vertices. The thing is, I went through this exact same process six years ago, and the tools ran without a hitch. That would have been ArcGIS Desktop 10.0 or 10.1 with hardware that is more than six years older than the hardware I'm running on today. No cartographic partitions, no dicing up lines or setting a max number of vertices per feature, it just worked. I've tried this with ArcGIS Pro 2.4.1 and Desktop 10.6.1. It's not just Simplify Line that is getting the error, the Contour tool is also getting the error in some cases. I've not gotten the error with any other tools. My process already incorporates smoothing the DEMs before building contours by using resampling and filtering functions. Actually this time around I am using ArcGIS Pro's Contour function with its Adaptive Smoothing, which I definitely recommend over using a standard filtering operation. This led me to trying it on some older installations of ArcGIS. On one machine running Desktop 10.5.1, I ran into the same out of memory errors. On another machine I tried 10.2.2 and 10.4.1 and was able to successfully complete the processes that were failing on the other machines running newer versions of ArcGIS. None of the machines were ever actually close to running out of available memory.

‎08-23-2019

I came here to create an idea for this exact enhancement but unsurprisingly Kevin "Mr. Everywhere" MacLeod beat me to it! It's come up a number of times with our users, I think people intuitively expect that the app state would also include their favorite basemap. I hope the web appbuilder team eventually sees this.

‎05-24-2019

I'm trying to setup a search expression using the IN operator and configure it with a pre-determined list of values, but I can't get it to work. If I enter the values like so: CC,RRC-R10000,RRC-R.5,RRC-R1,RRC-R2,STMU,STR-4 -- then the search expression ends up like this: ZONE IN ('CC,RRC-R10000,RRC-R.5,RRC-R1,RRC-R2,STMU,STR-4'). If I enter the values like so: 'CC','RRC-R10000','RRC-R.5','RRC-R1','RRC-R2','STMU','STR-4' -- then the search expression ends up like this: ZONE IN ('''CC'',''RRC-R10000'',''RRC-R.5'',''RRC-R1'',''RRC-R2'',''STMU'',''STR-4'''). Has anyone tried setting up a search like this an gotten it to work?

‎05-10-2019

I forget... is there a way to configure eSearch so it will return a number of records that exceeds the "Maximum Number of Records Returned by Server" set in the map service? Or is that accomplished only by increasing that cap in the map service properties?

‎12-12-2018

In Web Appbuilder's Search widget, I would like the option to disable suggestions for feature layer search sources. I have mine configured with a parcel layer and not only do I find the suggestions unnecessary, but it makes multiple costly requests to the server as I type in the parcel number. Ideally, this would be an option that could be set on each search source individually.

‎11-27-2018

I was thinking mostly about the clipped geometry issue as the more serious problem, which if what you said is true that it's a known issue with newer versions of the API and Chrome, I don't see the point in reporting. They'll bother to fix it or they won't. And you're right, GeoNet is a community of people, which includes ESRI Staff, who sometimes graciously step in and offer help as well, and I like to think they at least read some of this stuff even if they don't respond. My experiences have made me cynical about contacting ESRI support, I avoid it unless I feel like it's my last hope. I think anyone who encounters a problem they see as serious enough to pursue fixing, would be smart to generate as much exposure to ESRI eyeballs as possible, including opening a support case, using the Ideas site, and posting here on GeoNet.

‎11-26-2018

Thanks again, Robert. That is basically what I was after in the beginning to fix the 'clear' button. I'm going to go ahead and mark this discussion as answered, however I think the 'real' answer to this would be for Esri to acknowledge and commit to fix these issues with their widget and API because measuring is a core feature for many GIS apps/users and these sort of issues should be ironed out.

‎11-21-2018

Thanks Robert that is super helpful. I've taken that change a step further and made the 'Clear' button disappear when it is disabled. And you're right, the clipped geometry issue doesn't look like it is there in FireFox. For the people who are getting really frustrated by that problem I'm going to try setting them up with FireFox. Hopefully either Esri or Google fixes the problem eventually.

‎11-20-2018

Yes, it is my own service with my own templates. I'll give the script tool in ArcMap a shot and see what I can find out. Does "Whitespace is not allowed at this location" mean anything to you? Like, do you know if this means something specific I should be looking for? Thanks again for helping me along with this.

‎11-20-2018

I've noticed some strange behavior with the standard Measurement widget, I wonder if others have noticed at least some of these things and they might get addressed. Clicking the 'Clear' button while you have an active measurement (before you double-click to finish) causes some buggy behavior when you start another measurement. It will include the final point of your previous measurement, and if you double-click to finish, it will draw all of the geometry from the previous measurement, though it does not include those distances in the measurement total. Also while this is happening, the measurement totals are not dynamically updating as you move your cursor. I think it should be fixed by either making the 'Clear' button do nothing until you have double-clicked to finish your measurement, or have the Clear button delete any remnant of the previous measurement. It also wouldn't hurt to have some indication (a tooltip or message on the widget window) that you should double-click to finish your measurement, since this is not always obvious to less GIS-savvy users. The other main issue is that there are some actions that cause the measurement geometry to become clipped and invisible while you are actively measuring. The easiest way to see it in action is to start a measurement and continuously pan the map as you are measuring. Sometimes continuing to click your measurements (or finishing) will cause the geometry to appear, sometimes not. It seems like other actions will trigger this behavior but I haven't been able to isolate them. I've noticed this in other widgets that use draw tools. It appears to be an issue with more recent versions of the JSAPI, I can load up an old v2.1 WAB app and can't duplicate the problem.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by RyanKelso

Re: Expressions Not Being Honored By The Append Tool

Re: Enhanced Search Widget Version 2.17 - 12/11/20

Re: Hover instead of click popup in WAB

Re: Measure Widget 2.15 for Web App Builder

Re: Simplify Line Tool throws Out of Memory errors at under 25% usage

Re: Simplify Line Tool throws Out of Memory errors at under 25% usage

Re: WebApp Builder 'app state' does not remember what Basemap was selected

Re: Enhanced Search Widget Version 2.13 - 09/25/19

Re: Enhanced Search Widget Version 2.13 - 09/25/19

Search Widget - disable suggestions

Re: Buggy behavior with Measurement widget

Re: Buggy behavior with Measurement widget

Re: Buggy behavior with Measurement widget

Re: Occasional problem with custom text in Print widget

Buggy behavior with Measurement widget

Re: Expressions Not Being Honored By The Append To...

Re: Delete Features - Reset OBJECTID?

Re: Manage tile cache, anti-aliasing

Manage tile cache, anti-aliasing

Re: Cached map service without Server access to da...

Web AppBuilder Custom Widgets