Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Environment Variables 

Description

 egov.services.egov_mdms.hostname

 Host name for MDMS service.

egov.services.egov_mdms.searchpath

MDMS Search URL.

 egov.service.egov.mdms.moduleName

 MDMS module which contain boundary master.

egov.service.egov.mdms.masterName

MDMS master file which contain boundary detail.

Deployment Details

  1. Add/Update the mdms master file which contain boundary data of ULB’s.

  2. Add Role-Action mapping for egov-location API’s.

  3. Deploy/Redeploy the latest version of egov-mdms service.

  4. Fill the above environment variables in egov-location with proper values.

  5. Deploy the latest version of egov-location service.

...

Attribute Name

Description

 tenantId

 The The tenantId (ULB code) for which the boundary data configuration is defined.

 moduleName

 The The name of the module where TenantBoundary master is present.

TenantBoundary.hierarchyType.code

Unique code of the hierarchy type.

TenantBoundary.hierarchyType.name

Unique name of the hierarchy type.

TenantBoundary.boundary.id

id Id of boundary defined for particular hierarchy.

boundaryNum

sequence Sequence number of boundary attribute defined for the particular hierarchy.

name

Name of the boundary like Block 1 or Zone 1 or City name.

localname

Local name of the boundary.

longitude

Longitude of the boundary.

latitude

Latitude of the boundary.

label

Label of the boundary.

code

Code of the boundary.

children

Details of its sub-boundaries.

Integration

 Integration Scope

...

  1. To integrate, host of egov-location should be overwritten in helm chart.

  2. /boundarys/_searchshould be added as the search endpoint for searching boundary details based on tenant Id, Boundary Type, Hierarchy Type etc.

  3. /geography/_search should be added as the search endpoint .This method handles all requests related to geographical boundaries by providing appropriate GeoJson and other associated data based on tenantId or lat/long etc.

  4. /tenant/_search should be added as the search endpoint. This method tries to resolve a given lat, long to a corresponding tenant, provided there exists a mapping between the reverse geocoded city to tenant.

  5. The MDMS Tenant boundary master file should be loaded in MDMS service.

...