Admin Boundary Module¶

File: computing/misc/admin_boundary.py

Overview¶

This module handles administrative boundary processing for geographic data, specifically extracting tehsil/block-level boundaries and synchronizing them across multiple geospatial platforms.

Purpose¶

Processes Indian administrative boundaries (state → district → tehsil/block hierarchy) and distributes them to: - Google Earth Engine (GEE) - Cloud-based geospatial analysis platform - GeoServer - Open-source geospatial data server - Database - Layer metadata storage - STAC catalog - SpatioTemporal Asset Catalog specifications

Architecture¶

flowchart TD
    A[Celery Task Triggered] --> B[ee_initialize]
    B --> C[clip_block_from_admin_boundary]
    C --> D{Census 2011 Data Available?}
    D -->|Yes| E[Filter by TEHSIL column]
    D -->|No| F[Load SOI Tehsil Data]
    F --> G{Census data exists?}
    G -->|Yes| H[Intersect SOI with Census]
    G -->|No| I[Use SOI boundary directly]
    E --> J[Build FeatureCollection]
    H --> J
    I --> J
    J --> K[create_shp_files]
    K --> L[Generate Shapefile]
    L --> M{GEE Asset Exists?}
    M -->|No| N[upload_shp_to_gee]
    M -->|Yes| O[make_asset_public]
    N --> O
    O --> P[save_layer_info_to_db]
    P --> Q[push_shape_to_geoserver]
    Q --> R{Success?}
    R -->|Yes| S[Generate STAC specs]
    S --> T[Update sync status]
    T --> U[Return True]
    R -->|No| V[Return False]

Components¶

Main Task: generate_tehsil_shape_file_data()¶

Location: Line 27

A Celery task decorated with @app.task(bind=True) that orchestrates the entire pipeline.

Parameters: | Parameter | Type | Description | |-----------|------|-------------| | state | str | State name | | district | str | District name | | block | str | Block/tehsil name | | gee_account_id | int | GEE account identifier |

Processing Steps:

Data Extraction: clip_block_from_admin_boundary()¶

Location: Line 102

Handles the complex logic of extracting block boundaries from multiple data sources.

Data Source Priority: 1. Primary: Census 2011 data (contains village boundaries with demographic attributes) 2. Fallback: Survey of India (SOI) tehsil boundaries

Logic Flow:

flowchart LR
    subgraph Input Sources
        A[Census 2011 GeoJSON]
        B[SOI Tehsil GeoJSON]
    end

    subgraph Processing Logic
        C{TEHSIL column exists?}
        D[Direct filter]
        E[SOI filter + intersection]
    end

    subgraph Output
        F[FeatureCollection with village-level attributes]
    end

    A --> C
    C -->|Yes| D
    C -->|No| B
    B --> E
    A --> E
    D --> F
    E --> F

Shapefile Creation: create_shp_files()¶

Location: Line 86

Converts the GeoJSON FeatureCollection to ESRI Shapefile format: - Writes JSON intermediate file - Calls generate_shape_files() utility

Data Attributes¶

When census data is available, each village feature includes:

Identifiers¶

Demographic Metrics¶

Social Categories¶

Literacy¶

Asset Indices¶

Integration Points¶

computing/misc/admin_boundary.py
├── computing.utils
│   ├── generate_shape_files()     # JSON → Shapefile conversion
│   ├── push_shape_to_geoserver()  # GeoServer publication
│   ├── save_layer_info_to_db()    # Database persistence
│   └── update_layer_sync_status() # Status tracking
├── utilities.gee_utils
│   ├── ee_initialize()            # GEE authentication
│   ├── valid_gee_text()           # Text sanitization
│   ├── get_gee_asset_path()       # Asset path generation
│   ├── is_gee_asset_exists()      # Asset existence check
│   ├── create_gee_directory()     # GEE folder creation
│   ├── upload_shp_to_gee()        # Shapefile upload
│   └── make_asset_public()        # ACL management
└── computing.STAC_specs
    └── generate_vector_stac()     # STAC metadata generation

Constants Used¶

Output¶

GEE Asset¶

• Naming: admin_boundary_{district}_{block}
• Path: projects/earthengine-legacy/assets/projects/nrm/{state}/{district}/{block}/admin_boundary_{district}_{block}

GeoServer Layer¶

• Workspace: panchayat_boundaries
• Format: WMS/WFS service

STAC Entry¶

• Layer Name: admin_boundaries_vector

Usage¶

# Trigger via Celery
from computing.misc.admin_boundary import generate_tehsil_shape_file_data

result = generate_tehsil_shape_file_data.delay(
    state="Rajasthan",
    district="Jaipur",
    block="Sanganer",
    gee_account_id=1
)

Error Handling¶

• Handles missing Census 2011 data gracefully by falling back to SOI boundaries
• Continues processing even if census data file is not found
• Logs errors for debugging

Dependencies¶

• ee (Google Earth Engine Python API)
• geopandas - Geospatial data manipulation
• shapely - Geometry operations
• geojson - GeoJSON handling
• Celery - Distributed task queue