GPS Coordinates: Data Point Intelligence Guide

Six decimal places is a doorstep. Two is a district. Precision in a coordinate is a decision about harm, not a formatting preference.

Understanding the GPS Coordinates as an intelligence artifact

A GPS coordinate is a latitude and longitude pair expressed against a specific datum and reference frame, most commonly WGS 84. Latitude runs from minus ninety to ninety and longitude from minus one hundred eighty to one hundred eighty. Common formats include signed decimal degrees, degrees-minutes-seconds, military grid references, UTM eastings and northings, and geohash strings. Each additional decimal place in decimal degrees changes ground resolution by roughly an order of magnitude, from about a hundred kilometres to about ten centimetres.

Altitude and a timestamp turn a bare point into an observation. Coordinates carried in image metadata, telemetry and broadcast position feeds usually include accuracy or dilution-of-precision fields, which are routinely stripped in transit. Datum matters enormously: identical numbers expressed in a local datum can sit hundreds of metres from their WGS 84 position, and some national systems apply deliberate systematic offsets to published coordinates.

Why it matters

Coordinates are the atomic unit that lets unrelated datasets be joined geometrically. Imagery, movement tracks, incident reports, infrastructure and boundaries all reduce to geometry, enabling distance, bearing, containment and intersection tests that names cannot support. They allow imagery tasking against a specific footprint and change detection over time. They also permit falsification, since a coordinate can be tested against terrain, sun angle, shadow length and mapped infrastructure.

What analysts actually look for

These are the concrete, observable signals that carry weight in this area of work:

Trailing precision indicates the source: rounded values suggest manual entry, six decimals suggest device-derived capture.
Elevation compared against a digital elevation model tests whether a claimed position is physically plausible at all.
Sun azimuth and shadow length for the coordinate and timestamp verify or refute the claimed time of capture.
Distance and bearing between successive points yield implied speed, exposing physically impossible movement in a track.
Containment tests place the point inside administrative, restricted or exclusion zones with direct legal consequence.
Identical coordinates repeated across many records indicate a shared source or a default value, not real observation.
Nearby mapped infrastructure either explains or contradicts the activity reported at that specific point.
Repeated zero-zero values mark parsing failures rather than a genuine location in the Gulf of Guinea.

Where the data comes from

Authoritative and openly available collection points. Always confirm licensing and terms before operational or commercial use:

EPSG Registry (epsg.io) — Coordinate reference system definitions and transformation parameters between datums and projections.
PROJ and QGIS — Open tooling to convert between decimal degrees, DMS, UTM, MGRS and national grid systems.
Copernicus DEM and SRTM — Elevation values used to sanity check altitude and model terrain visibility from a point.
SunCalc — Sun azimuth and elevation for a coordinate and time, supporting shadow and timing verification.
OpenStreetMap and Overpass — What is actually mapped at and immediately around the point in question.
NOAA NGS transformation tools — Datum transformation between historic and modern reference frames for legacy coordinates.
Sentinel Hub and Copernicus Browser — Imagery covering the exact footprint on or near the observation date.
NGA MGRS and geohash converters — Standard grid references used in military, maritime and emergency reporting.

A working method

A repeatable sequence beats ad-hoc searching. This is a practical starting workflow:

Normalise format and datum — Convert everything to signed decimal degrees on WGS 84, recording the original format and any assumed datum.
Bound the precision — Truncate to the precision the source genuinely supports and attach an explicit accuracy figure to the record.
Check plausibility — Test against elevation, land cover and mapped features, flagging points in open water, wrong hemispheres or at zero-zero.
Verify the timestamp — Compare sun position and shadow geometry against any imagery or photograph tied to the coordinate and claimed time.
Join geometrically — Run containment and proximity queries against boundaries, facilities, incidents and infrastructure layers you already hold.
Retrieve imagery — Pull overhead imagery for the footprint on the nearest available dates to confirm what is physically present.
Downgrade before sharing — Publish at the coarsest resolution that still supports the finding, keeping the precise value in restricted holdings.

How this connects across the intelligence taxonomy

Intelligence work does not respect neat boundaries. The mission domain you are working, the disciplines you practise, and the data points you pivot on are one connected system. These are the direct relationships for this entry — every link is also a tag, so you can follow any thread across the whole library.

Collected by these disciplines

