Missing Tiles cause Errors and Crashes in TiledMapServiceLayer

3393
1
04-30-2014 12:38 AM
MartinScherpinski
New Contributor II
Hi Guys,
we are developing mapping applications based on the Esri API for Flex and use some of the free Basemaps from AGO. Our API-Version is the older v. 3.1 to ensure compatibility to older applications.
While reactivating some of these old applications we have discovered a huge Problem:
We are using the World Terrain Base Map (http://services.arcgisonline.com/ArcGIS/rest/services/World_Terrain_Base/MapServer) that should have 14 LODs and some other Basemaps with 20 (e.g http://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer).
First problem: when you change from any Basemap in a similar LOD to the Terrain Base Map in the Level 10, 11, 12 or 13, there are no Tiles. MapService-Description says, that these LODs are available, but you only get 404-Errors instead of ???no data???-Tiles. This Problem I reported in an extra Thread.

[ATTACH=CONFIG]33472[/ATTACH]

[ATTACH=CONFIG]33473[/ATTACH]

[ATTACH=CONFIG]33474[/ATTACH]


Inside our application, the screen gets white, but the application is still usable. Anynway, the missing tiles cause a crash in one of our Use-Cases:
When, for example, the Imagery Map is activated and there are some features or geometries added by any kind of service to any layer of the map and you change to the Terrain Map in one of the missing LODs, Flex throws an error:

TypeError: Error #1010: A term is undefined and has no properties.
at com.esri.ags.layers::TiledMapServiceLayer/loadTiles()
at com.esri.ags.layers::TiledMapServiceLayer/updateLayer()
at com.esri.ags.layers::Layer/updateLayerIfInvalid()
at com.esri.ags.layers::Layer/updateDisplayList()
at mx.core::UIComponent/validateDisplayList()
at mx.managers::LayoutManager/validateDisplayList()
at mx.managers::LayoutManager/doPhasedInstantiation()
at mx.managers::LayoutManager/doPhasedInstantiationCallback()

The application then freezes, the Map-GUI (e.g. the Nav-Control) is not responding. It seems like an error in the API, TiledMapSerciveLayer seems not to be able to handle a 404 in loadTiles().
Any suggestions? May this be a known issue and already be resolved in a newer API-Version?

Regards,
Martin Scherpinski

alta4 AG
Fleischstra??e 57
54290 Trier, Germany
tel: +49.651.96626-0
fax: +49.651.96626-26
0 Kudos
1 Reply
by Anonymous User
Not applicable
Original User: pIseVen101

Hi,

after a lot of debugging we were able to find our problem. It was not caused by the API, but the usage of it.
So this is not a problem anymore.
0 Kudos