Latest Contributions by Mike_Koutnik

When using an Experience Builder Filter Widget users often wish to select based on a range values of a string field. For instance, they may want to select those features with a name field value that starts with a capital alphabetic character of at least "A" and no more than "Z, or "between A and Z." To accomplish this, it would be very helpful to have string operators of less than, greater than, at least, at most, between and not between. This would also be very useful when filtering on codes, categories or types that start with a few characters that specify a broader category, and additional characters that differentiate between sub-categories. In a variety of these use cases, the data must be filtered in the form its supplied. Transforming the data into a more structured form that would establish domains and subtypes isn't an option. ... View more

I often find it very convenient to review and edit layer attributes right in the table the Data tab in item details. I usually only need some fields, so I hide the others. And I often need the fields in different order than in the attribute table. So I drag some fields, in a current situation, from the far right to the far left. Then I'm ready to go. The frustrating part is that this"configuration" of the table view doesn't persist. Even if I'm away from my laptop for a bit and the machine goes into sleep mode, the table is reset and I have to repeat the configuration again. Please add a capability to "save" the current table layout, and allow one to "check" an option to reapply that each time the table is opened. A reset option would also be helpful. Related to this request, it would be very handy to allow drag and drop placement of fields in the field visibility list. And also those layout changes to "stick" across uses of the Data tab for that layer. When one has to move several fields, with numerous fields in the table, that is another big time and frustration save.  One other enhancement relates to this use case. If one has a field whose width in the table is less then the width of some of its contents, the contents will wrap. All good there. But when I scroll to the right, and there are only fields that don't need to wrap, the row height snaps back to "normal." One might think that's a good thing, that more rows can be presented in less space. But often when this happens, the row I selected gets scrolled well upwards beyond the current visible rows. It can be difficult and frustrating to find it again. And then when you scroll back to the left, the opposite occurs. The selected row is now somewhere below the visible rows in the table. More frustration. My request is that if ANY fields in the table are being wrapped,  the same row height should be maintained regardless of whether there are any wrapped fields in the current set of visible columns. Thanks. ... View more

It would be very helpful to have general settings for display of popups, rather than just whether a popup is displayed in a particular slide. The settings would be: 1. Whether popups should automatically be docked on first presentation. This would make for a consistent presentation of popup content and map content across throughout the range of features to be visited in an exhibit configuration. 2. Where to position the docked popup when opened: either upper right (as happens on the Exhibit app now), or upper left (as happens in web maps). Upper left what works best for my use of bookmarks in web maps that drive initial creation of slides in an Exhibit config. These two settings, together, also make it way more efficient--and fast--to create an initial Exhibit configuration. As it is now, I create bookmarks in the web map, where the docked popup is positioned in the upper left of the map. Then I create an Exhibit config and load the bookmarks as slides. That is great. But the docked popups in the Exhibit app appear in the upper RIGHT. So then I need to repeat the tedious process of setting the map extents for each slide all over again. If I could set docked popups to appear in the same place in Exhibit slided relative to the map as the web map, that duplicative effort would be avoided. These settings would have the secondary config advantage of making it more tractable to do more significant changes to the web map (additional layers, etc.) that require replacing the web map in the Exhibit config, and the resulting change in the Item ID and URL for the Exhibit config. Thanks for considering. Mike Koutnik ... View more

Hi, I am working with two Exhibit apps. One has 36 places to visit, the other has 61 stops a long an "auto trail." In both cases, I set bookmarks in the web map to make setting up an initial Exhibit configuration faster. We want the popup to be docked for each place or stop. We instruct users to dock the popup for the first place/stop they visit . Once they do that subsequent popups will be docked automatically. The problem is that the web map always positions the docked popup in the upper left of the map. And the Exhibit app always docks the popup in the upper right of the map. That means configuring bookmarks in the web map is not very useful for "seeding" the Exhibit app. How can I force the Exhibit app to dock popups in the upper left of the map? Thanks. ... View more

