Known Limitations

Layer stacks: The layer stacks differ between JS and Flex client. Further information...

Labeling: The number of features to be labeled is limited to 150 due to performance issues regarding the browser. If there are more point features within the map extent they won't be labeled.

Grouped basemaps: Sliders for changing the grouped basemaps are just available in the Flex client and the JS desktop client. In the mobile clients the backgroundmaps will be listed without slider functionality.

The RoutingTool is not available in version 3.0+.

Flex client specific information

The QueryMapExtentTool is exclusively available in the Flex map client.

The ProfileTool is exclusively available in the Flex map client.

The PublishUrlTool is exclusively available in the Flex map client.

JavaScript specific information

IdentifyAndSelectionTool is just available in the javascript client. It's currently not available in atlasFX 3.0+.

The CoordinateTransferTool is exclusively available in the JS desktop client. It is not available in the Flex client and not in the mobile clients.

Language settings are not covered by Esri components

The language settings are not covered by Esri components (like tooltip of the the drawing tools and color picker) when changing the language during the execution of the map application. For this purpose, a reload of the entire map is required, which is by default turned off. Via external interface you can change this (see documentation for external JS interface).

Limitations in mobile Clients

Tools are not available in mobile clients.

Label Feature

In javascript viewer the settings for the text background color has no effect. In contrast to the Flex client the starting point for labeling is the lower left point of the label text. Therefore, the thumbnail differs minimally to object labeling compared to the view in the javascript viewer. In the flex client the center of the label is used as base point. Preview and the real map view are identical in flex.

System specific words

If you are using services which are using the following keywords as field names it' possible that atlasFX will not work properly or/and show an error message:

"AS", "BY", "DO", "IS", "IN", "OR", "ON", "ALL", "AND", "ANY", "KEY", "NOT"SET", "ASC", "TOP", "END", "DESC", "INTO", "NULL", "LIKE", "DROP", "JOIN", "LEFT", "FROM", "OPEN", "CASE", "WHEN", "THEN", "ELSE", "SOME", "FULL", "WITH", "TABLE", "WHERE", "USING", "UNION", "GROUP", "BEGIN", "INDEX", "INNER", "LIMIT", "OUTER", "ORDER", "RIGHT", "DELETE", "CREATE", "SELECT", "OFFSET", "EXISTS", "HAVING", "INSERT", "UPDATE", "VALUES", "ESCAPE", "PRIMARY", "NATURAL", "REPLACE", "BETWEEN", "TRUNCATE", "DISTINCT", "INTERSECT".

Please avoid field names containing any of these keywords.

Avoid special characters

While using ArcGIS you know that using special characters in field names should cause problems. The same problems will happen while using  data with special characters in field names in atlasFX as atlas vector layer. In atlasFX special characters could cause problems while loading,  displaying and querying the data. Only the special characters ä, ö, ü, Ä, Ö, Ü, ß are allowed.

Please avoid others while maintain your data.

Links to example data

We assume no liability for the contents of the above listed links.

Links to WMS services

We assume no liability for the contents of the above listed links.

Links for icons

We assume no liability for the contents of the above listed links.