ruvector/examples/data/framework/docs/GEOSPATIAL_CLIENTS.md
rUv 38d93a6e8d feat: Add comprehensive dataset discovery framework for RuVector (#104)
* feat: Add comprehensive dataset discovery framework for RuVector

This commit introduces a powerful dataset discovery framework with
integrations for three high-impact public data sources:

## Core Framework (examples/data/framework/)
- DataIngester: Streaming ingestion with batching and deduplication
- CoherenceEngine: Min-cut based coherence signal computation
- DiscoveryEngine: Pattern detection for emerging structures

## OpenAlex Integration (examples/data/openalex/)
- Research frontier radar: Detect emerging fields via boundary motion
- Cross-domain bridge detection: Find connector subgraphs
- Topic graph construction from citation networks
- Full API client with cursor-based pagination

## Climate Integration (examples/data/climate/)
- NOAA GHCN and NASA Earthdata clients
- Sensor network graph construction
- Regime shift detection using min-cut coherence breaks
- Time series vectorization for similarity search
- Seasonal decomposition analysis

## SEC EDGAR Integration (examples/data/edgar/)
- XBRL financial statement parsing
- Peer network construction
- Coherence watch: Detect fundamental vs narrative divergence
- Filing analysis with sentiment and risk extraction
- Cross-company contagion detection

Each integration leverages RuVector's unique capabilities:
- Vector memory for semantic similarity
- Graph structures for relationship modeling
- Dynamic min-cut for coherence signal computation
- Time series embeddings for pattern matching

Discovery thesis: Detect emerging patterns before they have names,
find non-obvious cross-domain bridges, and map causality chains.

* feat: Add working discovery examples for climate and financial data

- Fix borrow checker issues in coherence analysis modules
- Create standalone workspace for data examples
- Add regime_detector.rs for climate network coherence analysis
- Add coherence_watch.rs for SEC EDGAR narrative-fundamental divergence
- Add frontier_radar.rs template for OpenAlex research discovery
- Update Cargo.toml dependencies for example executability
- Add rand dev-dependency for demo data generation

Examples successfully detect:
- Climate regime shifts via min-cut coherence analysis
- Cross-regional teleconnection patterns
- Fundamental vs narrative divergence in SEC filings
- Sector fragmentation signals in financial data

* feat: Add working discovery examples for climate and financial data

- Add RuVector-native discovery engine with Stoer-Wagner min-cut
- Implement cross-domain pattern detection (climate ↔ finance)
- Add cosine similarity for vector-based semantic matching
- Create cross_domain_discovery example demonstrating:
  - 42% cross-domain edge connectivity
  - Bridge formation detection with 0.73-0.76 confidence
  - Climate and finance correlation hypothesis generation

* perf: Add optimized discovery engine with SIMD and parallel processing

Performance improvements:
- 8.84x speedup for vector insertion via parallel batching
- 2.91x SIMD speedup for cosine similarity (chunked + AVX2)
- Incremental graph updates with adjacency caching
- Early termination in Stoer-Wagner min-cut

Statistical analysis features:
- P-value computation for pattern significance
- Effect size (Cohen's d) calculation
- 95% confidence intervals
- Granger-style temporal causality detection

Benchmark results (248 vectors, 3 domains):
- Cross-domain edges: 34.9% of total graph
- Domain coherence: Climate 0.74, Finance 0.94, Research 0.97
- Detected climate-finance temporal correlations

* feat: Add discovery hunter and comprehensive README tutorial

New features:
- Discovery hunter example with multi-phase pattern detection
- Climate extremes, financial stress, and research data generation
- Cross-domain hypothesis generation
- Anomaly injection testing

Documentation:
- Detailed README with step-by-step tutorial
- API reference for OptimizedConfig and patterns
- Performance benchmarks and best practices
- Troubleshooting guide

* feat: Complete discovery framework with all features

HNSW Indexing (754 lines):
- O(log n) approximate nearest neighbor search
- Configurable M, ef_construction parameters
- Cosine, Euclidean, Manhattan distance metrics
- Batch insertion support

API Clients (888 lines):
- OpenAlex: academic works, authors, topics
- NOAA: climate observations
- SEC EDGAR: company filings
- Rate limiting and retry logic

Persistence (638 lines):
- Save/load engine state and patterns
- Gzip compression (3-10x size reduction)
- Incremental pattern appending

CLI Tool (1,109 lines):
- discover, benchmark, analyze, export commands
- Colored terminal output
- JSON and human-readable formats

Streaming (570 lines):
- Async stream processing
- Sliding and tumbling windows
- Real-time pattern detection
- Backpressure handling

Tests (30 unit tests):
- Stoer-Wagner min-cut verification
- SIMD cosine similarity accuracy
- Statistical significance
- Granger causality
- Cross-domain patterns

Benchmarks:
- CLI: 176 vectors/sec @ 2000 vectors
- SIMD: 6.82M ops/sec (2.06x speedup)
- Vector insertion: 1.61x speedup
- Total: 44.74ms for 248 vectors

* feat: Add visualization, export, forecasting, and real data discovery

Visualization (555 lines):
- ASCII graph rendering with box-drawing characters
- Domain-based ANSI coloring (Climate=blue, Finance=green, Research=yellow)
- Coherence timeline sparklines
- Pattern summary dashboard
- Domain connectivity matrix

Export (650 lines):
- GraphML export for Gephi/Cytoscape
- DOT export for Graphviz
- CSV export for patterns and coherence history
- Filtered export by domain, weight, time range
- Batch export with README generation

Forecasting (525 lines):
- Holt's double exponential smoothing for trend
- CUSUM-based regime change detection (70.67% accuracy)
- Cross-domain correlation forecasting (r=1.000)
- Prediction intervals (95% CI)
- Anomaly probability scoring

Real Data Discovery:
- Fetched 80 actual papers from OpenAlex API
- Topics: climate risk, stranded assets, carbon pricing, physical risk, transition risk
- Built coherence graph: 592 nodes, 1049 edges
- Average min-cut: 185.76 (well-connected research cluster)

* feat: Add medical, real-time, and knowledge graph data sources

New API Clients:
- PubMed E-utilities for medical literature search (NCBI)
- ClinicalTrials.gov v2 API for clinical study data
- FDA OpenFDA for drug adverse events and recalls
- Wikipedia article search and extraction
- Wikidata SPARQL queries for structured knowledge

Real-time Features:
- RSS/Atom feed parsing with deduplication
- News aggregator with multiple source support
- WebSocket and REST polling infrastructure
- Event streaming with configurable windows

Examples:
- medical_discovery: PubMed + ClinicalTrials + FDA integration
- multi_domain_discovery: Climate-health-finance triangulation
- wiki_discovery: Wikipedia/Wikidata knowledge graph
- realtime_feeds: News feed aggregation demo

Tested across 70+ unit tests with all domains integrated.

* feat: Add economic, patent, and ArXiv data source clients

New API Clients:
- FredClient: Federal Reserve economic indicators (GDP, CPI, unemployment)
- WorldBankClient: Global development indicators and climate data
- AlphaVantageClient: Stock market daily prices
- ArxivClient: Scientific preprint search with category and date filters
- UsptoPatentClient: USPTO patent search by keyword, assignee, CPC class
- EpoClient: Placeholder for European patent search

New Domain:
- Domain::Economic for economic/financial indicator data

Updated Exports:
- Domain colors and shapes for Economic in visualization and export

Examples:
- economic_discovery: FRED + World Bank integration demo
- arxiv_discovery: AI/ML/Climate paper search demo
- patent_discovery: Climate tech and AI patent search demo

All 85 tests passing. APIs tested with live endpoints.

* feat: Add Semantic Scholar, bioRxiv/medRxiv, and CrossRef research clients

New Research API Clients:
- SemanticScholarClient: Citation graph analysis, paper search, author lookup
  - Methods: search_papers, get_citations, get_references, search_by_field
  - Builds citation networks for graph analysis

- BiorxivClient: Life sciences preprints
  - Methods: search_recent, search_by_category (neuroscience, genomics, etc.)
  - Automatic conversion to Domain::Research

- MedrxivClient: Medical preprints
  - Methods: search_covid, search_clinical, search_by_date_range
  - Automatic conversion to Domain::Medical

- CrossRefClient: DOI metadata and scholarly communication
  - Methods: search_works, get_work, search_by_funder, get_citations
  - Polite pool support for better rate limits

All clients include:
- Rate limiting respecting API guidelines
- Retry logic with exponential backoff
- SemanticVector conversion with rich metadata
- Comprehensive unit tests

Examples:
- biorxiv_discovery: Fetch neuroscience and clinical research
- crossref_demo: Search publications, funders, datasets

Total: 104 tests passing, ~2,500 new lines of code

* feat: Add MCP server with STDIO/SSE transport and optimized discovery

MCP Server Implementation (mcp_server.rs):
- JSON-RPC 2.0 protocol with MCP 2024-11-05 compliance
- Dual transport: STDIO for CLI, SSE for HTTP streaming
- 22 discovery tools exposing all data sources:
  - Research: OpenAlex, ArXiv, Semantic Scholar, CrossRef, bioRxiv, medRxiv
  - Medical: PubMed, ClinicalTrials.gov, FDA
  - Economic: FRED, World Bank
  - Climate: NOAA
  - Knowledge: Wikipedia, Wikidata SPARQL
  - Discovery: Multi-source, coherence analysis, pattern detection
- Resources: discovery://patterns, discovery://graph, discovery://history
- Pre-built prompts: cross_domain_discovery, citation_analysis, trend_detection

Binary Entry Point (bin/mcp_discovery.rs):
- CLI arguments with clap
- Configurable discovery parameters
- STDIO/SSE mode selection

Optimized Discovery Runner:
- Parallel data fetching with tokio::join!
- SIMD-accelerated vector operations (1.1M comparisons/sec)
- 6-phase discovery pipeline with benchmarking
- Statistical significance testing (p-values)
- Cross-domain correlation analysis
- CSV export and hypothesis report generation

Performance Results:
- 180 vectors from 3 sources in 7.5s
- 686 edges computed in 8ms
- SIMD throughput: 1,122,216 comparisons/sec

All 106 tests passing.

* feat: Add space, genomics, and physics data source clients

Add exotic data source integrations:
- Space clients: NASA (APOD, NEO, Mars, DONKI), Exoplanet Archive, SpaceX API, TNS Astronomy
- Genomics clients: NCBI (genes, proteins, SNPs), UniProt, Ensembl, GWAS Catalog
- Physics clients: USGS Earthquakes, CERN Open Data, Argo Ocean, Materials Project

New domains: Space, Genomics, Physics, Seismic, Ocean

All 106 tests passing, SIMD benchmark: 208k comparisons/sec

* chore: Update export/visualization and output files

* docs: Add API client inventory and reference documentation

* fix: Update API clients for 2025 endpoint changes

- ArXiv: Switch from HTTP to HTTPS (export.arxiv.org)
- USPTO: Migrate to PatentSearch API v2 (search.patentsview.org)
  - Legacy API (api.patentsview.org) discontinued May 2025
  - Updated query format from POST to GET
  - Note: May require API authentication
- FRED: Require API key (mandatory as of 2025)
  - Added error handling for missing API key
  - Added response error field parsing

All tests passing, ArXiv discovery confirmed working

* feat: Implement comprehensive 2025 API client library (11,810 lines)

Add 7 new API client modules implementing 35+ data sources:

Academic APIs (1,328 lines):
- OpenAlexClient, CoreClient, EricClient, UnpaywallClient

Finance APIs (1,517 lines):
- FinnhubClient, TwelveDataClient, CoinGeckoClient, EcbClient, BlsClient

Geospatial APIs (1,250 lines):
- NominatimClient, OverpassClient, GeonamesClient, OpenElevationClient

News & Social APIs (1,606 lines):
- HackerNewsClient, GuardianClient, NewsDataClient, RedditClient

Government APIs (2,354 lines):
- CensusClient, DataGovClient, EuOpenDataClient, UkGovClient
- WorldBankGovClient, UNDataClient

AI/ML APIs (2,035 lines):
- HuggingFaceClient, OllamaClient, ReplicateClient
- TogetherAiClient, PapersWithCodeClient

Transportation APIs (1,720 lines):
- GtfsClient, MobilityDatabaseClient
- OpenRouteServiceClient, OpenChargeMapClient

All clients include:
- Async/await with tokio and reqwest
- Mock data fallback for testing without API keys
- Rate limiting with configurable delays
- SemanticVector conversion for RuVector integration
- Comprehensive unit tests (252 total tests passing)
- Full error handling with FrameworkError

* docs: Add API client documentation for new implementations

Add documentation for:
- Geospatial clients (Nominatim, Overpass, Geonames, OpenElevation)
- ML clients (HuggingFace, Ollama, Replicate, Together, PapersWithCode)
- News clients (HackerNews, Guardian, NewsData, Reddit)
- Finance clients implementation notes

* feat: Implement dynamic min-cut tracking system (SODA 2026)

Based on El-Hayek, Henzinger, Li (SODA 2026) subpolynomial dynamic min-cut algorithm.

Core Components (2,626 lines):
- dynamic_mincut.rs (1,579 lines): EulerTourTree, DynamicCutWatcher, LocalMinCutProcedure
- cut_aware_hnsw.rs (1,047 lines): CutAwareHNSW, CoherenceZones, CutGatedSearch

Key Features:
- O(log n) connectivity queries via Euler-tour trees
- n^{o(1)} update time when λ ≤ 2^{(log n)^{3/4}} (vs O(n³) Stoer-Wagner)
- Cut-gated HNSW search that respects coherence boundaries
- Real-time cut monitoring with threshold-based deep evaluation
- Thread-safe structures with Arc<RwLock>

Performance (benchmarked):
- 75x speedup over periodic recomputation
- O(1) min-cut queries vs O(n³) recompute
- ~25µs per edge update

Tests & Benchmarks:
- 36+ unit tests across both modules
- 5 benchmark suites comparing periodic vs dynamic
- Integration with existing OptimizedDiscoveryEngine

This enables real-time coherence tracking in RuVector, transforming
min-cut from an expensive periodic computation to a maintained invariant.

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-01-04 14:36:41 -05:00

14 KiB

Geospatial & Mapping API Clients

Comprehensive Rust client module for geospatial and mapping APIs, integrated with RuVector's semantic vector framework.

Overview

This module provides async clients for four major geospatial data sources:

  1. NominatimClient - OpenStreetMap geocoding and reverse geocoding
  2. OverpassClient - OSM data queries using Overpass QL
  3. GeonamesClient - Worldwide place name database
  4. OpenElevationClient - Elevation data lookup

All clients convert API responses to SemanticVector format for RuVector discovery and analysis.

Features

  • Async/await with Tokio runtime
  • Strict rate limiting (especially Nominatim 1 req/sec)
  • User-Agent headers for OSM services (required by policy)
  • SemanticVector integration with geographic metadata
  • Comprehensive tests with mock responses
  • GeoJSON handling where applicable
  • Retry logic with exponential backoff
  • GeoUtils integration for distance calculations

Installation

Add to your Cargo.toml:

[dependencies]
ruvector-data-framework = "0.1.0"
tokio = { version = "1.0", features = ["full"] }

Usage

1. NominatimClient (OpenStreetMap Geocoding)

Rate Limit: 1 request/second (STRICTLY ENFORCED)

use ruvector_data_framework::NominatimClient;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let client = NominatimClient::new()?;

    // Geocode: Address → Coordinates
    let results = client.geocode("1600 Pennsylvania Avenue, Washington DC").await?;
    for result in results {
        println!("Lat: {}, Lon: {}",
            result.metadata.get("latitude").unwrap(),
            result.metadata.get("longitude").unwrap()
        );
    }

    // Reverse geocode: Coordinates → Address
    let results = client.reverse_geocode(48.8584, 2.2945).await?;
    for result in results {
        println!("Address: {}", result.metadata.get("display_name").unwrap());
    }

    // Search places
    let results = client.search("Eiffel Tower", 5).await?;
    println!("Found {} places", results.len());

    Ok(())
}

Metadata Fields:

  • place_id, osm_type, osm_id
  • latitude, longitude
  • display_name, place_type
  • importance
  • city, country, country_code (if available)

2. OverpassClient (OSM Data Queries)

Rate Limit: ~2 requests/second (conservative)

use ruvector_data_framework::OverpassClient;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let client = OverpassClient::new()?;

    // Find nearby POIs
    let cafes = client.get_nearby_pois(
        48.8584,     // Eiffel Tower lat
        2.2945,      // Eiffel Tower lon
        500.0,       // 500 meters
        "cafe"       // amenity type
    ).await?;

    println!("Found {} cafes nearby", cafes.len());

    // Get road network in bounding box
    let roads = client.get_roads(
        48.85, 2.29,  // south, west
        48.86, 2.30   // north, east
    ).await?;

    println!("Found {} road segments", roads.len());

    // Custom Overpass QL query
    let query = r#"
        [out:json];
        node["amenity"="restaurant"](around:1000,40.7128,-74.0060);
        out;
    "#;
    let results = client.query(query).await?;

    Ok(())
}

