Latest Contributions by Miralem_Zeljo

I was referring to Web Editor and Webmap. Instant app is a nice workaround. Appreciate your feedback Emily. ... View more

Same problem here:   ... View more

In ArcGIS Pro, you can visually “spatially filter” layers without editing data using clipping: Map Frame Clipping (Layout): Select the map frame → Map Frame tab → Clip → Clip to Shape → choose your polygon layer. This clips everything in the map frame so layers only display inside that boundary. Clip Layers in Map (Map View): In the Map Properties → Clip Layers, you can clip specific layers (or all layers) to a polygon, acting like a spatial filter without creating new data. Map Series Clipping: When using a map series, enable Clip to Index Feature so each page automatically clips the map to the current feature (e.g., per permit/cabinet area). All of these are display-only and don’t modify your data. ... View more

A potential workaround is to create a view layer and split your categories across two instances of the same layer until Esri provides a way to extend the current limit. This approach allows you to effectively manage and display up to ~1800 categories without needing to publish an entirely separate layer. This can help maintain continuity in your workflows while avoiding the overhead of duplicating data or restructuring your content organization. Hopefully, this serves as a practical interim solution until ArcGIS Online increases the category limit. ... View more

Thank you for sharing the resource — I’ll take a look at the basemap workflow. I understand and agree with the concern regarding projection distortion and the potential for grid-based measurements to be interpreted as exact. That said, from a practical workflow perspective, having the ability to define grid cell dimensions in real-world units (e.g., feet or meters) would still be very valuable. In many engineering and design use cases — especially at localized scales — users are already aware of projection limitations and are working within tolerances where that level of distortion is acceptable. Providing this capability, even with appropriate disclaimers, would significantly improve efficiency and alignment with existing workflows in tools like ArcGIS Pro. So yes, I would still prefer having the option to define grid cell dimensions, with the understanding that measurements may not be exact across the entire extent depending on the projection. ... View more

Yes, I am familiar.  Hopefully this is something that can be implemented where user can save default selection settings so that we dont have to keep unchecking the boxes over 30 layers. Grouping helps but having ability to save preferred selectable layers by map would be very helpful similar to how Arc Pro works when you save project, selectable layers are also saved.  ... View more

Thank you for the reply! ... View more

System-driven automations appear to have a significant impact on how custom symbology behaves in both ArcGIS Online and ArcGIS Pro. Specifically, when using Save Web Layer to update symbology driven by Shape_Length or Shape__Length, I’ve encountered cases where the symbology becomes corrupted. In those situations, the only reliable fix was to republish the data. ... View more

I’m starting to suspect that relying on `Shape_Length` (or `Shape__Length` after export) for symbology in ArcGIS Pro can introduce subtle—but real—issues. Here’s what I’m seeing: * In FGDB vs enterprise GDB, length values can differ slightly due to parametric curves vs densified geometry * When exporting (e.g., to shapefile or CAD), `Shape_Length` often becomes `Shape__Length` or gets truncated * After that, symbology driven by those fields sometimes: * fails to apply * behaves inconsistently * or throws field-related errors when overriding symbology My assumption is that this is a combination of: * system-managed field behavior * field renaming/recreation during export * and ArcGIS Pro’s sensitivity to field references in renderers In workflows where symbology is tied to length (fiber segmentation, QA layers, etc.), this can get messy fast. Curious how others are handling this: * Do you avoid using `Shape_Length` for symbology altogether? * Do you copy values into a user-defined field to stabilize things? * Have you run into symbology breaking after data moves between FGDB / SDE / shapefile? Feels like one of those edge cases that turns into a real production issue if not handled carefully. ... View more

It is important to note that we previously had the ability to bulk edit multiple layers using either a Mobile or Contributor license. This functionality has since been lost, and we are now limited to bulk editing one layer at a time. This limitation appears to be due to a reduction in functionality following the deprecation of Web AppBuilder (WAB). ... View more