Latest Contributions by ChristopherMoore

The short answer is this is not yet supported by the DictionaryRenderer. So these lines would need to be drawn with a custom line symbol for now.  For now, as you demonstrated above, the speed attribute controls a label displayed on some symbols (like air, equipment) and the direction attribute controls a direction-of-movement indicator. The longer answer is that I believe the standard doesn't require, or fully explain/specify the things shown in section K, so would probably require some more information to implement. Although, the speed leader is also mentioned outside of Section K in "FIGURE 13. Dynamic graphic amplifiers for icon-based symbols." Unfortunately, this section also doesn't provide much detail on how to draw, derive the length of the speed line, an error ellipse, etc.   I'll also forward this to the team responsible for the dictionaryrenderer to see if this in on their radar for a future release.   ... View more

There is an addin sample that does this - https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Exploration/OverviewMapControl  - but not sure if they have a prebuilt version of these sample addins available (otherwise you would need to build the addin with Visual Studio) Another option might be to create multiple maps in Pro and link the 2 maps views - Link multiple views—ArcGIS Pro | ArcGIS Desktop  ... View more

You'll probably want to subscribe to the project opened event in your EditRBIDGeneratorPro_Module.Initialize method, for example: internal class EditRBIDGeneratorPro_Module : Module { protected override bool Initialize() {     ArcGIS.Desktop.Core.Events.ProjectOpenedEvent.Subscribe(async (args) => {        // Call Desired Method     }); } ... View more

There is a SDK sample that is similar that loads XML messages from a file into a GraphicsOverlay: https://github.com/Esri/arcgis-runtime-samples-qt/tree/master/ArcGISRuntimeSDKQt_QMLSamples/DisplayInformation/GODictionaryRenderer - the other method mentioned above uses a FeatureLayer where the tables column names correspond to the message attribute names. Below is some more information on the 3 different ways to create a symbol: FeatureLayer, GraphicsOverlay, or SymbolDictionary. FeatureLayer, GraphicsOverlay are used to draw on the map and SymbolDictionary is mainly used to create images. https://www.esri.com/arcgis-blog/products/api-cqt/defense/working-with-mil-std-2525d-symbology-using-quartz-runtime/ https://developers.arcgis.com/net/latest/uwp/guide/display-military-symbols-with-a-dictionary-renderer.htm  ... View more

I had this problem (Pro/Python 3 choking when loading a toolbox from command line) and the workaround from Handle python 3 choking on non-text scripts. · habnabit/passacre@2ea05ba · GitHub  seemed to work for me: # WORKAROUND: for Python 3 choking on reading some non-binary files # Get error like: detect_encoding...tokenize.py...find_cookie...raise SyntaxError(msg)   # ...SyntaxError: invalid or missing encoding declaration for '...XXXX.tbx' # Workaround borrowed/used from: https://github.com/habnabit/passacre/commit/2ea05ba94eab2d26951ae7b4b51abf53132b20f0 if sys.version_info >= (3,0):   # Code will work on Python 2, but only do workaround for Python 3    import tokenize    try:       _detect_encoding = tokenize.detect_encoding    except AttributeError:       pass    else:       def detect_encoding(readline):          try:             return _detect_encoding(readline)          except SyntaxError:             return 'latin-1', []       tokenize.detect_encoding = detect_encoding ‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

I am not aware of any near term work on this (but perhaps others will know and/or the best way to request a feature like this). But it is an unfortunate nature of such a large and inclusive standard like 2525 that some things are shown that are not fully specified (or not specified to the level that they could be unambiguously encoded in a message format). This particular feature could use some further detail/specification of how one might implement/exchange such a feature. For instance, the data attributes used to drive such dynamic graphics. ... View more

You can install them both (10.X and Pro) on the same machine, there are no conflicts between the two. ... View more

Those "Dynamic Graphic Modifiers" shown in that section of that Table IV (and shown in Figure IV) are unfortunately not supported in Runtime. The standard is somewhat vague about how to represent and exchange that type of information. So if your system has this specific requirement, you would have to implement these graphics using custom drawing (not message processor properties - if needed, the list of properties Runtime supports is here: military-features-data/data/mil2525c at master · Esri/military-features-data · GitHub ).  A few years ago we did a custom drawing sample using the Qt API here: vehicle-commander-qt/mapcompass.cpp at master · Esri/vehicle-commander-qt · GitHub  - but I am not sure how current this approach is (that is, there might be easier ways to do this custom drawing with the Qt API now) ... View more

I believe that property you mention: "[datetimevalid] , " is 4 separate properties from that Table mentioned ( https://github.com/Esri/military-features-data/tree/master/data/mil2525c#modifier-label-fields ) "datetimevalid" + "x" + "y" + "z" In the standard (2525C) those x, y, z are the location and are on the same line/label as datetime. Unfortunately, because of how the label is specified if you set one of the properties, it will turn them all on/set visible. ... View more

Unfortunately, setting the properties to get the correct labels to show up using the MessageProcessor has been somewhat of a point of confusion, the Github repo that hosts this data attempts to clarify this here: https://github.com/Esri/military-features-data/tree/master/data/mil2525c#modifier-label-fields But I believe those properties names listed there have only been tested using the latest version so hopefully these will also match your version of the software. I *think* the only thing that changed from version to version was in older versions Case/Capitalization was not significant and in the newer versions the casing of the properties do matter. Hope it helps. ... View more

We are working with the Runtime to get this in for the next dictionary/runtime release. Here is where this issue is currently being tracked: https://github.com/Esri/military-features-data/issues/21 ... View more