Latest Contributions by BrettFrahm

I’ve not found anything helpful for this online or with ESRI premium support. We are launching a new reservation software for the park district at the end of the month that has interactive webmaps, but their labels are not dynamic and the initial extent is based off the REST of the vector tile so initial extent starts you off showing our entire park system (several counties wide) so it is very zoomed out and every label is horribly stacked on top of each. We are working with the vendor to have their code modified to provide dynamic labels and be able to set the extent client side, but we aren't sure if they’ll be able to fix it by the time this whole system launches at the end of the month. So as a temporary solution, we’d like to have the initial extent start on a single park more zoomed in.   Does anyone know of way (ESRI supported or not) to modify the initialExtent in the REST for either Vector or Raster tiles without changing the overall extent of the tiles?   REST we sent Vendor: https://tiles.arcgis.com/tiles/nD1JmvAORRtTorXS/arcgis/rest/services/Summer_Basemap_20250429/VectorTileServer "initialExtent":{"xmin":-1.0493620790438743E7,"ymin":5537603.347470856,"xmax":-1.0322504371694421E7,"ymax":5689194.582256599,"spatialReference":{"wkid":102100,"latestWkid":3857}     What I’ve tried so far: ArcGIS Pro Publishing (Map -> Share as web layer) Centered and zoomed in map on single park before publish No change Modified the extent of the map to only be boundary of the single park Only creates tiles for that park as expected Publish a raster tile Main publish failed, so trying this again. Publish to portal as a map image -> with raster tile caching Centers on park in map viewer from layer, but when accessed through REST it puts me in ocean. Looking more at this.   ArcGIS Online modifications Downloaded our production tile’s vtpk file and modified the extent in a text editor, then re-add to arcgis online Corrupted the vtpk file Edited the bounding box extent in the metadata of a published tile layer (also tried doing it in vtpk before a publish) Fixes the initial extent when opening the main layer in an AGO web map but does nothing to the REST or the vendor’s map. Open service in admin REST and attempt to edit service json Got it to say it was successfully saved, but the json never changed in the REST and there was no change when testing in maps. Trying this more with REST API and Portal vs. AGO ... View more

There is currently no way to get labels with callouts or leaders lines in vector tiles published to ArcGIS Online. Providing this would allow for detailed labels with less conflicts. I have also gotten an Enhancement logged with support ENH-000143760.   Here is my attempt with ArcGIS Pro 3.5 In Pro:   In Vector Tiles:     ... View more

While testing Field Map Layer Filtering I noticed that if you use a field with a lot of unique values like an ID field, it does not seem to work as intended. I first tried searching for the ID then I tried scrolling, both attempts were unsuccessful(see images below). My best guess as to why it is not working, is that there is a hard limit to how many unique values there can be in the filter. If this is the case, I would like to request that the search in filter look beyond the limit of around 2800 unique values.   Attempt at searching for ID Scrolled down as far as I could and it only went to around 2800 or so. ... View more

In Web Map Item Details->Application Settings->Enable Search By Layer, I am noticing that only ArcGIS Online hosted feature layers show up as an option to configure. I would like to request that reference ArcGIS Enterprise layers are also supported.   To show that this is the case, here are all the layers in this map that are not showing up in the dropdown. Most of the layers in this map are from ArcGIS Enterprise that have been collaborated over to ArcGIS Online.   ... View more

Similar to my previous idea: https://community.esri.com/t5/arcgis-pro-ideas/export-layout-accessibility-prefills/idi-p/1656726 I am using ArcGIS Pro 3.5.2 and I've recently started looking what ArcGIS Pro offers for exporting PDFs with accessibility metadata. For the "Accessibility" tab for the "Export Layout" tool with PDFs, I noticed that if I enter information in for the accessibility inputs in one project that it carries over what I input into other projects.  Here is an example where the metadata parameters that were prefilled from another project.   As an Idea: Instead of pre-filling the "PDF Metadata" parameters with previous filled information, I'd like it to be sourced from the Layout Properties Metadata. Title: Use Title from layout properties Language: Add a language metadata field to Layout properties Subject:  Use Summary or add a Subject field to Layout properties Author: Use Credits from Layout properties or add an Author field to Layout properties Keywords: Use Tags from Layout properties or add a Keyword field to Layout properties   ... View more

I am using ArcGIS Pro 3.5.2 and I've recently started looking what ArcGIS Pro offers for exporting PDFs with accessibility metadata. For the "Accessibility" tab for the "Export Layout" tool with PDFs, I noticed that if I enter information in for the accessibility inputs in one project that it carries over what I input into other projects. The reasoning behind this might make sense because ArcGIS Pro does this for all the other settings in the "Export Layout" so that you don't have to enter in the same settings every single time.   It does not make sense for the "Accessibility" tab's "PDF Metadata" settings though as it will apply that Title, Keywords, etc to every layout I make which will 99% of the time have different titles and other metadata. If I had not realized it was doing this all my future PDFs would have a title of "Hole 1 Irrigation Utilities". Image below shows my inputs from a different project.   As an Idea, I would like to request that the "Accessibility" tab's "PDF Metadata" inputs do not carry over from other projects. Force the user to fill them out each time to ensure that the correct information is being exported.   As a note: I will also be creating another idea requesting that the layout properties be the place for you to store this information. I can't foresee a situation where a Layout would need to be exported with different tags each time it is exported so I don't know why it was decided to put these inputs in this tool vs. layout properties.   ... View more