Recently, a user asked if GeoEvent supports the "Allow assignment of unique IDs for map service publishing" feature in Map Services. The short answer to this is YES, but there are some known limitations as described below. Note that these limitations only apply to Map Services and don’t apply to Feature Services. Feature Services allow you to set unique Layer IDs, but will always present the layers in numerical ordering (ignoring the order you imposed when publishing).
NOTE: A workaround for Map Services you don't own/can't control at the bottom of this post.
In a map service, if you choose to assign Layer IDs to your layers, you should ensure one of the following:
GeoEvent manages its configuration based on the Layer ID. If you change a Map/Feature Service so that the layer’s Layer ID changes, you are responsible for updating your GeoEvent component to use the correct layer. Some examples are provided below:
If you find a need to use a map service that has the Layer Id 0 in a location other than the first (topmost) spot, you can use the Poll an External Website for JSON input and hardcode the layer ID in the URL you provide.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.