I had written a silverlight application that was parsing out JSON strings returned from our ESRI's geoportal instance. We had set up this portal instance with our list of authoritative layers served to the internal users (US Dept of Agriculture). the above mentioned silverlight app was loading the searched layer names into a data grid at the bottom.
when the user selected a layer in that grid, its name was loaded on to a list from which users could choose to display the contents of that layers at 80% opacity on the silverlight map (ESRI API) with NO ability to change the opacity.
Some data had to be shared with the public as per requirement as a map. Since we cannot share our 'authoritative' layer data with the public as it is, we decided to use ESRI's publicly available layers from its portal (URL indicated) above for backdrop or reference purposes.
We were able to parse and display the JSON string returned from ESRI's GEOSS portal in a grid. When one of the returned layer name was selected from those listings, it was evident that the returned list were REST services, WMS services of varying versions, names of a website that had a lot of layers.
I was wondering whether there were ways to limit usable layers coming into the grid so the users will not wondering why there selection did not work.
if i can restrict the listing to be only ArcGIS Server REST and then later on a recent version of WMS, i think my purpose would be solved.
