Robert Scheitlin, GISP wow you've hit out of the park! I'm beginning to upgrade sites to WAB 2.1 along with your widgets and I can see your eSearch's ability to *Export to Feature Collection* is a game-changer for end users. They already LOVE Jeremie Cornet's eDraw -- because of the ability to draw a polgyon (let's say of "Project Area 1") and export, send to another user, they can modify, then send back. Your widget now offers the ability to leverage EXISTING geometry, in other words, users can use your widget to select a few parcels, or a few street centerlines for example, then Export. However, it would be incredible if they could export existing features, let's say parking lot, send to someone, then they can load it up and review it. So the feature stands by itself.
I immediately then looked for an "Upload" button in your widget. There is none. I'd highly suggest this, to implement this kind of two-way use. However!!! The good news for all eSearch / eDraw users -- Jeremie Cornet's eDraw can load your eSearch features.json featureset collection results, Robert! Now, it does not bring back in symbology. I presume if you were to implement an Upload button, that would be included perhaps. And eDraw does not bring back in attributes. It just shows weird 'bearings' as users will see. I tested with the latest eDraw widget. Although I noticed they are of course included in the FeatureCollection.json export file. However even with these two considerations, it will still be immediately popular with our users across the city. Or perhaps you two could collaborate??
Because the utlimate workflow would be true two-way: User 1 selects a Parking Lot from your eSearch and exports it. User 2 then loads it (with eSearch or maybe eDraw) and modifies some geometry or attributes, then passes it back. Currently Jeremie's eDraw does this but again the usefulness in eSearch somehow integrating into this concept is that it takes existing feature(s) geometry and attributes and even symbology allowing a second user to simply modify it a bit. It would massively scale up to save time of course with this concept as well. Thoughts Robert and others? I know it's a tall order and perhaps more of a theoretical at this point but I couldn't help but think of this after discovering your eSearch results loaded so nicely into eDraw.
