Disable Topology
- URL:https://<utlitynetworkservice-url>/disableTopology(POST only)
- Version Introduced:10.6
Description
Displaying the network topology for a utility network may be done by the owner. When the topology is disabled, feature and association edits do not generate dirty areas. When the topology is disabled:
- We delete all the rows at the current moment in the topology tables (however, the topology is not physically deleted).
- During data loading, no dirty areas will be created.
- Remaining error features still exist and can be cleaned up without the overhead of dirty areas.
- The owner of the network may expand the service territory of the network.
- Analysis and diagram generation can't be performed if the topology is not present.
The topology may be disabled in the DEFAULT or child version.
- If disabled in a child version, it may not be later enabled in the child version.
- The purpose of disabling the topology in a child version is optimizing appending data (so individual dirty areas are not created).
- We want to avoid enabling topology in a child version because of the potential impact on all versions with the significant number of rows created in the internal topology tables.
- In order to add or remove rules (alter the schema of the topology), the topology must be disabled in the DEFAULT version.
- Existing versions will see the modified definition during the subsequent validatation.
License:Request Parameters
Parameter | Details |
|---|---|
| f | Description: Optional parameter representing the output format of the response. The default response format is html. Values: html | json. |
| gdbVersion | Description: Optional parameter specifying the name of the geodatabase version (default is DEFAULT). Syntax: gdbVersion=<version> |
| sessionId | Description: Optional parameter representing the token (guid) used to lock the version. If the calling client is editing a named version, the sessionId must be provided; if the client is editing DEFAULT, the version may not be locked and the sessionId should not be specified. Syntax: sessionId=<guid> |
JSON Response Syntax
JSON response:
{
"moment" : <datetime>,
"success" : <true | false>,
"error" : { // only if success is false
"extendedCode" : <HRESULT>,
"message" : <error message>,
"details" : [ <detail> ]
}
}