Parity between WebADF and REST?
During the last Road Ahead webinar mention was made about the parity now between WebADF and REST API.
It's true the Silverlight Viewer has come a long way with regard to that parity. However, I have to ask about the ability to extract markup to a shapefile in the Silverlight Viewer. There seems to be interest on the forum for having that ability in a version that is compatible with AGS 10.1, but Latitude has been silent on the subject.
Feedback from Latitude would be appreciated. Can we expect an update to the Code Gallery sample? Or perhaps an addition to the core product that provides the ability to extract markup to shapefile?
Thanks,
Steve
-
Hi Steve
I’m pleased to hear that someone else shares my frustration. We were promised exactly the same thing during a Road Ahead meeting in Oslo on the 16th of October. Two updates have been and gone since then, and yet I’ve seen no movement on this front.
Has anyone managed to make “Extract to markup” compatible with ArcGIS 10.1 yet?
James0 -
Sorry to hear of your frustration Steven and James. I’d like to address both your posts. First, keeping promises is sacred to me. Given this, and the uncertainties around product development and related prioritization, I never make promises when I speak about the road ahead. As with my presentation in Oslo, I make clear that what I am sharing is predictive, forward looking, and subject to change (“Current estimates... not commitments” is the terminology on my slide). Second, on the topics of parity between Web ADF/REST and ArcIMS-gen/ArcGIS Server-gen technology (I speak of both), we’ve been working through a list of key features for a couple years now, and Dynamic Symbolization was the last major feature on that list. For us, this milestone wasn’t so much about a fulfilling a specific promise or formal obligation (neither exist); it’s about achieving a symbolic goal we’ve been working towards for many years now; that ArcIMS and Web ADF can finally be put to rest, once and for all. I’ve stated on several occasions that Geocortex Viewer for Silverlight 1.7 was a milestone release for us because it included dynamic symbolization which was not possible with ArcGIS Server until 10.1 (and a reason some clients had not yet switched off their remaining ArcIMS apps). Time permitting, I usually qualify parity observations with an acknowledgement that I’m referring to the common, broadly applicable features. This is because over the last decade we’ve also made lots of highly specialized, client funded product additions that will likely only get redeveloped in REST if client funded. Still, I dropped the ball. I misjudged the importance to our clients of what I’ve considered to be relatively minor features (after all, “minor” is a matter of perspective). Perhaps we even missed a couple. I wish I’d stated that Geocortex Viewer for Silverlight 1.7 was a milestone release because it added in the last high visibility feature that was sorely missing with REST-gen technology, and that we now need to identify and complete any remaining lower-visibility capabilities that remain important to our clients. Third, the Extract Markup to Shapefile feature, which has been a topic of discussion elsewhere in the forums, has not dropped off our development radar. While I hope to see it included in the Geocortex Essentials 3.14 release this March, I’ll leave the decision to our development leads who are working hard to balance competing priorities. I hope this helps.0 -
Hi All,
Our product development team is currently allocated through March - we have a very busy quarter of R&D planned with releases scheduled for the end of February and the end of March. Nonetheless, we have been able to free up some room in the schedule to commit to the delivery of this feature within our March delivery.
That means that we will ship Geocortex Essentials 3.14 (the release following the 3.13 version scheduled for February) with the ability to create and return a Shapefile from a featureset via a REST endpoint. The Geocortex Viewer for Silverlight 1.10, which will ship alongside 3.14, will provide a tool to call the service in order to extract the current markup on the map, and provide the user with a downloadable shapefile.
Thank you for your ongoing feedback!
Drew.
0 -
Steven and Drew,
Thank you! And thank you for taking to the time to respond personally. I look forward to the 3.14/1.10 release in March!
Steve
0 -
Thank you Steven and Drew for your positive replies.
That has set my mind at ease and I can finally give our customers a more robust answer to their questions.
Keep up the good work!
James0 -
Just echoing the sentiments of those above... great response, and look forward to the release!
again, keep up the good work
Gareth
0 -
In addition, the module available for download from the Code Gallery has been updated to work with Viewer 1.8, so those of you depending on this sample should be able to continue to use it pending the release of Essentials 3.14 and Viewer 1.10. No changes to the Geoprocessing Tasks are required, and you should be able to just drop the new .xap file in as a replacement.
0 -
Thanks a ton! this is great that we can still use tool and I am really looking forward for the new module as well.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
8 Kommentare