Audience: Administrators
Understand how to add new spatial operations and layers to GeoSmartOperation without modifying the core product.
Related articles
Understand the extension model
GeoSmartOperation includes standard spatial operations and layers, but is designed for extension. Extensions deploy as installable packages that load automatically when the service starts.
Using extensions avoids modifying the standard product, providing the following benefits:
-
Custom builds are no longer required for project-specific capabilities.
-
System upgrades do not overwrite custom configurations.
-
Extensions can be installed, updated, or removed independently.
This approach replaces legacy custom builds, such as ArcGIS Server Object Extensions.
Add spatial operations
Extensions can add new spatial operations to the default set.
Once installed, new operations function like built-in features: they appear in the service operations list, follow standard monitoring and progress reporting, and return results through the standard interface. Long-running tasks execute in the background.
Use the provided reference template to build new operations.
If an extension operation uses an existing standard operation name, the system reports a naming conflict instead of overwriting the standard operation.
Add layers
Extensions can add layer definitions to expose new datasets on the map without publishing through Esri infrastructure.
Extension layers function identically to standard layers: they are fully discoverable, expose metadata, and support standard query interfaces and field aliases.
The service validates layer definitions at startup:
-
Invalid definitions trigger explicit validation errors before use.
-
Duplicate service identifiers or addresses are rejected explicitly.
Maintain standard security and logging
Extensions operate under standard system rules and security frameworks:
-
Access requires valid NextGen Geo authentication.
-
Extension layers enforce standard user visibility rules.
-
Extension operations record full details in system logs for traceability.
What's next
-
To learn more about layer field aliases, see Understand and configure field aliases.