Metadata Fields:

  • osm_id, osm_type
  • latitude, longitude
  • name, amenity, highway
  • osm_tag_* (all OSM tags preserved)

Common Amenity Types:

  • restaurant, cafe, bar, pub
  • hospital, pharmacy, school
  • bank, atm, post_office
  • park, parking, fuel

3. GeonamesClient (Place Name Database)

Rate Limit: ~0.5 requests/second (free tier: 2000/hour) Authentication: Requires username from geonames.org

use ruvector_data_framework::GeonamesClient;
use std::env;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let username = env::var("GEONAMES_USERNAME")?;
    let client = GeonamesClient::new(username)?;

    // Search places by name
    let results = client.search("Paris", 10).await?;
    for result in results {
        println!("{} ({}, pop: {})",
            result.metadata.get("name").unwrap(),
            result.metadata.get("country_name").unwrap(),
            result.metadata.get("population").unwrap()
        );
    }

    // Get nearby places
    let nearby = client.get_nearby(48.8566, 2.3522).await?;
    println!("Found {} nearby places", nearby.len());

    // Get timezone
    let tz = client.get_timezone(40.7128, -74.0060).await?;
    if let Some(result) = tz.first() {
        println!("Timezone: {}", result.metadata.get("timezone_id").unwrap());
    }

    // Get country information
    let info = client.get_country_info("US").await?;
    if let Some(result) = info.first() {
        println!("Capital: {}", result.metadata.get("capital").unwrap());
        println!("Population: {}", result.metadata.get("population").unwrap());
    }

    Ok(())
}

