nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Web Editor functionality inside normal Web Map?

rkelley_NA

I am just curious, why wasn't all of the editing tools/capabilities that are inside of Web Editor built right into the Web Map? It seems kind of silly to have to bounce back and forth between the two (or some other type of editing application) depending on what kind of editing you want or need to do.

Find more posts tagged with

General Editing Tools

Needs Clarification

Status: Needs Clarification

Comments

rkelley_NA

@Joshua-Young Great information! This is one of the things I commonly point out in product surveys and the UC survey...I just think the products need to be conflated somehow because I also often run into the scenario you describe above.

joyoung_kerrvilletx

I too am enjoying the new Web Editor app and the functionality that it is bringing to a web environment. That said, I do hope that all the functionality it brings is eventually brought into Experience Builder as an "Advanced Editor" widget. One of my organization's biggest issues with Esri web technologies is the fragmentation of functionality. Often we have a workflow where we need to do "A" and "B". Well one Esri web app does "A" and another does "B", but none do both. I hope that Experience Builder eventually becomes the one and only web app building experience. I really think Experience Builder could and should become the home for Instant Apps, Dashboards, Web Editor, and StoryMaps.

I think Map Viewer should keep its simplified editor interface to keep that specification as lightweight as possible and save the advanced functionality for Experience Builder.

cgillgrass

@AdamMesser1 no, there are no plans to remove Web Editor.

AdamMesser1

@CraigGillgrass if Esri is "working on moving the capabilities in the Web Editor into the Editor widget within Map Viewer" does that mean Web Editor will be removed as an app once capabilities are moved?

rkelley_NA

@CraigGillgrass Thanks for the reply!

I actually love the Web Editor overall, especially the look and feel of the way the toolbars work, and cannot wait to see else comes next! I guess my issue/concern is that the editing experience in the web map is different than the web editor and is also different than the editing widget in experience builder. I wish there was more consistency in the capabilities and the look/feel across all three (I personally like our users using apps built in experience builder) editing experiences.

So for our users, I find editing things like attributes or creating point data can be easily done in a web map or an experience builder app but for more complicated geometry drawing, copying/pasting features and batch attribute editing, the web editor is the way to go. It seems like adding the same editing experience from web editor into the web map and experience builder would just simplify things for end users. If I am thinking about this incorrectly please let me know!!!

cgillgrass

@RyanKelley_NA Thanks for the feedback. We're working on moving the capabilities in the Web Editor into the Editor widget within Map Viewer. This will be taking place over several releases.

Interested in knowing what kind of editing you're doing where you feel the need to bounce between the two applications. We've gotten a positive reaction to Web Editor overall, so it could be that your workflows are different or unique from some of the feedback we've gotten.