Latest Contributions by Mike_Koutnik

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

I am using the Dissolve tool to aggregate groups of parcels based on common tax bill address. The parcels have had various extra attributes added to parcels, both numeric and string. It would be most useful and appropriate for our use case for the Dissolve tool to support a MAJORITY "statistics type." This would allow me to capture the dominant characteristic among the possible values for a specific attribute. I imagine some users might also find a "MINORITY" statistics type useful. Thanks.  ... View more

One VERY nice feature in Web AppBuilder is being able to explicitly set the presentation order of values in a predefined choice list. Apparently, Experience Builder automatically sorts value choices alphabetically. That option surely has some utility for some. But for our needs, allowing explicit placement is far superior. We have several long lists of choices in one application. Some dictated by regulations or policy, others by convention. Users a very familiar with these choices being presented in a specific order. In each case, there is an inherent grouping of the individual choices they are familiar with a comfortable with and makes sense to them. To not see those options in the familiar order is disorienting to them. It would be VERY helpful if an option could simply be offered NOT sort filter value choice lists and just use the order of choices as configured in the builder. Thanks ... View more

I spend quite a bit of time selecting and fine-tuning symbolization options for layers in web maps. The palette color picker in the "classic" Map Viewer saves me gobs of time. A color I pick there, often with transparency adjustments. That makes it quick and simple to set an appropriate color. But a BIG side benefit is that this approach allows me to assure that a color I use in one map or app can easily and quickly and confidently be "reused" to provide consistent color use across use cases. It thus sets up the ability to "enforce" standards for a set of maps and apps. When I go to a new map with a layer that I want to "reuse" a color, I can go to the palette and quickly pick, say, the magenta in the 3rd row in the last column. Choosing from the palette also sets--and continually reinforces--a spatial and visual "muscle memory" for often-used colors. Overall, this leads to clarity for users of your information products. With the new Map Viewer, you are faced with having to always use slider bars, or remember and type in hexadecimal codes, constantly referring back to another map or layer to make sure you have the color right. It's tedious and frustrating. Picking from a palette is SO much easier, faster and repeatable. PLEASE add the palette to the new Map Viewer. Thanks. ... View more

In ArcGIS Pro I sometimes need to mimic the symbology of a raster layer in a vector layer.  I also sometimes have the need to do the opposite: mimic vector symbology in a raster layer.  It would be very helpful to enable the Import Symbology tool in the Map button bar to import the symbology from one layer to another of different type.  Obviously the data types for the two layers would have to align, e.g., an integer raster and a numeric column in a vector  layer.  But it should also be allowed to import symbology for a text categorical raster into either a numeric OR text column in a vector layer, if the categorical values in the raster are numeric.  This capability would eliminate tedious manual creation of classes and copying of RGB values between the layers.  ... View more