Did you know that two perfectly reasonable-looking numbers can send a map pin to the wrong side of the world? A student copying a pair of coordinates might preserve every digit and still reverse its meaning. This is a useful lesson in why accurate data handling begins with knowing what each position represents.
Latitude measures a position north or south of the equator; longitude measures position east or west of the prime meridian. In familiar prose the pair is often spoken as latitude then longitude. But a GeoJSON Point uses its coordinate array in the order [longitude, latitude]. The immediate answer is to check the required format, label the two quantities explicitly, preserve signs and only then place a map pin.
Our worked coordinates are invented teaching examples, not verified addresses for schools, homes or field sites. We will use decimal degrees, not degrees-minutes-seconds, and no live location or personal tracking data is needed.
A two-question diagnostic before opening a map
Ask the learner: ‘Which coordinate can reach 180 degrees east or west? Which can reach 90 degrees north or south?’ Latitude ranges from 90 degrees south to 90 degrees north. Longitude is commonly represented from 180 degrees west to 180 degrees east. A response that reverses these ranges shows the learner is relying on number order rather than the geography.
Now ask: ‘If a worksheet displays Latitude 1.30° N, Longitude 103.80° E, should I type [1.30, 103.80] into a GeoJSON Point?’ No. In GeoJSON the two-element position is [103.80, 1.30]. In the swapped version, 103.80 would occupy the latitude slot, outside its ordinary valid range.
What the two coordinate axes actually describe
Latitude circles are parallel to the equator; the latitude number describes north-south position. The equator is zero. Positive latitude commonly means north and negative latitude south in signed decimal notation. Thus +1.30° means 1.30 degrees north, while −1.30° means 1.30 degrees south. These are angular positions, not distances in kilometres.
Longitude measures position around Earth in relation to the prime meridian, with east usually positive and west negative in signed decimal notation. A positive 103.80° longitude represents 103.80 degrees east. A negative 81.20° longitude represents 81.20 degrees west. Geographic latitude and longitude are not Cartesian lengths: the physical distance represented by a degree of longitude changes markedly with latitude.
A notation can use N, S, E and W letters instead of signs. If the software requires numbers, convert the hemisphere notation consistently: 35.1° N → +35.1, 81.2° W → −81.2. Do not type a minus sign and a contradictory east/west letter together and hope that the software will guess.
Why map tools can expect different orders
People commonly read a map location in ‘latitude, longitude’ order because geographic lessons teach north-south position before east-west position. Many online maps show this convention to readers. GeoJSON is a specific data interchange standard with a fixed geometry-position convention: first longitude, then latitude. Its authors use x-then-y style ordering, so the array begins with the east-west coordinate.
There is no general rule that every web form, spreadsheet, programming library or mapping tool uses the same order. Some tools request latitude and longitude as named fields; others use longitude and latitude as unnamed array positions. A CSV column heading is not automatically a GeoJSON array position. Read the expected input documentation, not just the example you saw on another platform.
A full hand-checked example using a fictional point
Suppose a fictional field-study point is labelled latitude 1.30° N; longitude 103.80° E. First convert the hemisphere notation: latitude = +1.30°; longitude = +103.80°. Both numbers pass the ordinary range check: |latitude| ≤ 90 and |longitude| ≤ 180.
Next construct the GeoJSON position: [103.80, 1.30]. The first value is longitude, the east-west angle; the second is latitude, the north-south angle. A simple GeoJSON object is {"type":"Point","coordinates":[103.80,1.30]}. The data structure has no need for N and E letters because signs encode hemisphere.
Read the saved position backwards as an independent check. ‘Longitude +103.80° E; latitude +1.30° N’ matches the original labels. That round trip—labels to format and format back to labels—catches an order error before anyone uses the result to plan a journey or report an observation.
Now deliberately reverse the values. The incorrect GeoJSON array [1.30, 103.80] treats 103.80° as latitude, outside the allowed latitude range, so validation can reject it. That seems easy; however, this friendly example hides a more serious case.
The dangerous case: a swapped pair that is numerically valid
Take another entirely fictional point: 35.1° N, 81.2° W. The signed latitude is +35.1°, and the signed longitude is −81.2°. Correct GeoJSON is [-81.2, 35.1]. Both positions are within their valid angular ranges.
A mistake could produce [35.1, -81.2]. Here the interpreted longitude is +35.1° and latitude is −81.2°. Both are still numerically valid, but the result describes a radically different position. A range check alone would not detect it. A second check must use expected hemisphere, known region, source labels or a credible reference map.
This is why reliable work uses both syntax checks and meaning checks. ‘The numbers fit the allowed range’ is not the same as ‘the location is correct’. In data science, computing and geography, valid input can still be wrong input.
A step-by-step map-pin checking routine
- Record the source exactly: its location name or fictional label, latitude, longitude, hemisphere letters, datum or coordinate reference system if supplied, and source date.
- Convert degrees with hemisphere letters into signed decimal degrees, documenting the conversion.
- Check latitude is between −90° and +90°, and longitude in the usual −180° to +180° range.
- Read the destination’s specification: named latitude/longitude fields versus an ordered GeoJSON coordinates array.
- Write or import the values in the required order, without adding spurious units inside numeric slots.
- Plot the point and compare the result with a region or landmark you reasonably expect.
- Read the stored values back, checking signs and field identities before reporting the pin as accurate.
A small dataset with three coordinate mistakes
Imagine a school-group spreadsheet with three invented rows. Row A lists Lat +1.30, Lon +103.80. Row B lists Lat +35.10, Lon −81.20. Row C lists Lat −6.20, Lon +106.80. The correct GeoJSON arrays are A [103.80, 1.30], B [-81.20, 35.10] and C [106.80, -6.20].
If a conversion script creates A [1.30, 103.80], B [35.10, −81.20] and C [−6.20, 106.80], all three are wrong. A and C should fail basic latitude-range validation; B is particularly dangerous because both numbers fit legal ranges despite the swap. Ask students to identify which rows a naive range checker misses.
The point is not to memorise a famous location. It is to reason across three representations: labelled observation, signed numeric values and the specified file format. A consistent decoding rule lets students work with new coordinates they have never seen.
Guided practice: learn the order from both directions
Task one: hemisphere and signs
A worksheet states latitude 12.5° S and longitude 77.6° E. Write signed values: latitude −12.5°, longitude +77.6°. Its GeoJSON position is [77.6, -12.5]. Check backwards: +77.6 east; −12.5 south. The worked example is not a claim about an actual city.
Task two: detect the wrong array
A map file contains "coordinates":[-72.4,14.6]. If it is a conforming geographic GeoJSON point, the longitude is −72.4°, the latitude is +14.6°. The order is not chosen by whichever number ‘looks more like latitude’. The standard supplies the meaning.
Task three: diagnose without a map image
A student records ‘Lat = 105.0°, Lon = 3.0°’ as ordinary latitude and longitude. Explain why that label pair itself needs review: 105° is beyond the latitude range. Do not automatically swap it and call the correction confirmed. Ask for the original source because it might reflect transposed fields or another coordinate system.
Independent challenge
Prepare the GeoJSON position for an invented point with 48.2° N and 122.3° W. Answer: [-122.3, 48.2]. Then explain why exchanging the two elements is wrong, even if a mapping application silently renders something. A complete answer should mention both the formal array convention and the need for real-world plausibility checking.
Common misconceptions and fixes
- ‘Latitude must be first because my atlas prints it first.’ Human presentation order does not determine GeoJSON storage order.
- ‘Positive numbers are always north.’ A positive longitude represents east; latitude and longitude have different axes.
- ‘If both values are legal, the pin must be correct.’ Swapped valid numbers can still represent another location.
- ‘A degree of longitude always equals a fixed number of kilometres.’ Its physical length varies with latitude.
- ‘Every coordinate is WGS 84 latitude/longitude.’ Projected grids can use metres and another reference system; read the data specification.
- ‘I can replace a missing hemisphere by guessing from the country.’ Missing sign or reference information should be resolved from the source, not invented.
What learners, parents and teachers can do next
Students can make a two-column conversion sheet labelled ‘human latitude/longitude’ and ‘GeoJSON longitude/latitude’. For each row they should describe the physical meaning of each field in ordinary words. Teachers can include one numerically invalid swap and one silently valid swap to test conceptual understanding rather than rote range checking.
Parents do not need specialist mapping software to ask a strong question: ‘Which number tells us north or south, and which tells us east or west?’ A learner’s ability to answer that independently is more meaningful than how quickly they copy a pin from an example.
Progress is observable when a student can explain the input convention, detect a swapped pair, preserve hemisphere signs, and read a saved array back into human-readable coordinates. Encourage a habit of keeping the source and format specifications together with the data.
Limitations, coordinate systems and privacy
The examples assume ordinary geographic coordinates in decimal degrees. Real map projects can use projected coordinates, national grids, transformations, differing datums and different axis-order conventions. The accepted values for a specific software endpoint may have additional requirements. A file’s geometry type and coordinate reference context matter as much as its two numbers.
For actual field trips, use official, up-to-date location information and do not publish precise locations of children’s homes, restricted school activities or personal movement records. A classroom demonstration can use invented points or appropriately public map features instead.
Frequently asked questions
Is latitude a horizontal line or a horizontal movement?
Lines of constant latitude run east-west, but a change in latitude measures movement north or south. That apparent reversal is a common source of confusion: distinguish the direction a line runs from the coordinate it measures.
Why does GeoJSON list longitude first?
The standard defines a position as x-then-y style values, beginning with longitude for geographic coordinates. Following the specification is the reliable rule regardless of habits on a particular mapping website.
Can I check coordinate order just by looking for a number over 90?
Only sometimes. An out-of-range latitude is a strong warning, but many swapped coordinate pairs remain within both numerical bounds. Always check source labels and plausible geography.
Is the same order always used by other GIS software?
No. Some interfaces request named latitude/longitude fields, while others follow x/y or specific protocol conventions. Check the tool and file-format documentation each time.
Are these coordinates a claim about a real school’s location?
No. All plotted points in this lesson are illustrative values used to explain signs, degrees and ordering. Do not use them as directions.
Primary geographical and data-format references
The U.S. National Ocean Service explains latitude and longitude, including their angular directions and ranges. The actual interchange rule comes from RFC 7946, Section 3.1.1, which specifies longitude before latitude in a GeoJSON position. These primary references, rather than an undocumented web-tool convention, govern the discussion.
Nearby eduKate lessons include using a map scale bar after resizing and keeping online source evidence with a screenshot. See the Core Aim of Education hub and Education Hub for further transfer.
The diagnosis-first and independent-checking sequence mirrors the principles explained in the Clementi Mathematics tutorial reference.
The core aim: keep meaning attached to data
A pair of numbers is not self-explanatory. Labels, units, signs, order and reference systems tell us what those numbers can mean. When learners check those details before trusting a map pin, they practise the same care they need for scientific graphs, spreadsheet formulas and evidence-based decisions.