Metadata Fields:

  • geoname_id, name, toponym_name
  • latitude, longitude
  • country_code, country_name
  • admin_name1 (state/province)
  • feature_class, feature_code
  • population

Country Info Fields:

  • capital, population, area_sq_km, continent

4. OpenElevationClient (Elevation Data)

Rate Limit: ~5 requests/second Authentication: None required

use ruvector_data_framework::OpenElevationClient;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let client = OpenElevationClient::new()?;

    // Single point elevation
    let result = client.get_elevation(27.9881, 86.9250).await?; // Mt. Everest
    if let Some(point) = result.first() {
        println!("Elevation: {} meters", point.metadata.get("elevation_m").unwrap());
    }

    // Batch elevation lookup
    let locations = vec![
        (40.7128, -74.0060),  // NYC
        (48.8566, 2.3522),    // Paris
        (35.6762, 139.6503),  // Tokyo
    ];

    let results = client.get_elevations(locations).await?;
    for result in results {
        println!("Lat: {}, Lon: {}, Elevation: {} m",
            result.metadata.get("latitude").unwrap(),
            result.metadata.get("longitude").unwrap(),
            result.metadata.get("elevation_m").unwrap()
        );
    }

    Ok(())
}

Metadata Fields:

  • latitude, longitude
  • elevation_m (meters above sea level)

