ArcGIS Online
Last updated
Was this helpful?
Last updated
Was this helpful?
We have an ETL () that uses the component_arcgis_online_view Moped database view to push data about project components to an AGOL feature service with point, line, and combined_geometry layers (). This describes the workflow of adding, updating, or removing fields in this service and the coordination it takes with the DTS Geospatial team.
There are two downstream dependencies of this database view that can break:
(coordinate with the Geospatial team; see below)
(coordinate with the Data Science team; see below)
The database view and ETL GraphQL query must be updated with the new or updated field names.
Here is an example pull request: .
Stage code changes for new field
Submit a for the GIS team to add new field
Release or patch to introduce new field into ETL
Tell the Data Science team about this update so they can
Stage code change for field rename
Release or patch to introduce new field into ETL
Request GIS team remove the old field name now that it is unused
Stage code change for field removal
Release or patch to remove column from ETL
The ETL will not break with the changes up to this point. The next step can be performed anytime after removing the fields from the code to clean up the AGOL dataset.
Before making any changes to a feature service, check with the Geo team and let them know what we are trying to accomplish.
Once a token is retrieved and place in the URL, the UI can be used to make a POST request through the form with new configuration in JSON format placed in the input labeled Update Service Definition.
To update the sanitization config, the following JSON was used.
Once you press the Update Definition button to send the payload, you will see a success message or an error if the JSON is invalid.
Submit a for the GIS team to add new column name. We keep the old column name to keep the ETL compatible and working with both the new and old field names
Tell the Data Science team about this update so they can
Submit a for the GIS team to remove the field
Tell the Data Science team about this update so they can
Settings on the feature service level (the AGOL side) can be updated using the Admin Service Catalog endpoint described . The only setting that we have changed so far is the xssPreventionInfo setting to place the responsibility of sanitizing invalid HTML on the AGOL side.
To update this setting, go to .
You will need to fetch a token using the same mechanism we use in our . Using an API development tool like Postman or Insomnia can be helpful for this, and it will require the same secrets used in the code.
To update configuration, you should include only the configuration that you are trying to update. Including unneeded configuration will produce errors. See this for more context.