Bernt
58ca4e68db
- Go backend API with full CRUD for all modules (CRM, Sales, Finance, HR, Legal, Marketing, Support, Purchase, Inventory, Projects, Automation, Analytics) - Rust analytics service with parallel report generation - C runtime with POSIX shared memory IPC - PostgreSQL schema with 30+ tables, full migrations - Redis cache, sessions, pub/sub - Kafka event streaming with Zookeeper - WebSocket hub for real-time updates - Automation engine with cron jobs, workflows, event triggers - JWT authentication, multi-tenant from start - Docker Compose with all services - Nginx reverse proxy with rate limiting - Integration tests passing - Feature gap analysis against Fortnox/Odoo/Visma Refs: BOC-001
106 lines
8.1 KiB
HTML
106 lines
8.1 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
<title>Field Data vs Satellite Imagery: When to Use What | Landvex</title>
|
|
<meta name="description" content="Satellites see wide. Field observers see detail. Learn when each approach wins and how to combine them for better infrastructure intelligence.">
|
|
<link rel="canonical" href="https://landvex.com/insights/field-data-vs-satellite-imagery/">
|
|
<meta property="og:title" content="Field Data vs Satellite Imagery: When to Use What | Landvex">
|
|
<meta property="og:description" content="Satellites see wide. Field observers see detail. Learn when each approach wins and how to combine them for better infrastructure intelligence.">
|
|
<meta property="og:type" content="article">
|
|
<meta property="og:url" content="https://landvex.com/insights/field-data-vs-satellite-imagery/">
|
|
<script type="application/ld+json">
|
|
{
|
|
"@context": "https://schema.org",
|
|
"@type": "Article",
|
|
"headline": "Field Data vs Satellite Imagery: When to Use What",
|
|
"description": "Satellites see wide. Field observers see detail. Learn when each approach wins and how to combine them for better infrastructure intelligence.",
|
|
"author": {"@type": "Organization", "name": "Landvex"},
|
|
"publisher": {"@type": "Organization", "name": "Landvex", "logo": {"@type": "ImageObject", "url": "https://landvex.com/apple-touch-icon.png"}},
|
|
"datePublished": "2026-07-21",
|
|
"dateModified": "2026-07-21",
|
|
"mainEntityOfPage": {"@type": "WebPage", "@id": "https://landvex.com/insights/field-data-vs-satellite-imagery/"}
|
|
}
|
|
</script>
|
|
<style>
|
|
body { font-family: -apple-system, BlinkMacSystemFont, 'Inter', sans-serif; line-height: 1.6; max-width: 760px; margin: 0 auto; padding: 40px 20px; color: #1a1a1a; }
|
|
h1 { font-size: 2.5rem; font-weight: 700; margin-bottom: 0.5em; line-height: 1.2; }
|
|
h2 { font-size: 1.5rem; font-weight: 600; margin-top: 2em; margin-bottom: 0.5em; }
|
|
p { margin-bottom: 1.2em; }
|
|
.meta { color: #666; font-size: 0.9rem; margin-bottom: 2em; }
|
|
.cta { background: #f5f5f5; padding: 24px; border-radius: 8px; margin: 2em 0; }
|
|
.cta a { color: #0066cc; text-decoration: none; font-weight: 600; }
|
|
footer { margin-top: 4em; padding-top: 2em; border-top: 1px solid #eee; font-size: 0.85rem; color: #666; }
|
|
.sources { margin-top: 3em; padding-top: 2em; border-top: 1px solid #eee; font-size: 0.85rem; color: #666; }
|
|
.sources h3 { font-size: 1rem; margin-bottom: 1em; }
|
|
.sources ul { list-style: none; padding: 0; }
|
|
.sources li { margin-bottom: 0.5em; }
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<article>
|
|
<h1>Field Data vs Satellite Imagery: When to Use What</h1>
|
|
<p class="meta">Published July 21, 2026 · Technology</p>
|
|
|
|
<p>Infrastructure monitoring has two powerful tools: satellites that can image the entire planet, and field observers who can inspect individual assets in detail. Neither is universally superior. Each has strengths, limitations, and optimal use cases. The challenge is knowing when to use which — and how to combine them.</p>
|
|
|
|
<h2>What satellites do well</h2>
|
|
<p>Satellite imagery excels at coverage and consistency. A single satellite pass can image thousands of square kilometers at uniform resolution and lighting conditions. This enables wide-area assessment, change detection over time, and comparison across regions that would be impractical with ground-based methods.</p>
|
|
|
|
<p>Modern commercial satellites achieve 30-50 cm ground sample distance — sufficient to detect large-scale changes like road construction, vegetation clearance, building demolition, and flood extent. Synthetic aperture radar (SAR) satellites can image through clouds and darkness, enabling all-weather monitoring.</p>
|
|
|
|
<p>Satellites are also consistent. The same sensor, calibrated the same way, captures every image. This eliminates observer variation and enables precise change detection: subtract last month's image from this month's, and the difference highlights what changed.</p>
|
|
|
|
<h2>What satellites cannot do</h2>
|
|
<p>Resolution limits are the most obvious constraint. A 50 cm pixel cannot resolve cracks in pavement, corrosion on bridge bearings, or graffiti on walls. These conditions require centimeter-scale resolution that satellites cannot provide.</p>
|
|
|
|
<p>Angle and occlusion are equally limiting. Satellites look down. They cannot see under bridges, inside tunnels, or behind buildings. Vertical surfaces — retaining walls, bridge piers, building facades — are poorly resolved or invisible.</p>
|
|
|
|
<p>Timeliness is a third constraint. Commercial satellites revisit the same location every few days at best, often every few weeks. A condition that develops and worsens between passes is invisible to satellite monitoring. And ordering targeted imagery adds cost and delay.</p>
|
|
|
|
<h2>What field data does well</h2>
|
|
<p>Field observation provides the detail and access that satellites cannot. A trained contributor at ground level can assess crack width, measure pothole depth, photograph bridge bearings, and document drainage blockages. They can access spaces satellites cannot see and inspect assets from angles satellites cannot achieve.</p>
|
|
|
|
<p>Field observation is also timely. Contributors can be directed to specific assets on demand, providing observation within hours rather than weeks. This enables rapid response to reported issues, verification of satellite-detected changes, and priority assessment of critical assets.</p>
|
|
|
|
<p>Perhaps most importantly, field observation captures context. A photo of a cracked road surface includes the surrounding drainage, vegetation, traffic pattern, and adjacent land use. This context is essential for understanding why a condition exists and what intervention is appropriate.</p>
|
|
|
|
<h2>What field data cannot do</h2>
|
|
<p>Coverage is the primary limitation. Field observation requires physical presence. A single contributor can assess tens of assets per day, not thousands. Comprehensive coverage of a large network requires many contributors, extensive coordination, and significant cost.</p>
|
|
|
|
<p>Consistency is a second challenge. Different observers assess the same condition differently. Training, calibration, and quality control are essential but never perfect. The result is more variable than satellite data, where the same sensor captures every image.</p>
|
|
|
|
<p>Finally, field observation is subject to access constraints. Private property, dangerous conditions, and regulatory restrictions limit where observers can go. Some assets simply cannot be assessed from the ground.</p>
|
|
|
|
<h2>The integrated approach</h2>
|
|
<p>The optimal strategy uses both sources, with each compensating for the other's limitations. Satellites provide wide-area screening, identifying zones of change or concern. Field observation follows up, providing detailed assessment of priority areas.</p>
|
|
|
|
<p>This is the approach Landvex employs. Satellite imagery identifies where conditions have changed. Field observers verify what changed and assess severity. The result is comprehensive coverage with targeted detail — the strengths of both methods, without the weaknesses of either.</p>
|
|
|
|
<div class="cta">
|
|
<strong>See how integrated monitoring works for your assets.</strong><br>
|
|
<a href="/enterprise/">Request a pilot →</a>
|
|
</div>
|
|
|
|
</article>
|
|
|
|
<footer>
|
|
<p><strong>Related:</strong> <a href="/insights/field-intelligence-vs-satellite/">Field Intelligence vs Satellite Imagery</a> · <a href="/insights/the-future-of-infrastructure-monitoring/">The Future of Infrastructure Monitoring</a> · <a href="/insights/continuous-monitoring-vs-periodic-inspection/">Continuous Monitoring vs Periodic Inspection</a></p>
|
|
</footer>
|
|
|
|
<div class="sources">
|
|
<h3>Sources and References</h3>
|
|
<ul>
|
|
<li>Landvex Platform Documentation — <a href="/docs">landvex.com/docs</a></li>
|
|
<li>quiXzoom Field Operations Manual — Internal operations documentation</li>
|
|
<li>Landvex Intelligence Reports — Analysis from 100+ cities worldwide</li>
|
|
<li>European Space Agency: "Satellite Applications for Infrastructure" (2024)</li>
|
|
<li>Nature: "Remote sensing in urban infrastructure" (2023)</li>
|
|
</ul>
|
|
<p><em>Disclaimer: This article reflects Landvex's analysis and methodology. For specific monitoring strategies, <a href="/contact/">contact our team</a>.</em></p>
|
|
</div>
|
|
|
|
</body>
|
|
</html>
|