Geographic Utilities

All clients use GeoUtils for distance calculations:

use ruvector_data_framework::GeoUtils;

// Calculate distance between two points (Haversine formula)
let distance_km = GeoUtils::distance_km(
    40.7128, -74.0060,  // NYC
    51.5074, -0.1278    // London
);
println!("NYC to London: {:.2} km", distance_km); // ~5570 km

// Check if point is within radius
let within = GeoUtils::within_radius(
    48.8566, 2.3522,   // Paris center
    48.8584, 2.2945,   // Eiffel Tower
    10.0               // 10 km radius
);
println!("Eiffel Tower within 10km of Paris: {}", within); // true

Rate Limiting

All clients implement strict rate limiting to respect API policies:

Client Rate Limit Enforcement
NominatimClient 1 req/sec STRICT (Mutex-based timing)
OverpassClient ~2 req/sec Conservative delay
GeonamesClient ~0.5 req/sec Conservative (2000/hour limit)
OpenElevationClient ~5 req/sec Light delay

Nominatim Rate Limiting

Nominatim uses a strict rate limiter that ensures exactly 1 request per second:

// Internal rate limiter tracks last request time
// Automatically waits if needed before each request
client.geocode("Paris").await?;  // Executes immediately
client.geocode("London").await?; // Waits ~1 second if needed

