ThinkGeo.com    |     Documentation    |     Premium Support

Problem when layers do not render in ArcRest server layer

#1

In testing we are connection to an ArcGisServerRestRasterAsyncLayer server that has many layers. Some of the layers render without issue and some do not render under most circumstances. Sometimes, when the layer does not render we see a message on the map, ‘The task was cancelled’. Other times there is simply a blank map. In all cases, when the layer that will not render is present none of the other layers in the map will draw. I am thinking there should be a way to allow the rest of the map to draw in those situations, but I can’t seem to figure out what that is. I have attached a sample project that adds a shapefile and a layer from the ArcRestLayer service. If you look in mAddArcGisRestLayer of the sample project there are some comments to explain which layer will draw properly and which will not. Any help would be appreciated!

Thanks!

Steve

ArcRestLayerTest.zip (2.5 MB)

#2

Hi Steve,

You can suppress the layer’s exception so the other layers can keep rendering, by doing

oArcRestLayer.DrawingExceptionMode = DrawingExceptionMode.IgnoreException

or you can add those layers to different overlays.

Let me know if that doesn’t work for you.

Thanks,
Ben

#3

Hi Ben,

I would prefer to have the capability to be aware that there is an error without preventing the rendering of the rest of the layers, but I understand that may not be an option. So the next best thing would be to ignore the error. However, the latest production build does not have DrawingExceptionMode.IgnoreException.

We have started what will be a lengthy test cycle in preparation for releasing our application with the ThinkGeo 14 components and would prefer not to test with beta versions. When do you expect this option to be available in a production build?

Thanks again for all your help!

Steve

#4

Hi Steve,

The next production release is currently planned for early May. I’m not sure if that aligns with your timeline, but that’s when this option should be available in a production build.

Thanks,
Ben