Okinawa Mangrove Temporal Analysis

Satellite-Based Environmental Monitoring Using Google AlphaEarth Deep Learning Embeddings

Interactive Temporal Analysis Maps

Click on region boundaries or red star markers to view detailed change statistics and coordinates

🌊 Hiyagon Wetland (ęÆ”å±‹ę ¹ę¹æåœ°) | 11 Sub-Regions

Site: Hiyagon Wetland, Okinawa
Analysis: Fine-grained 11 sub-region segmentation
Features: Tidal zone dynamics, vegetation gradient analysis
Data Source: manglobal.or.jp/okinawahonto/hiyagon

šŸļø Kin/Kokuba River Mangroves (é‡‘ę­¦ćƒ»å›½å “å·)

Site: Kin Town / Kokuba River mangrove forests
Analysis: Multi-patch mangrove ecosystem monitoring
Features: River corridor dynamics, urban interface zones
Conservation: Protected zones referenced from manglobal.or.jp database
How to Use:
  • šŸ—ŗļø Toggle between satellite and street view using layer control
  • šŸ” Zoom in/out to explore different spatial scales
  • ⭐ Red stars mark the most environmentally dynamic locations (highest AlphaEarth vector change 2017-2023)
  • šŸ“Š Click any region boundary to view change score statistics
  • šŸ“ Click hotspot markers to see coordinates and detailed change metrics

Methodology: AlphaEarth Temporal Change Detection

Objective: Identify and quantify temporal changes in Okinawan mangrove ecosystems using Google AlphaEarth satellite embeddings to detect environmental hotspots and assess ecosystem health over time (2017-2023).

1AlphaEarth Feature Extraction

Google AlphaEarth is a deep learning model trained on massive satellite imagery datasets that generates 65-dimensional feature vectors for each satellite image pixel. These embeddings capture complex environmental patterns including spectral characteristics, textural information, seasonal variations, and vegetation indicators that are not easily discernible through traditional spectral band analysis.

Data Acquisition:

2Spatial Hotspot Identification

Most dynamic points are identified using a simple Euclidean distance metric in the 65-dimensional AlphaEarth embedding space. For each geographic point within the mangrove regions, we compute the vector distance between 2017 and 2023 feature vectors:

Temporal Change Calculation: Ī” = ||vā‚‚ā‚€ā‚‚ā‚ƒ - v₂₀₁₇||ā‚‚ = √(Ī£įµ¢ā‚Œā‚€ā¶ā“ (vįµ¢,ā‚‚ā‚€ā‚‚ā‚ƒ - vįµ¢,₂₀₁₇)²) where v is the 65-dimensional AlphaEarth feature vector (A00-A64)

Hotspot Identification Process:

  1. Point-wise temporal analysis: For each unique geographic coordinate, calculate the Euclidean distance between 2017 and 2023 feature vectors in the 65-dimensional space
  2. Regional ranking: Within each mangrove region, rank all points by their change magnitude (Euclidean distance)
  3. Hotspot selection: Top 3-5 points per region with highest Euclidean distances are marked as environmental hotspots (red star markers on maps)
  4. Validation: Cross-reference with year-to-year consistency to avoid noise artifacts

These hotspots represent locations where the satellite-derived environmental signature has changed most significantly, potentially indicating:

3Region Boundary Extraction

Mangrove region polygons were obtained directly from the Mangrove Global Initiative Japan (manglobal.or.jp) Google Maps database, which provides pre-digitized conservation zone boundaries for mangrove sites across Okinawa.

Direct KML Download Process:
Region boundaries are downloaded directly from the Google Maps interface at:
https://www.google.com/maps/d/viewer?mid=1UWET-y7O5wSp-iWmha1GEGJdwHEU1rQ
  1. Access Google Maps Database: Navigate to the manglobal.or.jp Google Maps link containing pre-digitized mangrove conservation zones
  2. Select Region of Interest: Identify the specific mangrove site (e.g., Hiyagon Wetland, Kin mangroves, Kokuba River)
  3. Download KML:
    • Click the ā‹® menu icon on the Google Maps interface
    • Select "Export to KML/KMZ"
    • Choose KML format (not KMZ) for direct Python processing
    • Download saves polygon geometries with WGS84 coordinates
  4. Multi-Region Processing: For sites with multiple conservation zones (e.g., Hiyagon Wetland with 11 sub-regions), the KML file contains all polygon boundaries as separate Placemark features
  5. Coordinate Validation: Verify downloaded KML coordinates align with AlphaEarth pixel locations (WGS84 coordinate system standard ensures compatibility)
Data Integration: Using pre-digitized conservation boundaries from manglobal.or.jp's Google Maps database ensures analysis focuses on expert-validated mangrove habitats. This approach combines authoritative conservation zone mapping with automated satellite feature extraction (AlphaEarth) for scalable environmental monitoring.

4Regional Statistics & Visualization

For each region and year, we compute:

Interactive maps display:

Analysis Results & Visualizations

Hiyagon Wetland (ęÆ”å±‹ę ¹ę¹æåœ°) Temporal Analysis

Comprehensive temporal change analysis of Hiyagon Wetland covering 2017-2024. The visualization below shows six analytical panels revealing environmental dynamics across 11 sub-regions.

Key Findings:
  • Most Dynamic Region: Region_12 (Change Score: 0.5940)
  • Temporal Coverage: 8 years of AlphaEarth embeddings (2017-2024)
  • Top Hotspot: 127.828491°E, 26.312437°N (Euclidean distance: 0.4168)
  • Data Points: 896 satellite pixels analyzed across 4 major regions
Hiyagon Wetland Temporal Analysis - Six-panel comprehensive visualization

Panel Descriptions:
Top-left: Regional change scores | Top-center: Cumulative change in most dynamic region | Top-right: Year-to-year changes comparison
Bottom-left: Spatial distribution with KML boundaries | Bottom-center: Feature vector magnitudes over time | Bottom-right: Maximum point changes per region

Kin/Kokuba River Mangroves Analysis

Note: Kin mangrove analysis encountered coordinate system alignment issues between AlphaEarth pixel locations and KML region boundaries. Zero points were assigned to regions, indicating a potential datum mismatch. Further investigation required to ensure WGS84 coordinate consistency across datasets.

Technical Issue: The Kin mangrove dataset shows 28,760 satellite pixels but none fall within the downloaded KML polygon boundaries. This suggests either:
  • Coordinate reference system mismatch (CSV vs KML)
  • Incorrect KML file selection from Google Maps database
  • Geographic offset in AlphaEarth pixel coordinates
Solution: Verify CSV coordinate ranges match KML polygon bounds and ensure both use WGS84 datum.