Geospatial Intelligence — Intelligence Derived from Place
Imagery Intelligence — Interpretation of Visual Imagery
Technical Intelligence — Technology Capability, Design, and Exploitation
Risk Intelligence — Structured Assessment of Threat and Consequence
Measurement & Signature Intel — Signatures, Measurements, and Physical Phenomena
Environmental Intelligence — Environmental Conditions, Damage, and Crime
Radio Frequency Intelligence — The Electromagnetic Spectrum as an Intelligence Source
Sanctions Intelligence — Screening, Designations, and Evasion Detection
Maritime Intelligence — Vessels, Shipping, and the Maritime Domain
Economic Intelligence — Economic Conditions, Trade, and Market Signals

Investigated in these domains

Pivots to these data points

Location / Coordinates — A geographic point, place, or region — the basis of GEOINT analysis.
Facility / Site — A physical installation — plant, base, port, data centre — with a fixed footprint and function.
Satellite Imagery — Overhead imagery of an area of interest, used for change detection and site analysis.

Inside the platform: where GPS Coordinates lives

The Quantus platform is 204 pages behind a 147-item sidebar organised into six working groups: Command (24 items), Dashboards (15), Threat Theaters (14), Intelligence Domains (15), Investigate (34), and Administration (45). This entry is not a page in isolation — it is a thread running through several of them.

The modules that matter most here:

datapoint.php?dp=dp_coordinates — Data point hub
domain.php?d=critinfra — Critical Infrastructure dashboard
domain.php?d=mining — Mining & Resource Crime dashboard
domain.php?d=wmd — WMD / Proliferation dashboard
domain.php?d=mil — Military & Defense dashboard
search.php — Advanced search, filter and pivot
correlate.php — Correlation graph
cases.php — Case management

Each dashboard is local-first: it renders from the platform’s own database rather than depending on a live third-party call, so it still works when an upstream API is unreachable or rate-limited. Heavy aggregates are cached with a hard query time cap and degrade to the last good value instead of hanging the page.

Automation, playbooks and AI skills

Analysis that only happens when someone remembers to run it is not a capability. The platform ships a 30-step automation pipeline (cron.php) that collects, ingests, resolves, enriches, correlates and scores on a schedule — 25 seeders, 11 resolvers and 7 enrichment runners, all idempotent and cursor-based so a run can be interrupted and resumed without duplicating or losing work.

AI skills that apply

The 16 one-click operations in ai-skills.php are deterministic jobs, not free-text generation. The ones that matter here:

Enrichment Runner
Enrichment → Local
Correlate Infrastructure
Summarise (Copilot)
Generate Report

Alerting closes the loop: rules in alerts.php fire on new indicators matching a saved query, so a first sighting in this area raises a notification rather than waiting to be noticed at the next review.

Feeds, data sources and the API

The collection layer runs a feed registry of free, machine-readable sources — bulk blocklists and trackers (Maltrail, IPsum, FireHOL, the full abuse.ch corpora, phishing databases, Emerging Threats, Spamhaus, DigitalSide, ThreatView), authoritative government feeds (CISA KEV, OFAC, UN and EU sanctions lists), and reference datasets (RIR allocations, ip-to-ASN and geolocation tables, MITRE ATT&CK, EPSS). collect.php pulls them server-side on a schedule; feeds.php and source-catalog.php show what is registered, what it covers and when it last ran.

Anything the platform holds is reachable programmatically. The REST API in api.php exposes 11 endpoints — status, stats, search, lookup, recent, export, bulk_check, top_threats, by_category, categories, check — and export.php streams 18 formats in bounded chunks, so a million-row export neither exhausts memory nor times out:

STIX 2.1, MISP, OpenIOC 1.1, CEF (ArcSight), LEEF 2.0 (QRadar), Zeek/Bro intel, Snort/Suricata rules, Palo Alto EDL, BIND RPZ, hosts blackhole, iptables, CSV, JSON, NDJSON/JSONL, XML.

That covers the CTI standards (STIX 2.1, MISP, OpenIOC), SIEM ingestion (CEF, LEEF, Zeek), detection engines (Snort/Suricata), and direct enforcement (Palo Alto EDL, BIND RPZ, hosts, iptables) — so intelligence developed here can be actioned in the tools you already run, without a manual reformatting step. A TAXII 2.1 server and a MISP/RSS feed are also served for pull-based sharing.

