In-depth practical guides

Check coordinates before placing them on a map

Check axes, units, reference system and precision before creating a GeoJSON point.

Updated :

Mapping workspace with a map, compass and illustrative coastal image.

Does the pair describe the location you intend?

Decimal-degree latitude and longitude differ from projected coordinates in metres. A point within numeric bounds may still be swapped, shifted or imprecise. Start with source documentation.

  1. Identify the reference system

    Find coordinate system, units and axis order. Do not infer WGS 84 from two small numbers; conversion needs the original reference system.

  2. Check both axes

    Latitude ranges from −90 to 90 degrees and longitude from −180 to 180. RFC 7946 GeoJSON uses longitude first, latitude second.

  3. Preserve stated precision

    Keep original text, measurement method and uncertainty. More decimals do not improve a measurement; a centroid need not identify a building entrance.

  4. Check documentary context

    Compare extent, date, layer and description. Near the antimeridian, avoid conclusions based on simple longitude differences.

Reading workshop

Two plausible numbers do not choose the axes

A fictional point separates order, unit, reference system and precision. Bounds checking follows examination of the source contract.

Fictional data and records for learning: none of these results comes from a live service query.

Position DEMO-G12 documented in WGS 84

The invented source names latitude 35 and longitude 12 in WGS 84 decimal degrees. It describes no person, address or actual measurement.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Position DEMO-G12 documented in WGS 84
Pair or valueReading contractCheck outcomeConclusion to retain
latitude 35; longitude 12Explicitly named fields, WGS 84 degreesThe expected GeoJSON point is [12, 35].The output format determines output order; field names define input.
[35, 12] presented as GeoJSONLongitude, then latitudeBoth values remain within bounds, but the position is reversed.Reject equivalence with the source; bounds cannot recover axis meaning.
650000; 6860000 with unit “metres”Projected coordinates with unspecified source systemThis is not a degree pair to swap.Obtain the source system and a suitable transformation; do not move decimal points to force values within bounds.
35 becomes 35.000000Same numerical value, longer displayNo additional measurement was supplied.Retain declared precision and method without inventing new accuracy.

Check the pair and order before writing a point

Two numbers with a decimal point or comma, at most six decimal places and no thousands separator. Declare order and reference system from the source. The initial example is fictional.

Inspection result

Pair within numeric bounds

The point below follows only the declared order. Still check place, date, precision and source record.

Swapping axes would pass numeric bounds; that does not justify choosing it. No automatic axis swap.

GeoJSON point under the declared assumptions

{"type":"Point","coordinates":[12,35]}

Numeric inspection without a map or geocoding, projection conversion or ground validation. Retain original strings: JSON notation does not measure precision. GeoJSON order is longitude then latitude.

The checker accepts [35, 12]. Has the source position been validated?

Open each proposition to compare its diagnosis. More checks may still be needed.

Yes, all values are within bounds.

Incorrect. The bounds admit both orders in this example. Apply the source’s field definitions.

Yes, after adding six decimal places.

Incorrect. Display formatting repairs neither axis order nor unknown precision.

No; the source yields [12, 35], then its context still needs checking.

That is the expected approach. Changing order establishes neither the described place nor measurement quality.

Fictional point construction record

Position: DEMO-G12; invented example
Source: latitude=35; longitude=12
Unit: decimal degrees; reference: WGS 84
Output order: longitude, latitude
{"type":"Point","coordinates":[12,35]}
Scope: axes transferred; place and precision not certified

This example geocodes nothing and consults no map. A real file retains field definitions, method, date and the document supporting the pair.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

Two plausible axes

Fictional latitude 12, longitude 8 satisfies bounds, as does its reversal. Bounds cannot decide order; read field names.

Excess digits

An illustrative location rounded to one degree is copied with six decimals. The longer format creates no additional geographic precision.

Guided reading of an excerpt

Two valid pairs, two different positions

The fictional source explicitly declares WGS 84 latitude and longitude in decimal degrees. A GeoJSON RFC 7946 point places longitude first.

Fictional exercise: identifiers, values and dates illustrate the check. This excerpt is not a live collected response.

  1. Read the fields

    The source gives latitude 35 and longitude 12. File order does not replace their definition.

  2. Build the expected pair

    The point is [12, 35]. Reversed [35, 12] also passes numeric bounds.

  3. Check the described place

    Compare with expected territory and source precision; bounds alone do not validate location.

Fictional axis conversion example

latitude: 35.0
longitude: 12.0

{"type":"Point","coordinates":[12.0,35.0]}

What to inspect

Axis order
The expected GeoJSON contains longitude then latitude.
Precision
Writing 35.000000 does not improve a measurement supplied as 35.
Does the absence of a numeric error prove the point correct?

Reasoning

No. Both positions fall within bounds. Check field names, reference system and agreement with the documented location.

