JSON Save MAP / Open In Meeting – ESRI UC
7/11 - Dollison and Tricomi met with ESRI architects of the open REST spec, arcgis.com (Jeremy Bartley), Palanterra x3 (Kevin Kelley), and arcgis online (Charlie fry) for about 45 minutes.
Good news on open JSON context profile direction
- presented target USGS JSON direction been working @NGP and @CDI included plot of arch direction
- Px3 is beginning to migrate to the open rest spec by, likely EOY
- meaning the main config file for Px3 can open easily in arcgis.com
- meaning current flex viewers can consume already like the water mapping viewer for the crbdemo
- meaning out of not esri js viewers can read - Silverlight too
- meaning if we had a json reader if we asked opengeo to do - and they are open to doing - then easy to take an view and open with no coding in openlayers
- ALSO, meaning it auto opens in arcmap 9.3, 10.x !Possibly no arcpy code needed to open config in arcmap since arcmap reads that json context
- still need to do json2kml, but we have Headstart, and they agreed that good direction for us to take
- ideas still open, but has legs (meaning, if we got the above its good transition state, the below would be target state):
--standard and standalone json2pdf,jpg,png that any viewer could call
--enterprise json to help multiple sub lists from many agencies
--kml input file so could have many URLs added @once as collection like a catalog
--they were tightlipped on asking if working with OGC on possible future new standard - I took that (IMHO) as they are not having luck with OGC in regards to the open REST spec still
-- arcgis.com likely integrating geodataportal for csw type code.... Not sure how relates yet
-- didn't discuss download config standard, but not off table
-- they understood need to make separate app, not build into just px3 or ags.com
-- noted the opengeo architects we've been talking to are very open to this direction
Also, TNM'll be moving to v18 of px3 as soon as Dave Hughes approves staff schedule, as tonight they gave us the px3 code with the ie fix (we need to double check some bugs, but looks good as FBI moved to already) - means the viewer on pub beta can move to live after that.
Rob very pleased with outcome (me too) and also happily surprised that months of struggling to meet up/chat, and boom, motherload.
So good day for the save as/ open in project.... And I could see finding for fy12 other projects and Corp sites to consider using this module in their viewers! (food for Aug workshop!)

7/13

Greg Smoczyk and Tricomi met with 3 ESRI Techincal staff members to confirm how/when the JSON 2 ArcMap works. Since this concept reduces or removes the need for USGS to code this, we wanted to validate the above

First with the ArcMap team, there seemed to be confusion of this working in ArcGIS 10. We tried to use the arcgis.com function “Open in ArcGIS Desktop” function. See:

http://www.arcgis.com/home/item.html?id=063d336982fd45dc98ab5397bab51ca2

for example, click the down arrow for open, then select Open in ArcGIS Desktop 10.

First, this does not work in AGS 9. We tried in AGS 10, and it errored out/hung

Then, we met with the arcgis.com team, which had a demo of AGS 10.1, and it worked great.

It makes a pkinfo file that once associated with ArcMap, just opens ArcMap.

Now big mashups take time, a few minutes, but it does work, and is VERY cool!

Arcgis.com has a library to take the context and make it into a pkinfo file.

It is recommended to explore how arcgis.com sets up this function, add this function to the save as toolkit on the USGS side, so that a user doesn’t have to go from there viewer then open in arcgis.com then go to arcmap