ArcGIS Pro has a superior interface for authoring weblayer symbology. It would be nice if you could use it to edit an existing webmap then simply share but overwrite an existing thus maintaining the webmap id.
I spend a lot of time managing AGOL webmaps for use in Collector for ArcGIS. I have to make changes to various existing web maps on a daily basis. The only way to manage these web maps seems to go on AGOL via web browser. Our internet can be unreliable at times and just adds to the poor inefficiencies I have to deal with when changing a web map, either by adding a new layer even changing symbology. The inefficiencies come from going to one item page to clicking to another item page, and then going back to opening the map viewer, and so on and so on, just waiting for everything to load. What should be a 1 second task can turn into a 5-10 minute task if you do not have the most reliable internet speed.
The ability to manage these web maps via ArcGIS Pro should be a no brainer.
Do you create your webmaps using a Map Image Layer from ArcGIS Server (AGS) or do you just add individual feature layers (either from AGS or AGOL) to make up your web map? Maybe a combination?
Unfortunately, I do not have ArcGIS Server. I am publishing individual feature classes from a gdb, and when you choose to publish it as a webmap, you are forced to use a web hosted basemap. In this case, using the exportable Topo that AGOL provides. I have tried to publish web maps with hosted feature classes that are in My Content already, but the links to the data(not the data itself) always ends up looking a little strange..sorry I can't really explain it well.
Anyway, I have noticed, since my first comment that webmap building interface has improved a lot on AGOL. However, if you consider bandwidth and internet speed...it can still take a bit of time. I don't want to have to redo this all the setting for this or that layer, when it is already set in a project file I have saved.
Providing a desktop application-based management tool for web maps is an obvious no brainer.
The ability to publish a web map from ArcGIS Pro proves that ESRI is committed to providing power users with tools to publish maps from ArcGIS Pro.
However, the inability to then maintain and update those maps is a serious drawback that will prevent a potential avenue for adoption of ArcGIS Pro by professionals who not only need to create content, but are then responsible for maintaining that content seamlessly and without interrupting downstream users of that content.
ESRI needs to support the complete project lifecycle and not just the initial adrenaline rush of creation.
Retrieving data ...