AnsweredAssumed Answered

Trying to keep two layers in sync

Question asked by rcoodey on Sep 11, 2013
Latest reply on Sep 15, 2013 by rcoodey
So we have a line feature class (pipelines) that is served up with a pretty elaborate hierarchy filtering on a few different columns a bunch of different ways. We also then have a point feature class of a number of items that exist along these lines (valves for example), the users would like to turn on and off these points independently of the lines (i.e. see just the pipes and no valves), but the points should never show if the corresponding lines are turned off (based off the hierarchy).

We don???t like the idea of duplicating the point layers over and over in each of the lines hierarchy, so currently the points and lines are two separate services. The question I have is what, if any, is a good way to keep the points definition in sync with the lines? The only common link between the two is an ID field.

On a legend changed event it seems we will have to request these IDs from the server passing along the visible lines and then set those in the points LayerDefinition (Yikes that could be a lot of IDs).

Problems using Find:
   - Find requires search text
   - Find doesn???t have option for out fields, so will return much more attributes than just the needed IDs.

Problems using Identify (would just pass a large geometry covering the entire AOI):
   - Like with find, identify doesn???t have option for out fields so sends a lot more than what is needed.

Problems using Query:
   - Does not work on service directly but on individual layers so would require many server requests since the hierarchy is pretty big.

Any ideas or recommendations on how to tackle this? Maybe a better way to design it even?

Thanks a lot for any help or ideas!

Outcomes