IMPORTANT: Violating Nominatim's 1 req/sec policy can result in IP blocking. The client enforces this automatically.

SemanticVector Integration

All responses are converted to SemanticVector format:

pub struct SemanticVector {
    pub id: String,                    // "NOMINATIM:way:12345"
    pub embedding: Vec<f32>,           // 256-dim semantic embedding
    pub domain: Domain,                // Domain::CrossDomain
    pub timestamp: DateTime<Utc>,      // When data was fetched
    pub metadata: HashMap<String, String>, // Geographic metadata
}

This allows geospatial data to be:

  • Stored in RuVector's vector database
  • Searched semantically
  • Combined with other domains (climate, finance, etc.)
  • Analyzed for cross-domain patterns

Error Handling

All clients use the framework's Result type:

use ruvector_data_framework::{NominatimClient, FrameworkError, Result};

async fn example() -> Result<()> {
    let client = NominatimClient::new()?;

    match client.geocode("Invalid Address").await {
        Ok(results) => {
            println!("Found {} results", results.len());
        }
        Err(FrameworkError::Network(e)) => {
            eprintln!("Network error: {}", e);
        }
        Err(e) => {
            eprintln!("Other error: {}", e);
        }
    }

    Ok(())
}

Testing

Run the test suite:

# Run all geospatial tests
cargo test geospatial

