Files
boc/landvex-site/insights/how-landvex-validates-observations/index.html
T
Bernt 1a12fb870b dev-api: add developer portal, OpenAPI spec, and Flatenbadet case study
- New /developers/ page with API docs, SDKs, pricing, use cases
- OpenAPI 3.0 spec for Orders, Missions, Photos, Analytics
- Case study: Glasskiosken i Flatenbadet — complete ROI analysis
- Updated /order/ with recurring missions and frequency dropdown
2026-07-14 15:27:33 +00:00

208 lines
16 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>How Landvex Validates Observations | Landvex</title>
<meta name="description" content="Every observation that enters the Landvex platform passes through multiple validation layers. Learn how we ensure data quality at scale.">
<link rel="canonical" href="https://landvex.com/insights/how-landvex-validates-observations/">
<meta property="og:title" content="How Landvex Validates Observations | Landvex">
<meta property="og:description" content="Every observation that enters the Landvex platform passes through multiple validation layers. Learn how we ensure data quality at scale.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://landvex.com/insights/how-landvex-validates-observations/">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How Landvex Validates Observations",
"description": "Every observation that enters the Landvex platform passes through multiple validation layers. Learn how we ensure data quality at scale.",
"author": {"@type": "Organization", "name": "Landvex"},
"publisher": {"@type": "Organization", "name": "Landvex", "logo": {"@type": "ImageObject", "url": "https://landvex.com/apple-touch-icon.png"}},
"datePublished": "2026-07-24",
"dateModified": "2026-07-24",
"mainEntityOfPage": {"@type": "WebPage", "@id": "https://landvex.com/insights/how-landvex-validates-observations/"}
}
</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>How Landvex Validates Observations</h1>
<p class="meta">Published July 24, 2026 · Technology</p>
<p>Data quality is the foundation of everything Landvex does. A platform that delivers decision intelligence cannot compromise on the reliability of its inputs. Every observation that enters our system passes through multiple validation layers, each designed to catch a different category of error. The result is not perfect data — no system achieves that — but data whose quality is known, measured, and transparent.</p>
<h2>Layer 1: Collection validation</h2>
<p>Quality control begins at the moment of collection. The quiXzoom mobile app enforces structured data capture: contributors must photograph specific angles, confirm GPS location, and answer standardized questions. The app validates inputs in real time.</p>
<p>Photos are checked for focus, lighting, and framing. GPS coordinates are validated against the claimed asset location — an observation geotagged 500 meters from the nearest road is flagged. Timestamps are checked for plausibility. Observations that fail any check are rejected immediately, with guidance to the contributor on how to correct the issue.</p>
<p>This layer catches the most common data quality problems: blurry photos, incorrect locations, and incomplete submissions. It does not require AI or complex analysis. It requires clear protocols and disciplined enforcement.</p>
<h2>Layer 2: AI assessment</h2>
<p>Observations that pass collection validation proceed to AI assessment. Computer vision models analyze photos for the conditions of interest: cracks, potholes, corrosion, vegetation, lighting function, and more. Each model outputs a confidence score indicating how certain it is about what it sees.</p>
<p>The models are trained on verified datasets and calibrated per category. A crack detection model performs differently on asphalt than on concrete. A lighting model performs differently in daylight than at dusk. The system knows these limitations and adjusts confidence accordingly.</p>
<p>High-confidence AI assessments proceed to consensus scoring. Low-confidence assessments are flagged for additional review or additional observation. The AI does not reject observations — it grades them, and the grading determines what happens next.</p>
<h2>Layer 3: Consensus scoring</h2>
<p>When multiple observations of the same asset exist, the Consensus Engine combines them into a single scored finding. This is not majority voting. It is weighted aggregation that considers contributor reliability, observation quality, historical consistency, and official record alignment.</p>
<p>A contributor with a track record of accurate observations carries more weight than a newcomer. An observation with high AI confidence carries more weight than one with low confidence. An observation that aligns with the asset's known history carries more weight than one that contradicts it.</p>
<p>The output is a confidence-scored finding: "Asset condition: degraded, confidence 87%, based on 4 observations, 2 validators, 1 contradiction with register." This is not a binary judgment. It is a statement of evidence strength that decision-makers can interpret according to their risk tolerance.</p>
<h2>Layer 4: Provenance and audit</h2>
<p>Every finding retains a complete provenance chain: which observations contributed, what each validation layer scored, how consensus was reached, and what the final confidence calculation yielded. This chain is immutable and inspectable.</p>
<p>If a customer questions a finding, the full chain can be examined. If an observation is later found to be erroneous, its impact on downstream findings can be recalculated. If validation models are improved, historical observations can be re-scored.</p>
<p>Transparency is not a feature we added. It is a design principle that shapes every layer of the system.</p>
<h2>Measuring quality</h2>
<p>We measure validation performance continuously. Precision (how often flagged issues are real), recall (how many real issues are caught), and confidence calibration (whether stated confidence matches actual accuracy) are tracked per model and per category.</p>
<p>When performance drifts — when a model starts producing more false positives, or when confidence scores become poorly calibrated — the system alerts and the model is retrained or replaced. Quality is not assumed. It is monitored.</p>
<div class="cta">
<strong>See how validated observations improve your decision confidence.</strong><br>
<a href="/enterprise/">Request a pilot →</a>
</div>
</article>
<footer>
<div class="footer-container" style="max-width:1200px;margin:0 auto;padding:48px 24px 32px;">
<!-- Main Footer Grid -->
<div style="display:grid;grid-template-columns:repeat(4,1fr);gap:40px;margin-bottom:48px;">
<!-- Column 1: Products -->
<div>
<h4 style="font-size:13px;font-weight:600;color:#0A0A0A;margin-bottom:16px;text-transform:uppercase;letter-spacing:0.5px;">Produkter</h4>
<ul style="list-style:none;padding:0;margin:0;display:flex;flex-direction:column;gap:12px;">
<li><a href="/infrastructure-monitoring/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">VIMS</a></li>
<li><a href="/intelligence/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Intelligence</a></li>
<li><a href="/reality-alerts/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Reality Alerts</a></li>
<li><a href="/enterprise/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Enterprise</a></li>
<li><a href="/pilot/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Pilotprogram</a></li>
</ul>
</div>
<!-- Column 2: Solutions -->
<div>
<h4 style="font-size:13px;font-weight:600;color:#0A0A0A;margin-bottom:16px;text-transform:uppercase;letter-spacing:0.5px;">Lösningar</h4>
<ul style="list-style:none;padding:0;margin:0;display:flex;flex-direction:column;gap:12px;">
<li><a href="/verticals/bridge-inspection/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Broinspektion</a></li>
<li><a href="/verticals/road-monitoring/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Vägövervakning</a></li>
<li><a href="/verticals/infrastructure/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Infrastruktur</a></li>
<li><a href="/verticals/utilities/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Utilities</a></li>
<li><a href="/use-cases/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Användningsfall</a></li>
</ul>
</div>
<!-- Column 3: Resources -->
<div>
<h4 style="font-size:13px;font-weight:600;color:#0A0A0A;margin-bottom:16px;text-transform:uppercase;letter-spacing:0.5px;">Resurser</h4>
<ul style="list-style:none;padding:0;margin:0;display:flex;flex-direction:column;gap:12px;">
<li><a href="/blog/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Intelligence Insights</a></li>
<li><a href="/guides/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Guider</a></li>
<li><a href="/developers/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Developer API</a></li>
<li><a href="/status/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Systemstatus</a></li>
<li><a href="/reports/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Rapporter</a></li>
</ul>
</div>
<!-- Column 4: Company -->
<div>
<h4 style="font-size:13px;font-weight:600;color:#0A0A0A;margin-bottom:16px;text-transform:uppercase;letter-spacing:0.5px;">Företag</h4>
<ul style="list-style:none;padding:0;margin:0;display:flex;flex-direction:column;gap:12px;">
<li><a href="/about/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Om oss</a></li>
<li><a href="/careers/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Karriär</a></li>
<li><a href="/press/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Press</a></li>
<li><a href="/contact/" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">Kontakt</a></li>
<li><a href="https://www.quixzoom.com" target="_blank" rel="noopener" style="font-size:13px;color:#6E6E73;text-decoration:none;transition:color 0.2s;">quiXzoom →</a></li>
</ul>
</div>
</div>
<!-- Divider -->
<div style="border-top:1px solid #E5E5E5;padding-top:32px;">
<!-- Legal & Compliance Row -->
<div style="display:flex;justify-content:space-between;align-items:flex-start;flex-wrap:wrap;gap:24px;margin-bottom:24px;">
<div style="display:flex;flex-wrap:wrap;gap:16px 24px;">
<a href="/privacy/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Privacy</a>
<a href="/terms/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Terms</a>
<a href="/cookie-policy/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Cookies</a>
<a href="/compliance/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Compliance</a>
<a href="/trust/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Trust Centre</a>
<a href="/dpa/" style="font-size:12px;color:#6E6E73;text-decoration:none;">DPA</a>
<a href="/sla/" style="font-size:12px;color:#6E6E73;text-decoration:none;">SLA</a>
<a href="/security/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Security</a>
<a href="/accessibility/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Accessibility</a>
<a href="/responsible-disclosure/" style="font-size:12px;color:#6E6E73;text-decoration:none;">Responsible Disclosure</a>
</div>
<div style="display:flex;gap:16px;">
<a href="https://www.linkedin.com/company/landvex" target="_blank" rel="noopener" style="color:#6E6E73;" title="LinkedIn">
<svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M16 8a6 6 0 0 1 6 6v7h-4v-7a2 2 0 0 0-2-2 2 2 0 0 0-2 2v7h-4v-7a6 6 0 0 1 6-6z"/><rect x="2" y="9" width="4" height="12"/><circle cx="4" cy="4" r="2"/></svg>
</a>
<a href="https://x.com/landvex" target="_blank" rel="noopener" style="color:#6E6E73;" title="X">
<svg width="18" height="18" viewBox="0 0 24 24" fill="currentColor"><path d="M18.244 2.25h3.308l-7.227 8.26 8.502 11.24H16.17l-4.714-6.231-5.401 6.231H2.746l7.73-8.835L1.254 2.25H8.08l4.253 5.622 5.912-5.622Zm-1.161 17.52h1.833L7.084 4.126H5.117z"/></svg>
</a>
</div>
</div>
<!-- Company Info Row -->
<div style="display:flex;justify-content:space-between;align-items:flex-end;flex-wrap:wrap;gap:16px;">
<div>
<div style="font-size:12px;color:#86868B;line-height:1.6;">
<strong style="color:#0A0A0A;">Landvex Inc.</strong> · Houston, Texas · USA<br>
<strong style="color:#0A0A0A;">Landvex AB</strong> · Org.nr 559141-7042 · Stockholm, Sweden · EU<br>
<a href="mailto:contact@landvex.com" style="color:#86868B;text-decoration:none;">contact@landvex.com</a> ·
<a href="mailto:security@landvex.com" style="color:#86868B;text-decoration:none;">security@landvex.com</a>
</div>
<div style="font-size:11px;color:#86868B;margin-top:8px;line-height:1.5;">
Field data powered by <a href="https://www.quixzoom.com" style="color:#86868B;text-decoration:underline;">quiXzoom</a> ·
<a href="/data-lineage/" style="color:#86868B;text-decoration:underline;">Data Lineage</a> ·
<a href="/subprocessors/" style="color:#86868B;text-decoration:underline;">Sub-processors</a> ·
<a href="/methodology/" style="color:#86868B;text-decoration:underline;">Methodology</a>
</div>
</div>
<div style="font-size:12px;color:#86868B;">
© 2026 Landvex Inc / Landvex AB. All rights reserved.
</div>
</div>
</div>
</div>
</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>IEEE: "Quality assurance in AI-based inspection systems" (2024)</li>
<li>ACM: "Provenance in data-intensive systems" (2023)</li>
</ul>
<p><em>Disclaimer: This article reflects Landvex's analysis and methodology. For specific validation requirements, <a href="/contact/">contact our team</a>.</em></p>
</div>
</body>
</html>