I'm exploring options a simple app to let multiple users test different ways of assigning polygons to larger territories. They don't need to work collaboratively, but they each need to be able to save their work. The FeatureLayer editing approach looks appealing, but it would not be acceptable to have "last one-to-save wins" editing. Instead, I'd like for edits to be cached on the client and then posted later, after authentication, as assignment lists (probably via a non-spatial web service.)
It LOOKS like this might work if I simply omitted the .applyEdits call -- would it? If I did, would I need a feature service to support it, or would a map service be sufficient?
The old-fashioned alternative would be to query all the features, add them to a graphics layer, and render that. Splitting the difference, it also seems to be possible to load features into a featurelayer manually using .FeatureCollection; that would guarantee client-side edits, and seems like an appropriate option.
Thanks in advance for any thoughts you have to share.
Charlie Richman
DC Office of Planning