Use cases

Three ways this entry earns its keep in day-to-day work:

Triage under time pressure. An artifact or report lands and you need a defensible read in minutes, not days. Normalise format and datum is the first move; the platform pre-computes the enrichment so the analyst spends the time on judgement rather than lookups.
Building the picture. A single indicator is rarely the story. Check plausibility turns one artifact into a network — shared infrastructure, repeated selectors, the same operator behind different names — via the correlation graph and the cross-entity link engine.
Producing something actionable. Analysis that ends in a document nobody can use is wasted. Downgrade before sharing feeds the case file, the detection rule, the block list or the referral — with sourcing attached so the recipient can verify it.

Case management (cases.php), watchlists, saved searches and scheduled reports mean the work persists between sessions and survives an analyst leaving the team.

How each sector uses GPS Coordinates

The same entry is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The underlying artifacts are shared — the constraints, outputs and thresholds are not.

🎖 Military and defence

Coordinates are the currency of military reporting and the point at which analytic error becomes physical harm. A defence analyst uses them for terrain association, route planning, imagery tasking and situational awareness, expressed in a grid the receiving unit actually uses. The non-negotiable discipline is stated accuracy: every point carries a source, a datum, an error estimate and a time, because a position good enough for area awareness is not good enough for anything kinetic. Under the law of armed conflict, target verification requires positive identification by more than a coordinate, and the obligation to take feasible precautions means a point with unquantified error should stop the process rather than feed it.

🕵 National intelligence

For national intelligence coordinates are the join key across disciplines: they let imagery, signals-derived positions, human reporting and open source video be compared geometrically when nothing else is shared. Requirements are often expressed as areas of interest, and normalising every incoming position to one datum and grid is what makes fusion possible. Classification tends to track precision and source: an area is releasable where a device-derived point is not, and the fact that a coordinate came from a particular collection may be more sensitive than the coordinate itself. Products should therefore be written so a coarsened version can be released without rewriting the analysis.

👮 Law enforcement

Investigators encounter coordinates in device extractions, vehicle telematics, application data, image metadata and warrant applications. Each carries a different reliability and a different legal route: device-derived locations generally require a warrant, historical location data from a provider requires judicial authorisation in most jurisdictions, and consent-based extraction must be genuinely informed. Evidentially, the analyst must be able to explain the datum, the accuracy field, whether the position was satellite-derived or network-derived, and what the device was actually reporting. A last known position presented as a live location has ended prosecutions. Preserve the extraction with hashes and keep the derived mapping as separate, explainable analysis.

🔍 Private investigation and corporate security

Private investigators use coordinates for site verification, asset location, accident reconstruction and evidence of presence at commercial premises. Lawful sources are open imagery, mapping, publicly posted content and material the client already owns. What a private actor may not do is place a tracking device on a vehicle they do not own, obtain location data from a mobile provider by any route, purchase location data derived from advertising exchanges to track a named person, or aggregate a person's positions into a pattern of life. Several of these are criminal offences and all attract civil liability. Where a residence is involved, escalate to counsel rather than to finer precision.

📰 Journalism and OSINT media

Coordinates underpin verification of user-generated video and photographs, and geolocation to a building is now standard practice in investigative reporting. The published resolution is a separate decision from the resolution you established. Naming a street or a block is usually sufficient; publishing the precise coordinates of a home, a shelter, a hospital in a contested area or a source's location can get people killed, and has. Verify with at least two independent features matched against imagery, show your working so readers can check it, and take a documented editorial decision on precision that weighs public interest against the specific risk to identifiable people.

🌍 NGO, humanitarian and human rights

Coordinates support needs assessment, incident mapping and accountability documentation, and they are among the most dangerous fields a human-rights organisation holds. A precise point can identify a survivor's home, a clandestine medical facility or a witness's village. Practice should be to collect the coarsest useful precision, to hold precise references encrypted and separately from names, and to publish only aggregated geometry. For accountability, evidence intended for a future prosecution may need full precision, so store it under a separate regime with legal custody in mind. Staff-carried devices generate coordinates too, and a leaked field tracker exposes both the team and the people they visited.

🎓 University and research

