Skip to main content
Glama

getis_ord_g_local

Identify local spatial clusters and hotspots in geographic data by analyzing spatial autocorrelation patterns within shapefiles.

Instructions

Local Getis-Ord G.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shapefile_pathYes
dependent_varNoLAND_USE
target_crsNoEPSG:4326
distance_thresholdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main execution function for getis_ord_g_local tool: loads data, creates spatial weights, computes local Getis-Ord G* using esda.G_Local, handles islands with KNN fallback or filtering.
    @gis_mcp.tool()
    def getis_ord_g_local(shapefile_path: str, dependent_var: str = "LAND_USE", target_crs: str = "EPSG:4326",
                          distance_threshold: float = 100000) -> Dict[str, Any]:
        """Local Getis-Ord G."""
        gdf, y, w, (threshold, unit), err = pysal_load_data(shapefile_path, dependent_var, target_crs, distance_threshold)
        if err:
            return {"status": "error", "message": err}
    
        # Handle islands - if all points are islands, fall back to KNN weights for connectivity
        import libpysal
        if w.islands:
            if len(w.islands) == len(gdf):
                # All points are islands - fall back to KNN weights
                try:
                    # Use k=4 for a 5x5 grid to ensure connectivity
                    w = libpysal.weights.KNN.from_dataframe(gdf, k=4)
                    w.transform = 'r'
                except Exception as e:
                    return {"status": "error", "message": f"All units are islands and KNN fallback failed: {str(e)}"}
            else:
                # Some islands - filter them out
                keep_idx = [i for i in range(len(gdf)) if i not in set(w.islands)]
                if len(keep_idx) == 0:
                    return {"status": "error", "message": "All units are islands (no neighbors). Try increasing distance_threshold."}
                # Filter data
                gdf_filtered = gdf.iloc[keep_idx].reset_index(drop=True)
                y_filtered = y[keep_idx]
                # Rebuild weights without islands using the same threshold
                w_filtered = libpysal.weights.DistanceBand.from_dataframe(
                    gdf_filtered, 
                    threshold=threshold,  # Use the effective threshold already calculated in pysal_load_data
                    binary=False
                )
                w_filtered.transform = 'r'
                gdf, y, w = gdf_filtered, y_filtered, w_filtered
    
        import esda
        stat = esda.G_Local(y, w)
        preview = gdf[['geometry', dependent_var]].head(5).copy()
        preview['geometry'] = preview['geometry'].apply(lambda g: g.wkt)
    
        return {
            "status": "success",
            "message": f"Local Getis-Ord G completed successfully (threshold: {threshold} {unit})",
            "result": {
                "G_local": stat.Gs.tolist() if hasattr(stat.Gs, 'tolist') else list(stat.Gs),
                "p_values": stat.p_sim.tolist() if hasattr(stat.p_sim, 'tolist') else list(stat.p_sim),
                "z_scores": stat.z_sim.tolist() if hasattr(stat.z_sim, 'tolist') else list(stat.z_sim),
                "data_preview": preview.to_dict(orient="records")
            }
        }
  • Shared helper function for loading shapefile, reprojecting, extracting dependent variable, and creating row-standardized distance band spatial weights; used by getis_ord_g_local and other PySAL tools.
    def pysal_load_data(shapefile_path: str, dependent_var: str, target_crs: str, distance_threshold: float):
        """Common loader and weight creation for esda statistics."""
        if not os.path.exists(shapefile_path):
            return None, None, None, None, f"Shapefile not found: {shapefile_path}"
    
        gdf = gpd.read_file(shapefile_path)
        if dependent_var not in gdf.columns:
            return None, None, None, None, f"Dependent variable '{dependent_var}' not found in shapefile columns"
    
        gdf = gdf.to_crs(target_crs)
    
        effective_threshold = distance_threshold
        unit = "meters"
        if target_crs.upper() == "EPSG:4326":
            effective_threshold = distance_threshold / 111000
            unit = "degrees"
    
        y = gdf[dependent_var].values.astype(np.float64)
        import libpysal
        w = libpysal.weights.DistanceBand.from_dataframe(gdf, threshold=effective_threshold, binary=False)
        w.transform = 'r'
    
        for island in w.islands:
            w.weights[island] = [0] * len(w.weights[island])
            w.cardinalities[island] = 0
    
        return gdf, y, w, (effective_threshold, unit), None
  • Import statement that loads pysal_functions.py, triggering registration of getis_ord_g_local via @gis_mcp.tool() decorator.
    from .pysal_functions import * 
  • Resource endpoint listing available ESDA/PySAL operations including getis_ord_g_local.
    @gis_mcp.resource("gis://operations/esda")
    def get_spatial_operations() -> Dict[str, List[str]]:
        """List available spatial analysis operations. This is for esda library. They are using pysal library."""
        return {
            "operations": [
                "getis_ord_g",
                "morans_i",
                "gearys_c",
                "gamma_statistic",
                "moran_local",
                "getis_ord_g_local",
                "join_counts",
                "join_counts_local",
                "adbscan"
            ]
        }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate if this is a read-only or mutating operation, what permissions or inputs are required, how it handles errors, or what the output entails (e.g., statistical results). For a tool with 4 parameters and an output schema, this lack of behavioral context is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single phrase 'Local Getis-Ord G', which is under-specified rather than concise. It lacks any structuring (e.g., front-loaded purpose, usage notes) and wastes the opportunity to provide essential context. While brief, it doesn't earn its place by adding value beyond the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (spatial statistics tool with 4 parameters, no annotations, and an output schema), the description is completely inadequate. It doesn't explain the tool's function, parameter meanings, or behavioral traits, relying solely on the output schema for return values. For a specialized tool in a server with many siblings, this leaves critical gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning none of the 4 parameters are documented in the schema. The description adds no semantic information about parameters like 'shapefile_path', 'dependent_var', 'target_crs', or 'distance_threshold', failing to compensate for the schema gap. This leaves the agent guessing about their purposes and formats.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Local Getis-Ord G' is a tautology that restates the tool name without explaining what it does. It doesn't specify the verb (e.g., calculate, compute) or the resource (e.g., spatial autocorrelation statistic for geographic data), leaving the purpose vague. Compared to siblings like 'moran_local' or 'gearys_c', it fails to distinguish itself as a specific spatial analysis method.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context (e.g., for hotspot detection in spatial data), prerequisites, or exclusions, nor does it reference sibling tools like 'getis_ord_g' (global version) or other local spatial statistics (e.g., 'moran_local'). This leaves the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mahdin75/gis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server