The TNM Viewer uses a GeoServices REST Specification that ESRI submitted to the OWF. Its a nice beginning standard to a JSON-Version like the OGC Web Context Profile in XML.
In any case, since lots of viewers like Google Earth, Open Layers, Google Maps, Bing, and many ESRI Viewers reads KML, but not the JSON GeoServices Spec standard (yet), it may be easier to share the JSON Mashup as KML.
The following demo takes a JSON file created after making a mashup, runs a java parser built in eclipse. It deploys as a Web Archive (WAR) on any JAVA App server like Tomcat - and is not directly tied to the TNM Viewer - can be used in any viewer.
It takes the user-customized mashup JSON file output from the TNM Viewer, then converts it to KML. It takes the Basemap options and selected basemap, the zoom extent and location, and then takes the services groups, overlays, user-added content, which were turned on, any transparency and layer order settings and loads it into KML.
So, far it can handle REST and WMS, and plans should be able to support network linked KML and RSS - but not data KML unless network linked over a URL.
The attached presentation shows the beta efforts which USGS is looking to employ in FY12.
This effort is a result of the USGS Community for Data Integration efforts coordinated by:
Rob Dollison, USGS NGP (email@example.com)
Ryan Zoerb, USGS CIDA (firstname.lastname@example.org)
(John Hollister, Former USGS CIDA)
Voting on Ideas
Vote for your favorite ideas by clicking on the up arrow.To undo an upvote, simply click the arrow again. This second click removes your vote.