Official references : IETF — GeoJSON, RFC 7946

Worked exercise

Valid values in the wrong order

Fictional example: the values and documents teach the method and do not describe a real organisation.

Coordinates are in degrees. Values pass range checks; also check how the destination format interprets them.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
ObjectFieldValue
Source rowlatitude48.86
Source rowlongitude2.35
Format or systemCRSWGS84
Exported positionGeoJSON coordinates[48.86,2.35]

Your checks

  1. Read column names and target format.
  2. Check GeoJSON axis order.
  3. Compare the exported point with an expected reference.
Read the answer

Answer and decision

A GeoJSON position uses longitude then latitude: [2.35,48.86]. Reversed values remain in range, so range checking is insufficient. Fix the column mapping rather than manually moving a point while leaving the generator wrong.

If the case changes

For another coordinate system, establish an appropriate transformation before export too.

Record to retain

Keep field names, system, units, mapping and reference-point check.

Documentation reference : IETF — RFC 7946, section 3.1.1 · Consulted on

Record to retain

  • Original pair and field names
  • Reference system, unit and axes
  • Date, method and uncertainty
  • Transformation and checking record

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Is the reference system documented?
  • Is axis order explicit?
  • Does precision come from the source?
  • Do date and extent match the case?

A point with a note stating reference system and location limits.

Frequently asked questions

Do values within bounds establish a place?

No. Swapped axes may remain plausible. Check documentation, context and the selected layer.

Can RFC 7946 GeoJSON declare a local projection instead of WGS 84?

It uses geographic positions in degrees under WGS 84. Transform projected data with a suitable tool first and retain the operation.

How to interpret many decimals?

They describe a digital representation, not necessarily the accuracy of the location. Examine the method, point type and source information before qualifying its accuracy.

TOOLS / REGISTERS

Information to record

Compare extent, date, layer and description. Near the antimeridian, avoid conclusions based on simple longitude differences.

  • Access date and time zone
  • Exact URL
  • Observed passage / value
  • Exact column name
  • Unit / calculation basis
  • Method / definition
  • Version / revision
  • Observed status
  • Limit / uncertainty
  • Decision / next action
  • Review owner
  • Next review

DOCUMENTED REFERENCE

Read GeoJSON coordinate order

Inspect the actual input format before copying coordinates. Do not automatically swap a pair because another tool displays its fields in a different order.

−180°+180°+90°−90°[ longitude, latitude ]
Read GeoJSON coordinate order
ReferenceValue or formWhat it identifies
coordinates[0]longitudeFirst axis.
coordinates[1]latitudeSecond axis.
WGS 84 / CRS84°Decimal degrees.

Implication for the record

Compare the point with a known landmark and retain the source reference system. A plausible position establishes neither accuracy, date nor place identity. This table covers RFC 7946 GeoJSON, not every geographic format.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

IGN: a GNSS height is not directly an altitude

Two vertical values in metres can have different origins. IGN distinguishes ellipsoidal height from altitude in a vertical system. This complements horizontal-coordinate checks before comparing terrain or elevation.

IGN: a GNSS height is not directly an altitude
ReferenceValue or formWhat it identifies
hmEllipsoidal height refers to the geodetic system’s ellipsoid. A GNSS measurement needs its reference frame and determination conditions.
HmAltitude depends on the stated vertical reference system. The symbol m alone does not identify that reference.
h → Hh ≠ HConversion needs a surface model suited to the territory and reference frame. There is no single fixed correction for all of France.
NGF-IGN69HIGN’s FAQ cites NGF-IGN69 for altitude in continental France. Check the exact reference in the dataset metadata.
NGF-IGN78HThe FAQ cites NGF-IGN78 for Corsica. Territory therefore affects conversion choice, not just horizontal coordinates.

Implication for the record

Retain horizontal and vertical references, unit, conversion model and version. Relabelling or applying a Lambert projection does not automatically convert the vertical component. Do not treat h and H as sharing the same zero reference.

Is it possible to subtract two metre values without knowing their vertical systems?

Arithmetic is possible, but interpreting the result as an altitude difference is not established. First verify references, conversions and precision; retain uncertainty if the information is missing.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

Axis order: identify both CRS and reading contract

Plausible numbers do not locate a point without CRS, units and software conventions. GDAL and OGC API Features explain why WGS 84 alone does not settle data order.