Researchers must document coordinate reference systems, transformation parameters and precision explicitly, because silent datum assumptions are a leading source of irreproducible spatial results. Where coordinates relate to people, ethics review will normally require spatial masking through aggregation, jittering with a documented displacement distribution, or release of derived measures only. Publishing precise household coordinates has caused documented harm in health and conflict research and is now widely prohibited by data-sharing policies. Deposit code and masked data with a persistent identifier, state the masking method precisely enough for others to model its effect on inference, and retain the unmasked data under institutional controls rather than on personal devices.

Playbook: working GPS Coordinates end to end

A repeatable sequence, from the moment the requirement lands to the moment a product is delivered and the case is closed out. Each phase states what you are trying to establish, not merely what to click — the point is a defensible chain of reasoning, not a checklist.

Phase 1 — Record the coordinate as received

Capture the original string, its format, any stated datum, any accuracy or dilution field, the timestamp and its time zone, and the source artifact. Do not convert on ingest. The original form frequently carries evidence about how the position was produced, which is lost by normalisation. A good output is a raw field preserved alongside empty normalised fields. Stop when the untouched original is stored where later processing cannot overwrite it.

Phase 2 — Normalise format and datum

Convert to signed decimal degrees on a stated reference frame, recording the assumed datum where none was given and the transformation applied. Datum mismatch shifts positions by hundreds of metres, which is enough to identify the wrong building. Where a national system with deliberate offsets is involved, handle it explicitly. A good output records original format, source datum, target datum and transformation. Stop when no coordinate in the dataset has an unstated reference frame.

Phase 3 — Bound the precision honestly

Truncate to the precision the source genuinely supports and attach an explicit accuracy figure. A position rounded to three decimals by a reporter is not a hundred-metre fix, and a device fix with a fifty metre accuracy field is not a doorstep. Carrying six decimals through a pipeline manufactures confidence nobody measured. A good output pairs every point with a radius. Stop when precision and stated accuracy are consistent for every record.

Phase 4 — Run mechanical sanity checks

Test for transposed latitude and longitude, sign errors, values outside valid ranges, points at exactly zero degrees by zero degrees, positions in open water, and repeated identical values indicating a default. These errors are extremely common and each has a distinctive signature. A good output is a flagged exception list rather than a silently cleaned dataset. Stop when every anomaly is either explained or excluded with a reason.

Phase 5 — Test against the physical world

Compare against a digital elevation model, land cover and mapped features. A claimed position on a mountainside, in the sea or inside a lake is a data problem or a deception, and both matter. Elevation inconsistent with reported altitude is a strong signal. A good output is a plausibility note per point or per cluster. Stop when the physical checks are documented, including the ones that passed.

Phase 6 — Verify the time

Where a photograph or video is attached, compute sun azimuth and elevation for the coordinate and claimed time and compare against observed shadows. Check weather records where available. This is the most powerful cheap falsification test available for a claimed position and time. A good output states the expected and observed sun geometry with a conclusion. Stop when the timestamp is corroborated, refuted, or shown to be untestable.

Phase 7 — Assess the harm before enrichment

Before running proximity queries around a point associated with a person, decide and record whether resolving to a residence is necessary and lawful. If it is not, generalise first and analyse the generalised form. This step exists because the enrichment itself creates the sensitive dataset. A good output is a recorded decision naming purpose and basis. Stop when the decision is written down, not assumed.

Phase 8 — Join geometrically

Run containment and proximity tests against boundaries, facilities, incidents and infrastructure layers, using the uncertainty radius rather than the bare point. Containment inside an administrative, restricted or exclusion zone often has direct legal consequence and should be reported with the boundary source named. A good output lists relationships with distances expressed as ranges. Stop when the joins answer the original question rather than merely producing more layers.

Phase 9 — Retrieve corroborating imagery

Pull overhead imagery for the footprint on the nearest available dates and compare against what the report claims is present. Note the acquisition dates and the gap to the event. This converts a coordinate from an assertion into an observation. A good output pairs the point with scene identifiers and a statement of what is and is not visible. Stop when imagery either supports, contradicts or is shown to be insufficient.

Phase 10 — Compute implied movement where relevant

For a track, derive distance, bearing and implied speed between successive points and flag physically impossible transitions, which indicate spoofing, mixed sources or clock errors. Note that gaps are not evidence of concealment without knowing the collection mechanism. A good output is a cleaned track with anomalies annotated rather than deleted. Stop when the remaining track is internally consistent. Record the speed threshold you applied so another analyst can rerun the same test on new data.

