Latest Contributions by JakubSisak

Please consider adding the "Display attribute dialog after storing new features" Editing Options feature from ArcMap into PRO.   Setting the attribute value in Templates doesn't really cut it. Configure a feature template—ArcGIS Pro | Documentation This is only a crude work-around and does not come close to an intuitive pop-up dialog that's available in ArcMap. This feature is extremely useful when creating 100s or 1000s features with many different attribute values.  ... View more

Every time i select a feature or edit or split a feature the selection appears to slowly pulse (or fade in/out out/in) which is a new animated visual effect in Pro. The pulse effect takes way too long bordering on annoying which is especially cumbersome when splitting a feature to many parts as every part slowly pulses after the split operation completes.  There are a lot of such animated pulse and fade effects throughout the application. I would much rather see mu results instantly presented on the display.   Consequently, it makes the whole experience of using ArcGIS PRO, which is already much slower than the legacy ArcMap in almost every respect, even slower.  The whole editing experience feels slugish and non-responsive.  It would be great if we could TURN ALL such animated effects off globally in settings.    ... View more

Similar to how this is done in ArcMap it would be very useful if the outputs of the Export to CAD geoprocessing tool in ArcGIS PRO were placed into a single group in the TOC. Ideally, this group name would be the same as the name of the CAD output file. Currently, Export to CAD tool adds the results to the TOC as individual layers with generic names (Annotiation, Point, Polyline, MultiPatch, Polygon) and exporting (and subsequently needing to verify) the outputs requires me to manually create and place them in a group. It would be great to reproduce ArcMap behaviour in this instance.  ... View more

Abstract: All our data and maps are in NAD83 UTM. In portal we have a set of our own imagery and raster basemaps which are consumed within our web apps which is how our users interact with the data but we need to be able to also allow users to also use the default ESRI basemaps within the same web app.  There are no issues with this in desktop applications (ArcMap and Pro) albeit at the penalty of projecting the basemap on the fly and the resulting antialiasing artifacts - both perfectly acceptable. There is currently no way we can see to have basemaps with different spatial references in the basemap gallery widget and use them interchangeably in our web apps and having the app project the basemap on the fly without having to create a separate web app using the default WGS84 Web Mercator system. (Note: Switching over to the ESRI default WGS84 and tiling schema is not a solution as this is not suitable for our applications.)  We would be fine with the performance penalty resulting from projecting these basemap on the fly and with the antialiasing issues resulting from mismatched tiling schema zoom levels. I understand the coordinate system is obtained from the basemap but surely there must be a way do do this since we have been doing in the desktop apps for decades.   Solution attempt: In hopes to come up with a workaround we tried creating a basemap map in our default basemap gallery and first adding our custom NAD83 UTM basemap to the map in portal then adding a "layer from the web" and pointing it to the ESR World Imagery Service "World_Imagery (MapServer)".  Although this works in the portal map and appears in the basemap gallery widget in the web app, when we attempt to add the basemap, the World Imagery service web layer does not display. Adicionality, simply adding a layer from the web to our web app using the add data widget allows us do add the layer, does not raise any errors, layer is even added to the legend BUT the layer is NOT displayed in the app. Proposal: Allow basemaps of different spatial references including existing ESRI basemaps to be added to basemap gallery and used interchangeably with other custom basemaps of varying spatial references in the Web App basemap gallery widget projecting the basemap to a spatial reference of our choosing.  In the interim, fix or a usable workaround solution would be much appreciated.  ... View more