Latest Contributions by RussRoberts

Thanks for reporting this. I can reproduce this with your layer and will try to address it ASAP in a patch. If you can contact support you will be able to get a bug # for tracking and I can link to my internal dev work.  ... View more

This is supported in data pipelines. You can take that parquet file and publish a feature layer or the new parquet feature layer (beta). You can read about it here: https://www.esri.com/arcgis-blog/products/apps/announcements/whats-new-in-arcgis-data-pipelines-june-2026 ... View more

Right now the web style gives a symbol thumbnail at that above size. Improving the view of the symbols is on the list of enh we have for styler and appreciate the feedback.  ... View more

You can do a couple things - Under label style you can set a different placement location for each of the label classes and use the XY slider to manual adjust that position within the updated anchor location. - Disabling deconfliction. This will keep all the labels present for the class that has deconfliction disabled.    These topics get covered in this blog here: https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/map-viewer-a-labeling-recap ... View more

Thanks for posting this idea. We recently added support for adding and configuring offsets for lines and polygons symbols and looking into it for point/markers in a future update.  ... View more

No updates here - this is a limit when you have overlapping boundaries that are touching one another there will be cases where the dashes are not in sync based on scale, the segments and dash configuration so you will see similar issues in Pro    This is where I have used Johns technique above where you end up making a second boundary lines layer and you wont have dashes that can conflict with one another   ... View more

Symbol layer draw order - reading and authoring is planned for this UC release in Map Viewer. It requires you use vector/CIM symbols just like in Pro and available across a number of styles. Pro 3.7 will also publish web maps with symbol layer drawing as well.    We are also going to be supporting reading maps in with alternate symbols authored from Pro (Types and Class Breaks) but no authoring will be ready for this release. ... View more

We support reading in display filters in Map Viewer but authoring side is still planned for a future release.  ... View more

Thanks for this! I've posted this enhancement over to the portal to see how we can expand our font offerings. On the mapping side of things - We currently have Oswald available Map Viewer for labeling and will be adding supported fonts of Barlow this coming release. ... View more

Are you able to share what fonts your organization has picked? thanks! ... View more

Views can only be created by the owner or admin of the layer but the benefit is the various share settings and editing controls that can be configured. On the feature layer item is just an item pointing to the original service that could store any configuration of popups, table, symbols, filter etc. the feature layer item though cannot hide fields, features or change editing configurations. Also if someone changes the sharing the original hosted feature layer to private then the feature layer item that was saved off using the Save As which could be public or org wide shared still is just pointing to the original service referenced in that item is now private. This means that item no longer would work for those org or public viewing users when they load the item in a new map or open an existing map with the non-hosted version of the item. The service will be reported as no longer accessible.  ... View more

These wont need to be published separately. If you have a scene in Pro with the multipatch being used when you go to share that scene as a web scene you will see in the sharing panel something similar to this.  This will publish a hosted feature layer that could be used for export. Then you will have a scene layer that will have the cache built in ArcGIS Online as well and both layers are essentially published in one click. Or you could publish just the feature layer and then use the create scene layer package tool and then upload the package to ArcGIS Online and then you would have a proper 3D layer for visualizing that original multipatch in a web scene and also be able to bring it back into Pro or used in ArcGIS Earth.    ... View more

Depending on the use of the layer you could provide the scene layer package or the multipatch gdb or sd file. You can also use a tool in Pro to export a scene layer package from a service but you cannot go from a package back to a multipatch.  ... View more

Yup correct. displaying a multipatch feature layer in the web would no scale and be very expensive and is why we use the 3D layers for display. No steps to convert but at publish time you will see an associate scene layer being published along side the feature layer (this method will use credits to generate the scene layer in ArcGIS Online) or you can create it locally in Pro using create scene layer package tool.  ... View more

Correct, you will need to use a 3D layer https://doc.arcgis.com/en/arcgis-online/reference/scene-layers.htm   For surfaces you could also publish an elevation layer and use that in your scene  https://doc.arcgis.com/en/arcgis-online/manage-data/publish-elevation-layers.htm ... View more