Phase 11 — Downgrade deliberately for sharing

Choose the published precision explicitly, generalise to an area or a named street or block, and hold the precise value in a restricted store with access logging and a short retention period. Assume any published coordinate will be reused by someone whose intentions differ from yours. A good output records the published precision and the reason. Stop when the internal and external versions differ by design.

Phase 12 — Preserve and log

Store the original artifact, the transformation record, the checks performed and the analyst identity, and set retention tied to the case rather than to convenience. Precise positions about people should expire. A good output is an auditable record that another analyst can rerun. Stop when the retention date is set and enforced automatically rather than by memory. Log who accessed the precise value and when, since that record is what demonstrates proportionality later.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

Source register: what to collect from, and how

Sources are listed with their access model so you can plan around cost and licensing before you build a dependency on them. Open means no account required; registration means a free account or API key; licensed means paid or institutional access. Always confirm current terms — licensing changes, and a source that was free for research may not be free for commercial or evidential use.

Source	Access	What it gives you	How it is used here
EPSG Geodetic Parameter Registry	Open	Authoritative catalogue of coordinate reference systems, datums, projections and transformation parameters with stable numeric codes.	Identifies exactly which reference frame a coordinate is expressed in and the correct transformation to a common datum.
PROJ	Open	Open source coordinate transformation library implementing datum shifts, projections and grid-based corrections used across geospatial software.	Performs and documents the actual conversions, with transformation pipelines that can be recorded for reproducibility.
Copernicus digital elevation model	Registration	Global elevation data derived from radar missions, distributed at several resolutions through the Copernicus data ecosystem.	Tests whether reported altitude and terrain are consistent with the claimed position and supports viewshed reasoning.
SRTM and USGS elevation products	Open	Shuttle radar topography mission and other elevation datasets covering most of the land surface at moderate resolution.	Independent elevation cross-check where Copernicus coverage or licensing is inconvenient, and long-standing baseline for older analyses.
SunCalc	Open	Solar position calculator giving azimuth, elevation, sunrise, sunset and shadow direction for any coordinate and time.	Core chronolocation check: compares computed sun geometry against shadows visible in imagery tied to the coordinate.
NOAA National Geodetic Survey tools	Open	Datum transformation, geoid models and coordinate conversion utilities for United States and historical reference frames.	Handles legacy North American datums and orthometric height conversion that generic libraries commonly get wrong.
OpenStreetMap and Overpass	Open	Mapped features, buildings, land use and infrastructure queryable by geometry rather than by name.	Establishes what is actually present at and around a point, which either explains or contradicts the reported activity.
Copernicus Browser and Sentinel Hub	Registration	Search and visualisation over Sentinel optical and radar archives with cloud cover and acquisition metadata.	Retrieves imagery covering the exact footprint on dates near the claimed observation for corroboration.
NGA geospatial standards and MGRS references	Open	Military grid reference system definitions and geospatial standards used in defence, maritime and emergency reporting.	Converts between civilian decimal degrees and the grid references used in operational reporting without introducing error.
IGS and international terrestrial reference frame resources	Open	Geodetic reference frame definitions and realisations underlying satellite positioning accuracy over time.	Explains sub-metre discrepancies between reference frame realisations that matter in precise survey and forensic contexts.
Global Historical Climatology and weather archives	Open	Historical surface observations including precipitation, cloud and temperature by station and date.	Cross-checks weather visible in imagery or described in reporting against conditions recorded near the coordinate.
GeoNames and administrative boundary sets	Open	Gazetteer and boundary geometry allowing a point to be resolved to named places and administrative units.	Turns a bare coordinate into a jurisdiction and a named context suitable for reporting at coarse resolution.

Prefer sources that publish a methodology and a revision history. A dataset that changes silently is a liability in any product that has to survive challenge.

Tooling

Tools commonly used against GPS Coordinates. None of these replace judgement, and each carries its own failure modes — know what a tool infers versus what it observes.

