In ArcGIS Velocity, you can configure both real-time and big data analytics to write output records to a hosted feature layer. As the creator and owner of an analytic, you can decide who has access to the data in these feature layers through a combination of sharing and editing settings.
In ArcGIS Velocity, real-time and big data analytics automatically facilitate edits made to output hosted feature layers. This is done as part of the analytic processing pipeline rather than manual editing that may traditionally be done by an editor user. This does not mean that user-based editor workflows cannot be performed. Consider both workflows when deciding who needs access to edit the data.
By default, the owner of an analytic and its output feature layers can make edits to the layers even if editing is not enabled. This is useful if a layer requires infrequent changes outside the analytic. If you do not need to make the layer available for post-process editing by users in the organization, and you want the analytic to be the authoritative source for all layer edits, do not enable editing.
If you want other users in the organization to be able to edit data in a hosted feature layer created with ArcGIS Velocity, enable editing on the layer and share it with the appropriate group. When sharing the layer with a group or the organization, only those members who are assigned a role that includes editing privileges can edit the feature layer. A future release of ArcGIS Velocity will support public sharing of layers and anonymous access editing.
Once a hosted feature layer is created by an analytic, you must decide what type of editing is allowed after you enable editing. With editing enabled, three options are available that allow users to control the type of editing necessary: add, update, and delete. For example, you can configure a layer so editors can update existing attributes but not add records or delete records. You can also configure a layer so editors can add records but not delete records or update attributes.
If users editing the layer are performing the same type of edits, you only need a single hosted feature layer with one setting. As the owner of an analytic, you have full editing control on the layer regardless of how editing settings have been configured for other users.
If different users need to perform different types of edit operations, a single hosted feature layer is not sufficient. To meet this need, create a hosted feature layer view from the hosted feature layer, enable editing options on the view, and share the view with the appropriate group. You can create multiple views from a single hosted feature layer to meet different editing requirements if necessary.
Similar to when different editors need different levels of editing access, you can create hosted feature layer views to limit editor access. You can enable editing on the hosted feature layer and share it with only the group or groups whose users need to edit the layer. Next, create a hosted feature layer view from the editable hosted feature layer and disable editing for the view. Share the view with the groups who need read-only access to the data. This is useful if you want the entire organization to view the features but only need a few users to edit it.
You can enable editor tracking on a hosted feature layer when first configuring a Feature Layer (new) output. This adds fields to the layer to record the name of the user who creates a feature and when it was created, as well as fields to record who last edited a feature or its attributes and when it was edited. When an analytic is used to automatically facilitate edits to a hosted feature layer, the creator and editor username fields can be populated from either the analytic owner's user name or a field value in the incoming data.
When first configuring a Feature Layer (new) output and enabling editor tracking, the only option available for the creator/editor user name is My username. This assumes the creator and editor user name is the owner of the analytic. Once the Feature Layer (new) output is incorporated into an analytic such as to the output of a tool, you can edit the feature layer output to choose a string field for the creator/editor user name. In this case, the creator and editor user name is populated using the values from the streaming data.
Enabling editor tracking provides additional control over the types of queries and edits users can make to the data. For example, you can limit editors to only edit the features they add to the layer or only allow editors to view the features they add. This is accomplished through ownership-based access control.
Limit editing to a geographic area
If you need to limit editing to specific geographic areas, you can create hosted feature layer views. This is useful, for example, if a geographic area requires feature edits or is the only area you want other users to see. You can create a view, define an area of interest, and share it with a group whose users need to edit or view data in that area. Then create views for each additional area of interest required and share those views with the appropriate groups. For more information, see Create hosted feature layer views.
Limit editing to particular features or attributes
For example, if you have a single hosted feature layer that contains driver and vehicle information updated in real time, you can create views with the following definitions:
- Create a view for users who manage the drivers. Configure the view so only those fields that store driver information are available to those users.
- Create another view for users who manage vehicle information. Set a definition for the view that only makes available the fields containing the vehicle information and share the view with the group that manages vehicle information.
- Create another view for users who support driving operations. Set a definition for the view that makes available the location of each vehicle and other drive-time fields or attributes with a group composed of the operations staff.