I am working on multiple projects which require numerous bookmarks. Those bookmarks need to be updated occasionally for various reasons. After saving a bookmark, the "pointer" in the bookmarks list always returns to the top. That causes me to have to navigate back to the next in the list each time I save a bookmark. In one project I have 36 bookmarks. In another I have 61. Having to navigate back to where I just left off is tedious, and with these longer lists, time-consuming. Please alter the code for Map Viewer and the Exhibit Instant App, to "hold" the position in the bookmark list rather than always returning to the top of the list after saving or updating a bookmark. Thanks.  ... View more

Hi, I have a challenging problem. I am creating maps to be printed for kiosks in about 30 land trust preserves. They want to use custom symbols on the maps for things like benches, parking, bridges, the kiosks, etc. I have loaded the symbols into the layer symbology. That works well. The problem is that the multiple features are often close together, e.g., a parking lot and a kiosk. So they overlap at the scale of the map. A custom map is being produced for each preserve. And since the size of the preserves varies greatly, so does the scale of the maps. I tried manipulating the size of the symbols. But that doesn't work well. It was suggested we move some features. But the varying scales of the maps makes that messy. And we really don't want to have to maintain one layer for cartographic purposes and another for the infrastructure inventory, where we want accurant locations. So I thought about putting an attribute in the table to correlate with a symbol character in a font. And use standard label conflict resolution to adjust the conflicts. That works quite well. But I have really struggled to find a way to get their custom symbols into a font. I thought callout labels would be another way to do that. But that would also require a way to link the custom symbols to features. Is there some other way to crack this nut? Thanks.  ... View more

Hi, I am a Notebook newbie. I have a simple task. I need to schedule a task to calculate acres for a polygon feature layer in ArcGIS Online. I just need to access the area of the geometry, convert to acres, and set the Acres field. Below is what I have so far in my first-ever notebook. I'm not sure I'm even taking the right approach. I am currently stuck on how to get at the area of the feature shape... Any guidance is appreciated. from arcgis import GIS from arcgis.geometry import lengths, areas_and_lengths, project from arcgis.geometry import Point, Polyline, Polygon, Geometry from IPython.display import display import pandas as pd from arcgis.features import GeoAccessor, GeoSeriesAccessor ## connect to AGOL agol = GIS("home") ## access the feature service item item = agol.content.get("xyz") ## get the layer of interest as a FeatureLayer ## the example here is the first layer in the Feature Service lyr = item.layers[0] fset = lyr.query() features = fset.features for f in features:     print(f.area)     f.attributes['Acres'] = 1   ... View more

I maintain an ExB app that focuses on two large layers, one with 1.6M features and another with about 800K. The area of interest for each user varies widely, from a few townships to dozens of counties. There is also a wide difference in the size of the features when users have a smaller area of interest versus a large area of interest. Features are larger when the area of interest is larger, and features are correspondingly smaller (more dense) when the area of interest is smaller. It is impossible to provide a single scale that meets all users' needs. Performance and visualization needs dictate custom scale thresholds for the two layers for each user.  Web AppBuilder provided this capability, ExB does not. Please add this capability to ExB. Thank you. ... View more

I developed an ExB app that focuses most of its capabilities on two rather large feature classes. One is about 800K features, the other about 1.6M features. The smaller layer is created by aggregating the larger based on a shared attribute value and spatial proximity of the features to each other. The bulk of the beneficial capabilities of the app relate to filtering the features in either layer (whichever is more useful to the specific user) to narrow down the features to an appropriate number. Work is then done on those filtered features. The filters for the two layers are essentially the same. For each layer there are 6 filters, with a total of 46 clauses across the filters. Some of those clauses have predefined choice lists of from 18-72 options. Creating the filters for one of the layers is tedious but not difficult. The real tedium is when creating the SAME filters for the second layer. Again, another 6 filters with 46 clauses and several long choice lists. Another aspect of this app is that there is at least one major update to the underlying data each year. And we continue to enhance the fields contained in the data. So I typically "start from scratch" and create a new ExB for each data "version." It would save many hours of time to be able to export filter configurations into some sort of text format, and then import them to for use in another layer in the same ExB, or for a parallel layer in another ExB altogether. This functionality would also reduce errors that occur due to the tedious nature of entering all the clauses and pick lists. The other big benefit of export/import of filter configurations is that I could then make the modest alterations for a new data version to the text files of the filter configurations, and import them, rather than have to create the entire list of filters and clauses from scratch. Thanks for considering. ... View more