QGIS — Desktop GIS handling conversion, plotting, elevation sampling and spatial joins; on-the-fly reprojection can mask datum errors that only surface on export.
PROJ command line utilities — Explicit datum and projection transformation with recordable pipelines; requires the analyst to know the source datum, which is often the missing fact.
GDAL — Reads, converts and samples raster and vector data including elevation models; defaults to assuming the file is right about its own reference system.
ExifTool — Extracts coordinate, altitude, heading and accuracy tags from image and video files; metadata is trivially editable so extraction is not verification.
SunCalc and solar geometry libraries — Compute sun position for chronolocation checks; accuracy depends on correct time zone handling, which is the usual source of a wrong conclusion.
H3 or geohash libraries — Generalise points into cells for privacy-preserving release; cell resolution must be chosen against population density rather than a default level.
PostGIS — Runs containment and proximity queries against boundaries and infrastructure at scale; buffer operations in degrees rather than metres are a routine silent error.

AI skills and automation in detail

These are deterministic jobs with defined inputs and outputs, not open-ended prompting. Each is idempotent and cursor-based: interrupt one and it resumes where it stopped rather than duplicating work or losing progress.

Enrichment Runner — Walks the indicator set through a chosen provider in time-boxed, cursor-based batches that resume rather than restart.
Enrichment → Local — Materialises enrichment into the local store so dashboards render from your own database instead of a live third-party call.
Correlate Infrastructure — Builds the cross-entity link graph: shared hosting, reused certificates, overlapping registrants, repeated selectors.
Summarise (Copilot) — Produces a narrative summary beside the underlying records. It explains; it never creates indicators or assigns attribution.
Generate Report — Assembles a sourced product from the current case or query, with provenance attached to each element.

A note on the boundary: the only skill that involves a language model is Summarise (Copilot), and it writes prose about records that already exist. Nothing else on this list involves generation of any kind. No indicator, relationship or attribution in the platform originates from a model. See the full skill list.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

Precision is a harm decision, not a formatting choice. Six decimal places identifies a doorstep. Decide the published precision deliberately, record why, and keep the precise value in a restricted store rather than in the shared spreadsheet.
Trailing digits reveal provenance. Values rounded to two or three decimals were typed by a human, six decimals with an accuracy field came from a device, and identical repeated points are almost always a default or a parsing failure rather than an observation.
A device position is where the device believed it was, not where it was. Network-derived and last known positions are routinely stored in the same field as satellite fixes, and the accuracy field is the only thing that distinguishes them.
Sun geometry is the cheapest falsification test in the discipline. Shadow direction and length for a claimed coordinate, date and time either fit or do not, and the check takes a minute against a claim that took someone weeks to construct.
Never buffer in degrees. A one degree buffer is a hundred and eleven kilometres at the equator and a fraction of that near the poles, and this single mistake has produced more wrong proximity findings than any deception.
Impossible speed between consecutive points is the signature of mixed sources or spoofing, not of fast travel. Compute implied velocity as a routine cleaning step before any movement claim is made.
Publishing residential coordinates causes physical harm regardless of intent, and the harm does not require the publisher to be wrong. Treat a resolved home address as a finding to be protected, not a result to be demonstrated.

Measuring whether it is working

Capability claims should be falsifiable. These are the measures that show whether work on GPS Coordinates is producing anything, and they are worth baselining before you change process or tooling.

Proportion of coordinate records carrying an explicit datum, accuracy value and source classification rather than bare numbers.
Detection rate for transposition, sign and zero-zero errors during ingest, compared against errors found later in analysis.
Share of chronolocation claims supported by a documented solar geometry or weather check rather than by metadata alone.
Number of publications where precision was reduced by documented harm assessment, tracked as a positive practice measure.
Rate at which precise person-linked coordinates are deleted on schedule rather than retained past their review date, audited by sample rather than self-reported.
Proportion of imagery corroboration attempts that returned usable coverage, as a measure of realistic task planning.

Beware of measuring volume alone. Indicator counts and report counts rise easily and say little; time-to-attribution, proportion of findings that survive review, and how often a product changed a decision say a great deal.

Common pitfalls

Latitude and longitude are frequently transposed, placing points in the wrong hemisphere or the middle of an ocean.
Sign errors during DMS conversion silently mirror a location across the equator or the prime meridian.
Datum mismatch shifts a point by hundreds of metres, which is more than enough to indict the wrong building.
Devices report last known or network-derived positions, so a coordinate may not be where the device actually was.
Excess decimal places imply an accuracy the sensor never had and mislead every downstream consumer of the record.
Publishing precise coordinates of residences, shelters or sources causes direct physical harm regardless of intent.

