GIS Schema

Schemas are crucial pieces of the application’s architecture. They are the key “translators” that allow the application to understand the unique architecture and attributes of your company’s data.

You have one schema for your tenant. You do not have separate schemas for each published feature service.

If you are a Designer XI customer, you can leverage your existing schema. In the Feeder Services plugin in Solution Center on the Additional Configuration subtab, you can toggle Use Designer GIS Schema to use your existing Designer XI schema for Feeder Services.

In the schema, you can establish the following configurations:

• Map components and fields to geodatabase features/object tables and fields.

• Map coded value domains to geodatabase domains.

• Check the completeness of mapping features to equipment specifications (specs). This is an optional configuration, but the benefit would be a quicker ADMS integration.

• Configure geodatabase non-network fields, with changes that should be treated as cause for marking the subnetworks and their related KV objects as stale data, which further makes them candidates for the next scheduled export process.

The schema mapping is grouped in four areas:

• Coded Value Domains

• Feature to Spec Mapping

• GRR Delta Detection

• Tables