# Run specific client tests
cargo test nominatim
cargo test overpass
cargo test geonames
cargo test elevation

# Run integration tests with mocked responses
cargo test --test geospatial_integration

Run the demo:

# Basic demo (skips GeoNames without username)
cargo run --example geospatial_demo

# Full demo with GeoNames
GEONAMES_USERNAME=your_username cargo run --example geospatial_demo

Best Practices

1. Respect Rate Limits

// ✅ Good: Use the client's built-in rate limiting
for address in addresses {
    let results = client.geocode(address).await?;
    // Rate limiting is automatic
}

// ❌ Bad: Don't try to bypass rate limiting
for address in addresses {
    tokio::spawn(async move {
        client.geocode(address).await // Violates rate limits!
    });
}

2. Cache Results

use std::collections::HashMap;

struct GeocodingCache {
    cache: HashMap<String, Vec<SemanticVector>>,
    client: NominatimClient,
}

impl GeocodingCache {
    async fn geocode(&mut self, address: &str) -> Result<Vec<SemanticVector>> {
        if let Some(cached) = self.cache.get(address) {
            return Ok(cached.clone());
        }

        let results = self.client.geocode(address).await?;
        self.cache.insert(address.to_string(), results.clone());
        Ok(results)
    }
}

3. Handle Errors Gracefully