Axis order: identify both CRS and reading contract
ReferenceValue or formWhat it identifies
EPSG:4326latitude, longitudeAuthority order is latitude, longitude; data mapping may differ.
OGC:CRS84longitude, latitudeOGC API Features Core defaults to CRS84 longitude, latitude in degrees; not a rule for every mapping API.
OGC:CRS84hlongitude, latitude, ellipsoidal heightCRS84h adds ellipsoidal height, not automatically national levelling altitude.
GDAL ≥ 3OAMS_AUTHORITY_COMPLIANTGDAL 3 defaults to authority axis order. Migrating old jobs may change expectations.
GIS mappingOAMS_TRADITIONAL_GIS_ORDERTraditional GIS mapping reads longitude, latitude for a latitude-longitude CRS. Mapping alone is not reprojection.
Assign / transformmetadata / coordinate operationAssigning CRS describes existing numbers; transforming computes coordinates in a target CRS. Relabelling metres as degrees does not convert.

Implication for the record

Keep CRS, units, axis strategy, software version and an independent control point. Round trips can hide two matching mistakes. Some projected systems use northing-easting authority order.

Does an in-range swapped point prove correctness?

No. Both orders can pass numeric limits. Check the input contract and an independently known point.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

GeoJSON extent: five degrees or almost the world?

RFC 7946 supplies two extents using the same longitude extremes: 5° across the antimeridian versus 355° the other way. Sorting west and east changes the selected region. The explorer uses these documented examples.

GeoJSON extent: five degrees or almost the world?
ReferenceValue or formWhat it identifies
2D bbox[west, south, east, north]2D order is west, south, east, north.
3D bbox[west, south, min height, east, north, max height]3D puts minima of all three axes before their maxima, not three coordinate pairs.
RFC Fiji example[177, -20, -178, -16] → 5°The Fiji example crosses 180° and spans (180 − 177) + (−178 + 180) = 5°.
Other RFC extent[-178, -20, 177, -16] → 355°The other RFC box spans 355°, sharing the −20° to −16° latitude band.
Antimeridianwest > east can be validWest greater than east is valid across the antimeridian; do not reject it categorically.
Latitude−90° ≤ south ≤ north ≤ 90°South stays at or below north, within −90° to 90°. Longitude 178° is possible; latitude 178° is not.

Test a point in both RFC extents

Invented initial point: longitude 178°, latitude −18°. Edges are included; rectangular test, no geocoding.

Inside or on edge · [178, -18]

[177, -20, -178, -16] · Longitude span : 5° · Latitude span : 4°

Test a point in both RFC extentsLinear longitude strip −180° to 180°, fixed scale. Colour shows selected intervals, not a map or distance.-180°-90°0°90°180°longitude
Linear longitude strip −180° to 180°, fixed scale. Colour shows selected intervals, not a map or distance.

Point must also have latitude between −20° and −16°. Dot or comma decimals; no thousands separators.

Implication for the record

Tests only a longitude-latitude rectangle, including edges. It supplies no coastline, national polygon or area. The initial point is invented for testing. Decimal digits do not establish positioning accuracy.

Should west and east be swapped to repair a box?

Not automatically. Crossing boxes would select the large remaining region. Check convention and intended territory first.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

GeoJSON: inspect nesting before counting objects

Files with the same number of positions can describe different objects. Geometry type determines array depth. An interior hole is not another municipality, and repeating the closing position does not add a new vertex.

[100, 0][101, 1]Polygon.coordinates[1]Polygon.coordinates[0]RFC 7946 · A.3
GeoJSON: inspect nesting before counting objects
ReferenceValue or formWhat it identifies
Point[x, y]One position. In GeoJSON, x is longitude and y latitude; interface language does not reverse them.
LineString[[x, y], …]At least two positions in sequence; the first and last do not implicitly enclose an area.
Polygon[ring0, ring1, …]An array of rings: exterior first, holes after it. Ring count is not administrative entity count.
LinearRing≥ 4 positionsA closed ring has at least four positions with identical first and last positions. Three distinct vertices can therefore require four positions.
MultiPolygon[polygon0, polygon1, …]An array of polygons, each with its own interior rings. Do not flatten them into a single outline.
GeometryCollectiongeometriesUses geometries rather than coordinates. It also differs from a FeatureCollection of described features.

Implication for the record

The RFC specifies counterclockwise exterior rings and clockwise holes, while asking readers not to reject older polygons for orientation alone. Correct JSON structure does not establish valid topology, an official boundary or exact area. The diagram uses Appendix A.3’s polygon with a hole; it is not a territorial map.

Primary documentation

Documentation consulted on .

DEEPER READING / PRACTICE

Verify a location before mapping it

A map shows points far from the expected territory. The verification focuses on the order of the coordinates, their system, their accuracy and the meaning of the location.

Updated on .

Priority checks

Keep original values, known system and source. Testing the limits, possible inversions and consistency with the available territorial attributes.

Interpretation pitfalls

A technically valid point can represent a centerid rather than an exact address. The accuracy displayed does not demonstrate the accuracy of the observation.

Working record to retain

The control report combines coordinates, system, location type and anomaly. Correction preserves its rule and initial value.