Legal and ethical considerations

Precise coordinates tied to a person are among the most sensitive data an analyst handles, exposing homes, refuges, sources and daily patterns. Establish a lawful basis and document a necessity test before collecting or retaining device-derived positions, and apply the minimum precision that answers the question. Restrict and log access and set short retention periods. In shared products, generalise to an area unless the finding genuinely requires the point and the harm has been assessed.

Data integrity: no fabrication, no drift, no hallucination

Intelligence that cannot be traced back to a source is not intelligence, it is assertion. Everything in this entry — and everything in the platform behind it — is built on a small number of non-negotiable rules.

Provenance on every record

Every indicator carries the source that supplied it, a first-seen and last-seen timestamp, and a sighting count. Where several feeds report the same artifact, each contribution is recorded separately rather than collapsed, so you can see whether a finding rests on one source or twelve. Source attribution travels with the data into every export, so a recipient can audit a claim without asking you for the working.

Nothing is invented to fill a gap

If the platform has no data for GPS Coordinates, it says so. Empty is displayed as empty — never padded with plausible-looking placeholder values, sample records or illustrative examples that a reader might mistake for observations. A dashboard with no rows is a true statement about collection coverage, and it is treated as a gap to close, not a blemish to hide.

Scoring is deterministic and reproducible

Threat scores, reputation grades and risk tiers are computed from stated inputs with fixed weights, not estimated. The same inputs always produce the same output, and the formula is visible rather than a black box. Aggregates are cached with an explicit time-to-live so a figure on screen is never silently stale — and when a heavy query exceeds its time budget the platform serves the last known-good value and labels it, rather than inventing a fresh number or hanging.

Where AI is used, and where it is not

Language models summarise and explain. They do not create indicators, assign attribution or manufacture relationships. No IP address, wallet, hash or identity in the platform originates from a model — every one is ingested from a named feed, resolved from a reference dataset, or entered by an analyst with a source recorded. Copilot output is presented as narrative alongside the underlying records, never in place of them, so a reader can always check the summary against the evidence.

Guarding against drift

Enrichment is additive and timestamped rather than overwriting. Reference data — sanctions lists, allocations, taxonomies — is re-synchronised from the authority on a schedule instead of being edited in place, so local copies cannot quietly diverge from the source of truth. Attribution is recorded with a confidence level and the reporting it rests on, and inferred relationships are labelled as inferred. When a source retracts or corrects, the correction propagates rather than leaving a stale assertion behind.

What this means for you

You can put a finding from this platform in front of a regulator, a court, a board or a partner agency and show where each element came from. That is the standard the tooling is built to — because in this work, being confidently wrong is more damaging than being usefully uncertain.

By the numbers

The taxonomy this entry belongs to is not a marketing list — it is the actual structure of the platform: 52 mission domains, 52 intelligence disciplines and 65 data points, each with a live dashboard behind it. Supporting that: 18 indicator types, 14 playbooks, 16 AI skills, 18 export formats and a 30-step automated pipeline.

This particular entry connects directly to 10 intelligence disciplines, 10 mission domains, 3 closely related entries — every one of them a tag you can follow, and a dashboard you can open.

Questions analysts actually ask

How many decimal places should I keep?

As many as the source supports and no more. Roughly, five decimal places is about a metre, four is about ten metres, three is about a hundred metres and two is about a kilometre. If a device reported a fifty metre accuracy figure, carrying five decimals implies a precision nobody measured. If a human typed a coordinate off a map, three decimals is generous. Truncate deliberately, store the accuracy alongside, and never let a spreadsheet's default formatting decide. Excess precision is not harmless: it propagates into products, drives false proximity conclusions and encourages exactly the residential resolution you should be avoiding.

The coordinates in this photograph put it in the right city. Is the photograph verified?

No. Metadata is trivially editable and frequently wrong even when nobody has tampered with it, because cameras carry stale positions, wrong time zones and network-derived fixes. Treat embedded coordinates as a hypothesis to be tested against the pixels: match terrain, architecture, signage, road markings, vegetation and infrastructure against mapping and street-level imagery, then test the timestamp against sun position and shadows. A photograph verified by content and geometry is evidence. A photograph verified by its own metadata is an assertion that agrees with itself. Where the two disagree, the pixels usually win.