async fn batch_geocode(client: &NominatimClient, addresses: Vec<&str>) -> Vec<Option<SemanticVector>> {
    let mut results = Vec::new();

    for address in addresses {
        match client.geocode(address).await {
            Ok(mut vecs) => results.push(vecs.pop()),
            Err(e) => {
                tracing::warn!("Geocoding failed for '{}': {}", address, e);
                results.push(None);
            }
        }
    }

    results
}

4. Use Appropriate Clients

// ✅ Use Nominatim for address lookup
client.geocode("1600 Pennsylvania Avenue NW").await?;

// ✅ Use Overpass for POI search
client.get_nearby_pois(lat, lon, radius, "restaurant").await?;

// ✅ Use GeoNames for place name search
client.search("Paris").await?;

// ✅ Use OpenElevation for terrain analysis
client.get_elevations(hiking_trail_points).await?;

Advanced Usage

Cross-Domain Discovery

Combine geospatial data with other domains:

use ruvector_data_framework::{
    NominatimClient, UsgsEarthquakeClient,
    NativeDiscoveryEngine, NativeEngineConfig,
};

async fn earthquake_location_analysis() -> Result<()> {
    let geo_client = NominatimClient::new()?;
    let usgs_client = UsgsEarthquakeClient::new()?;

    // Get recent earthquakes
    let earthquakes = usgs_client.get_recent(4.0, 7).await?;

    // Create discovery engine
    let config = NativeEngineConfig::default();
    let mut engine = NativeDiscoveryEngine::new(config);

    // Add earthquake data
    for eq in earthquakes {
        engine.add_vector(eq);
    }

    // Add nearby cities for each earthquake
    for eq in &earthquakes {
        let lat: f64 = eq.metadata.get("latitude").unwrap().parse()?;
        let lon: f64 = eq.metadata.get("longitude").unwrap().parse()?;

        let nearby = geo_client.reverse_geocode(lat, lon).await?;
        for place in nearby {
            engine.add_vector(place);
        }
    }

    // Detect cross-domain patterns
    let patterns = engine.detect_patterns();
    println!("Found {} patterns linking earthquakes to locations", patterns.len());

    Ok(())
}

Geofencing

use ruvector_data_framework::GeoUtils;

struct Geofence {
    center_lat: f64,
    center_lon: f64,
    radius_km: f64,
}

impl Geofence {
    fn contains(&self, lat: f64, lon: f64) -> bool {
        GeoUtils::within_radius(
            self.center_lat,
            self.center_lon,
            lat,
            lon,
            self.radius_km
        )
    }

    async fn find_pois(&self, client: &OverpassClient, amenity: &str) -> Result<Vec<SemanticVector>> {
        client.get_nearby_pois(
            self.center_lat,
            self.center_lon,
            self.radius_km * 1000.0, // Convert km to meters
            amenity
        ).await
    }
}

// Usage
let downtown = Geofence {
    center_lat: 40.7589,
    center_lon: -73.9851,
    radius_km: 2.0,
};

if downtown.contains(40.7614, -73.9776) {
    println!("Point is within downtown area");
}

let restaurants = downtown.find_pois(&overpass_client, "restaurant").await?;

API Reference

See the source code for complete API documentation.

Contributing

When contributing geospatial client improvements:

  1. Maintain strict rate limiting compliance
  2. Add comprehensive tests with mocked responses
  3. Update this documentation
  4. Follow the existing client patterns
  5. Test with real APIs (but don't commit credentials)

License

MIT License - See LICENSE for details

Resources