Latest Contributions by KerryRobinson

Hi Troy.  Yes, as Lucas mentioned, there is a new `scaleExpression` method on the Dictionary Renderer that can accept either a constant or an Arcade expression.   So it doesn't set your symbol to a specific size, but you can scale all symbols based on a specific value, or use the expression to scale based on an attribute, map scale, etc.  ... View more

Hi, The JSAPI 4.x can only work with feature layers published from ArcGIS Pro which reference a dictionary web style.  The only way to publish military symbols from ArcMap that will render correctly in JSAPI 4.x is as a map image service. If you need to support editing workflows, you can still publish a companion feature service to have in your web map in addition to the map image service, just don't turn the feature layer on in the map.  I hope that helps.   Kerry ... View more

Hello, I am not sure if this workflow would work with that version of ArcGIS Enterprise.  It not supported using ArcMap. Because the ArcGIS API for JavaScript 4.x includes support for the Dictionary Renderer, you can use ArcGIS Pro to publish the Military Overlay created by the Military Symbol Editor as a feature layer (Share as Web Layer).  Rendering of the features using the dictionary renderer is happening on the client.  Before you publish, you need to update the dictionary renderer for each layer in the Military Overlay to use the associated web style.  By default, the Military Symbol Editor will use the desktop style for the military symbol dictionaries, which are installed with ArcGIS Pro.  To choose a web style instead, in the Dictionary Renderer on the Symbology Pane, you can click the More drop-down menu and then click Add custom dictionary to  browse to a web style to add to the dictionary to the list.  If you have a connection to ArcGIS Online, you can search for the style based on the standard name ("MIL-STD-2525B").  If you do not have a connection to ArcGIS Online, you can share a desktop style as a web style in ArcGIS Enterprise.  To do that, click the More drop-down menu and then click Add dictionary to project. This will add the currently selected dictionary in the drop-down list to the list of Styles in the Catalog pane. Then you can right-click on the style in the Catalog Pane and choose Share As Web Style, which will create a new portal item for the web style.  At this point,  you should be able to browse to that web style as described in the previous paragraph.  The other thing you need to do before you publish is remove any group layers from the Table of Contents, since they are not supported in web feature layers. Let me know if you have any more questions. -Kerry ... View more

HI Mathew, Right now there are a few different ways to publish overlays using military symbology, primarily dependent on what web application they will be used in.  This is because some Esri web apps are based on our 3.x JavaScript API which does not have dictionary renderer support, and other applications are based on our 4.x JavaScript API, which does support the dictionary renderer.   Esri web apps built on our 3.x API include Web AppBuilder, ArcGIS Dashboards Classic and the Map Viewer Classic ("Classic" versions are what are currently the default in ArcGIS Enterprise up through Enterprise 100.9).   Apps built on our 4.x API include Experience Builder, the new ArcGIS Dashboards and new Map Viewer (these new versions are currently available with ArcGIS Online, and expected to be released with Enterprise 10.9.1).  If your overlays need to display and support editing in apps built on the 3.x API, then you need to follow the workflow outlined here (Share using ArcGIS Enterprise). This workflow publishes the layer both as a map image service (which can render the military symbology on the 3.x client) and feature service (which allows access to the features and editing from the client).   The Map Viewer Classic will let you add both of these layers (map and feature) to the map and will treat them as one unified layer. If your overlays need will be used in apps built on 4.x API, you can "Share as Web Layer" to publish your layers as a feature service (from your Enterprise GBD, or hosted) from Pro, but you need to first be sure to choose the web style for 2525D in the Dictionary Renderer.     I know there are several nuances in what I've described above, so please feel free to reach out to me directly or in this thread with any questions you might have. Kerry ... View more

Hi Michael,  We are looking into adding some of the capabilities of ArcGIS Mission Responder to ArcGIS Runtime. I'd be interested to learn more about which features you're particularly interested in. Feel free to reach out to me directly or in this thread with more information on what you're looking for. Kerry ... View more

Hi Virendra, We don't currently directly support STANAG 4607 in ArcGIS Runtime.  @ParkerHornstein has been looking into workflows with GMTI data and will reach out to you for further information. Kerry ... View more

Please see answers to this question in the Runtime SDK for .NET forum here: https://community.esri.com/message/740643-failed-to-create-rule-engine-mil2525c  ... View more

Hi Mauro, You're mostly correct.  To recap, we do support mil2525b (change 2), mil2525c, and mil2525d:  - mil2525c: use "mil2525c_b2" specification type and "mil2525c_b2.stylx" - mil2525b: use "mil2525c_b2" specification type and "mil2525c_b2.stylx", but also specify the `legacy_standard` configuration property.   We document this in the Qt API reference here: DictionarySymbolStyle Class | ArcGIS for Developers: - mil2525d: use"mil2525d" specification type and "mil2525d.stylx" Regarding APP-6(b), we are working to update the stylx on Military Symbology Styles | ArcGIS for Defense  to work with the Runtime SDKs. That should be available in the next few weeks.    As Mike mentioned, we understand the confusion and are working on making this more clear for a future release. Kerry ... View more

Hi Adam, ad 4545) Indeed, but it is not as not good as competitors solutions like RemoteView or so. Also, as I mentioned, it is not an out-of-the box feature. Can you expand more on what you would like to see supported with our support? ad 4607) Is it possible to give examples of these customers? It would be useful. Unfortunately we cannot share those implementations. ad App-6b) Great to hear that! What exactly do you mean by saying - through the proper channels with NATO how can we, as developers, have an access to this dictionary? Because APP-6(B) is marked NATO UNCLASSIFIED, we are unable to distribute support for it with our COTS products.  Therefore we need to distribute it through NATO. We are still working out the logistics of how this will work, and will be sure to update you once we know. Also, does Esri plan to support COSMO-SkyMed as an Mosaic Dataset item? Any plans for more extensive support for radar data? We currently support COSTMO-SkyMed in HDF5 format. I'm bringing in Vinay Viswambharan‌ so he can address our plans for supporting radar data. Thanks, Kerry ... View more

Hi David, I haven't been able to find any more information about this error.   I think the error is happening when the installer is restarting IIS, so it does seem to have to do with the IIS configuration. Maybe you can try installing from the command line, like what was suggested in this post (long shot): IIS Web Adaptor Install Error ... View more

Worked for me, too.  Thank you Avi!!!  ... View more

For future reference, here is the direct link to the idea: http://shar.es/1o6x6c I just submitted an idea to the ideas site to also allow us to just get the direct link to the idea without having to share as an email first and copying from there.  I also promoted the 'Share to GeoNet' idea. ... View more

OK, I got it now.  I saw your blog post and found it useful. I'm primarily interested in Portal deployments, so once I get more experience under my belt I'll contribute or write something similar. Thanks! ... View more