What is the risk in publishing a geolocated building?

It depends entirely on who is at that building. Identifying a military facility, a factory or a government site is normally proportionate. Identifying a residence, a shelter, a clinic operating discreetly, or a location associated with a witness or a displaced family can lead directly to violence, and the fact that you derived it from public imagery does not reduce that. The working approach is to establish the location precisely for your own confidence, then publish at the coarsest level that supports the claim, and to consult the people who bear the risk before deciding. Record the decision either way.

Two datasets place the same feature about two hundred metres apart. Which is wrong?

Probably neither, and the cause is usually a datum or reference frame mismatch rather than an error. Identical numbers expressed in different datums can sit hundreds of metres apart, and some national systems apply deliberate systematic offsets to published coordinates. Check the declared reference system for each dataset, transform both to a common frame using documented parameters, and compare again. If the offset is consistent in direction and magnitude across many features, it is a datum problem. If it is random, one dataset has genuine positional error, which its metadata should quantify if the producer did their job.

Can I buy commercial location data to place a person somewhere?

For a private actor this is a bad idea legally and evidentially, and in several jurisdictions it is unlawful. Advertising-derived location datasets are collected without meaningful consent for that purpose, and regulators have taken enforcement action against both sellers and buyers. Using such data to track a named individual generally lacks a lawful basis under data protection law, and the provenance will not survive scrutiny in proceedings. The lawful routes to a person's historical location are judicially authorised: a warrant or production order to the provider, executed by an authority with jurisdiction. If your case needs it, refer it rather than buy it.

How do I handle a coordinate with no stated datum?

Assume WGS 84 only if the source is a consumer device or a modern web service, record the assumption explicitly, and treat any position that matters as provisional until you can confirm. Legacy survey data, national mapping outputs and older military reporting often use local datums, and coordinates lifted from paper maps almost always do. Look for corroborating clues: the format, the era, the producing organisation, and whether transforming under a candidate datum makes the point land on the feature it is supposed to describe. Document what you assumed, because the next analyst will otherwise assume something different.

Standards, frameworks and further reading

Work that references a recognised framework is easier to defend, easier to hand over, and easier for a partner to consume:

EPSG dataset codes identify coordinate reference systems and transformations unambiguously and should be cited rather than described in prose.
WGS 84 is the reference frame underlying satellite positioning and the default target datum for interoperable geospatial exchange.
ISO 6709 defines the standard representation of latitude, longitude and altitude for interchange between systems.
ISO 19111 specifies referencing by coordinates, covering datums, coordinate systems and transformations.
ISO 19157 provides the data quality model used to express positional accuracy and uncertainty consistently.
The Berkeley Protocol sets expectations for geolocation methodology and documentation in open source human-rights investigations.
The EU General Data Protection Regulation and equivalent regimes treat precise location tied to an identifiable person as personal data subject to necessity and minimisation.
Additional Protocol I to the Geneva Conventions requires feasible precautions in attack, which in practice imposes a verification standard that a single coordinate cannot meet.

References

Primary sources and authoritative references for this entry. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

EPSG Geodetic Parameter Dataset — International Association of Oil and Gas Producers Geomatics Committee. The reference registry for coordinate reference systems and transformations.
PROJ coordinate transformation software — OSGeo. Open library implementing datum shifts and projections with documented pipelines.
Copernicus Data Space Ecosystem — European Space Agency and European Commission. Elevation models and Sentinel imagery for terrain and footprint verification.
National Geodetic Survey tools and datums — United States National Oceanic and Atmospheric Administration. Datum transformation and geoid models including legacy reference frames.
Berkeley Protocol on Digital Open Source Investigations — United Nations Office of the High Commissioner for Human Rights. Methodological standard for geolocation and chronolocation in accountability work.
Geographic information standards catalogue — International Organization for Standardization technical committee 211. The ISO 19100 series covering spatial referencing, metadata and data quality.
Climate and weather observation archives — United States National Centers for Environmental Information. Historical surface observations used to corroborate conditions at a coordinate and date.
Geospatial standards and reference systems — United States National Geospatial-Intelligence Agency. Grid reference definitions used in operational and emergency reporting.

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this entry: normalises, validates and geospatially joins coordinates while enforcing precision and access controls. Explore the platform, or browse the rest of the library by following any tag above.