Latest Contributions by PreetiMaske

‎03-20-2020

If feature table has advanced symbology , it is as designed that Renderer.ToJson will return empty symbol info and ((SimpleRenderer)Renderer).Symbol.toJson() will return the json of CIM Symbol. Since the service you had has AdvancedSymbology enabled, what you are getting is as expected. If you to access the simple symbol as advertised in layer's metadata you can turn FeatureTable.UseAdvanceSymbology=false before loading the table. Uri serviceUri = new Uri("https://sampleserver6.arcgisonline.com/arcgis/rest/services/USA/MapServer/0"); var table = new ServiceFeatureTable(serviceUri); table.UseAdvancedSymbology = false; await table.LoadAsync(); // Create new FeatureLayer from service uri and FeatureLayer fLayer = new FeatureLayer(table); var str = fLayer.Renderer.ToJson(); NOW YOU WILL GET FOLLOWING FROM RENDERER.TOJSON() {"symbol":{"angle":0,"color":[255,255,115,255],"outline":{"color":[0,0,0,255],"style":"esriSLSSolid","type":"esriSLS","width":1},"size":4,"style":"esriSMSCircle","type":"esriSMS","xoffset":0,"yoffset":0},"type":"simple"}‍‍‍‍‍‍‍‍‍‍

‎02-18-2020

It really depends on your workflow. Most straightforward and easiest approach , as you also mentioned , is to create a style file and get symbol from it. You could also create it in code behind but it won't be as straightforward as creating symbols from a style file. You will more room for creativity when using a style file. Following topics will help in choosing what is ideal for your workflow Read symbols from a mobile style | ArcGIS for Developers Symbol types—ArcGIS Runtime SDK for .NET | ArcGIS for Developers --Preeti

‎02-07-2020

Yes, a relatively similar issue was reported in the past. Blank map when WPF is in software rendering mode and has been fixed in 100.5 release. But every use case is different. The most recent release is 100.7. Could you give that a try and see if it makes any improvement/difference?

‎02-05-2020

Hello Mark, Just following up on your original issue in this post regarding Symbol Rotation not getting honored. This has been fixed in 100.7. Did you get a chance to try it out and remove any existing workarounds? The symbol rotation should be honored without any workarounds. Please note, other issue in this post that you reported regarding cloning layer renderer stripping out definition expression and other properties still exists in 100.7. Thanks, Preeti

‎01-30-2020

You are right, Runtime SDK does not honor/support alternate symbols yet. This feature is currently not slated for any future release. Do you mind sharing your workflow and a use case explaining why do you need this feature and how will it help you in achieving your workflow? This info will help us in prioritizing and will give some more weight to its usability from a Runtime-SDK user perspective. Thanks, Preeti

‎01-28-2020

Good to know 🙂

‎01-28-2020

Sorry for the inconvenience. I have logged already the bug. I will put your info in that bug.

‎01-28-2020

Hector, I don't think what you are seeing is a bug. It is merely a difference in ArcGISTiledlayer rendering at different Lods in two versions. I can see that at 10.2 the grid lines show up at different scale when compared to 100.7. See First two images for 10.2 above. First one does not show the grid lines but as I zoom in the grid lines start showing up. However in third image which is 100.7, the grid appears much sooner and it is not a bug because there is actually no data in those areas at those levels. The image you had for 10.2 was on android device and perhaps the background is darker on Android ( I haven't tested that). My test app was a WPF app using 10.2 and 100.7, but it shouldn't matter. I am almost certain if you zoom in further you will see the grid. It's hard to see the grey grid lines on dark gray. Perhaps there is MapBackground set in your for 10.2 app? I hope it makes sense. Please let me know if you still have concerns or questions. -Preeti

‎01-27-2020

I am not sure what kind of differences your are seeing but I do see you are using wrong layer type between two versions 10.2 and 100.5. AGSTiledMapServiceLayer in 10.2 version translates to "ArcGISTiledLayer" in ArcGIS Runtime SDK 100.5 version. I think if you switch layer type to ArcGISTiledLayer it will render as you expected. Please refer to: ArcGISTiledLayer Class ArcGISMapImageLayer Class Just as an FYI, the latest released version of SDK is 100.7 , if you want to move to latest.

‎01-27-2020

Sandra, Thanks for providing the video. That really helped. The difference was that my layers did not have labels enabled.I can reproduce the problem when I enabled the labels. Note, it is not the layers that are flickering, it is just the text/labels that flickers. I am not certain about the workflow of your app but the only workaround to avoid flicker is to disable the labels for layers. I have logged this a bug in our internal bug management system. Thanks for reporting this regression. Let me know if you have any questions.

‎01-24-2020

To achieve this, you could apply a UniqueValueRenderer to lines layers and in the renderer for the values for which you want to look bolder set the SimpleLineSymbol's width to be bigger than others.

‎01-24-2020

Hello, I was trying to see if I can reproduce the problem but wasn't able to. Could you please elaborate how is your map set up? What sources the data in the map? - Is it a webmap with FeatureLayers? Are featurelayers hosted featurelayers or ArcGIS FeatureServices? - or a MobileMapPackage? - or did you create a new Map and added FeatureLayers to it? again in this case also are featurelayers hostedfeaturelayers or ArcGIS FeatureServices or from a featurelayers from a localgeodatbase.? I tried the first approach in the list above and wasn't able to see the behavior you reported. If it works, you can even create a simple repro and share with us. It tremendously helps in troubleshooting. Thanks, Preeti

‎01-21-2020

Some questions and things to check: - What are the contents of the mpk? like types of layers, any networks etc. - What version of ArcGIS Runtime SDK .Net / are you you using? - If you put a try catch around StartAsync() do you get any additional information? - Sometimes output window prints out relevant information too. Do you see anything written out there that may be associated to this mpk?

‎01-21-2020

That's right x86_64 isn't supported yet. For Android you would need a 64 bit device to test this functionality and architectures supported are armv7, armv8 and x86. You will have to set the architecture to armv8 to ensure app is running as 64 bit. Other alternative is that If you have UWP in the forms project, you could use it for testing the locator.

‎01-21-2020

Yes Pro is 64 bit but these new locators created are not compatible for a 32 bit app. So changing the architecture of your test app to 64-bit should help.

Online Status	Offline
Date Last Visited	‎12-17-2025 01:47 PM

My Ideas

Latest Contributions by PreetiMaske

Re: How to get SimpleRenderer.ToJson to include Symbol?

Re: Symbol best practice

Re: Map freezes when returning from CTRL+ALT+DEL screen.

Re: MMPK: Bad Symbol Rotation

Re: alternate symbol Runtime support

Re: Soil survey shows holes in 100.5

Re: IdentifyLayerAsync on two layers flickering in 100.7

Re: Soil survey shows holes in 100.5

Re: Soil survey shows holes in 100.5

Re: IdentifyLayerAsync on two layers flickering in 100.7

Re: Bold Polylines

Re: IdentifyLayerAsync on two layers flickering in 100.7

Re: Exception loading mpk file

Re: Can't create a new offline locator that works with ArcGIS Runtime

Re: Can't create a new offline locator that works with ArcGIS Runtime

Re: Is it possible to pause / resume Offline Map A...

Re: need working example for polygon feature layer...

Re: createSwatch doesn't work anymore since 200.5 ...

Re: Can 200.6 parse this arcade expression that la...

Re: Create a MultiLayerPointSymbol from SVG