Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Silverlight application that consumes around 30 map service layers at different types. The service layers are categorized based on type and only applicable to certain screens of the application.

For organization's sake, I split each of the layer categories into separate map services, but I'm considering whether or not that makes sense.

What is the best practice in this situation? Should I just lump all of the map layers into a massive map service or keep them separate? I'm curious about server load vs application performance.

share|improve this question
up vote 4 down vote accepted

I would suggest to use multiple map services to take advantage between dynamic vs cached (tiled) services. For basemap data that does not change often you should use cached services (this will improve performance).

share|improve this answer
Good point. In this case, all of them are dynamic. Some are being consumed as dynamic while others feature layers. – Jordan Parmer Aug 10 '12 at 14:53

I would suggest multiple services, whether they're cached or not. I've often found that once a web map is available, a decision maker (boss) sees it and wants a similar app with only one or two of the same layers. If those layers are already in separate services then making the similar app will be quicker.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.