Translate | ISO 6709:2022 Coordinates, Latitude and Longitude Order, CRS, Elevation and Location Data

Translating ISO 6709:2022 coordinate information requires more than changing place names into another language. When a reader searches for latitude longitude translation, coordinate format translation, GPS coordinate order, decimal degrees conversion or coordinate reference system translation, a very small sign, axis or unit error can move a supposed location far away. A usable multilingual location record must preserve the numerical point while explaining the notation in terms the receiving reader can follow.

ISO 6709:2022 is a published standard on representing a geographic point location by coordinates. Its public ISO scope covers latitude and longitude, optional height or depth, other coordinate types and associated time using one or more coordinate reference systems. It describes text for one point in data exchange and a simpler human-readable form; it does not authorise translators to infer an unknown datum, reverse axes based on habit or assume every GPS-looking string uses the same system.

The quick answer: copy numeric data exactly, confirm axis order and direction, keep the coordinate reference system and vertical reference where supplied, and make any conversion reproducible. This guide walks through multilingual field logs, mapping app exports, survey certificates, rescue location messages, property plans and digital records. Each example is invented for teaching and should not be used as a navigation instruction or exact site coordinate without independent verification.

Quick information: the decision this translation must protect

Identify the source document, its edition, issuing organisation and intended decision.
Keep every product, specimen, location, identifier, role and revision aligned with its original record.
Do not turn a proposed action into an approved action or a reported observation into a guarantee.
Carry quantities, units, dates, thresholds, exceptions and uncertainty into the receiving language.
Keep source evidence distinct from editorial explanation and requests for clarification.
Use a subject-matter reviewer when a translation could affect safety, privacy, compliance, purchasing or public claims.
Preserve the original record and maintain a traceable revision history.
Give the reader a short answer first, then enough context to make that answer reliable.

The official standard: scope, edition and what this guide does not claim

ISO 6709:2022 addresses how a point location is represented for interchange and human readability, including contextual CRS identification. A file of many points sharing one CRS is outside the specific document scope described in the public abstract. The 2008 edition is withdrawn; the 2022 edition is the relevant current version. The public source is the official ISO catalogue entry. ISO standards are copyrighted publications. This independently written educational article is not the purchased standard, a certified translation of its clauses or evidence of product or organisational conformity. Where the exact contractual or regulatory obligation matters, consult the licensed edition, its amendments and the competent authority.

The narrower search intent here is how to translate coordinate strings, map labels, survey instructions and geospatial exchange records without reversing latitude and longitude, changing the reference system or confusing altitude with depth. It does not attempt to become a general translation handbook. Its examples are constructed and are not actual documents from a laboratory, government, printer, software supplier or customer. Real translations should preserve a secure copy of the actual source, obtain permission to handle confidential material and be reviewed by the people authorised to act on the result.

Understand the vocabulary before the document

Term or field	Meaning to preserve
latitude	North–south angular position, expressed with a sign or a hemisphere indicator.
longitude	East–west angular position; not interchangeable with latitude.
CRS	Coordinate reference system describing how positions are referenced.
datum	Underlying reference framework that matters for interpreting coordinates.
elevation	Vertical position relative to a specified vertical reference.
depth	Vertical displacement in a stated direction and reference.
decimal degrees	Angular values written as fractional degrees.
DMS	Degrees, minutes and seconds, with each component preserved.
axis order	The defined order of coordinate values in a record.
precision	How finely a number is expressed; not automatically its positional accuracy.
accuracy	Closeness to the true or accepted location, subject to a stated method.
geospatial timestamp	The recorded time associated with an observation or location.

A terminology table is a starting point, not a machine for replacing words one by one. A word’s practical meaning depends on its position in the record, the unit attached to it, the person who may authorise the next action and the consequences of an incorrect reading. Before finalising, check whether the same English expression names a measurement, a request, a permission or a completed event. Those distinctions are especially vulnerable when short database labels are localised without the surrounding workflow.

Part I: build a faithful explanation from the underlying evidence

1. First determine whether the string is a position

The distinction. A coordinate record may be a measured observation, a proposed location, an estimated address or an illustrative example. In geographic point-location records, a phrase is not just vocabulary: it carries a permission, quantity, observation or decision that somebody else may act upon. Before translating, separate the recorded event from the writer’s interpretation of the event. Where the original does not name the responsible person, the date or the scope, do not quietly supply them in the target language. A reader should be able to trace each claim back to a specific element in the source.

A practical check. Read the source’s record type, origin and measurement method. Contrast that evidence with the failure pattern: Translating ‘approximate point’ as ‘surveyed point’ creates authority that was never present. One reviewer should inspect the terminology and a second, suitably qualified owner should confirm the operational interpretation when the consequences are material. An apparently exact location can still be only an estimate. If the record cannot support the confident reading, retain its original uncertainty and explain what further confirmation is needed.

2. Keep latitude and longitude in their declared order

Why the wording matters. Map applications differ in presentation and some APIs use x,y order; an ordinary reader may expect latitude first. International readers may approach the same record through procurement, audit, operations or customer service, and each will be tempted to complete missing context differently. A confident English sentence can sound like an operational assurance even when the source merely reports a provisional observation. Keep that distinction visible in ordinary words. Accurate localisation is not a choice between literal language and readability; it is the work of making the source’s actual scope readable.

Where translations go wrong. Reversing the values can produce a valid-looking but incorrect point. The cure is not to make the sentence longer without purpose. It is to carry over the discriminating details: Check the named schema and axis-order convention rather than assuming a universal display order. A harmless-looking reformatting can send people to a different continent. In a bilingual table, place source status, verified target wording and unresolved query in separate fields so readers can see what belongs to the source and what remains editorial work.

3. Respect signs and hemisphere letters

Read the event before the terminology. A minus sign may encode south or west while N, S, E and W convey direction in text. Ask what happened, who recorded it and what the record is meant to support. Then test the translation against a second possible situation: would the same translated sentence still seem true if the next decision went the other way? This counterfactual check reveals when a translator has accidentally added approval, certainty or completion. It is especially useful where a source field is short but its operational meaning is narrow.

The common trap. Removing the negative sign to simplify typography changes the hemisphere. A reliable editorial review checks something observable rather than simply asking whether the prose sounds natural. Inspect directional indicators and whether the notation combines sign and hemisphere. Record any clarification as a question to the source owner; keep the unanswered question separate from the published translation. Small glyph changes can change the geographic meaning completely. This is why the best final version may be less dramatic, but more useful, than an apparently elegant paraphrase.

4. Never infer a missing coordinate reference system

The distinction. The same numeric values can be interpreted differently when their coordinate framework changes. In geographic point-location records, a phrase is not just vocabulary: it carries a permission, quantity, observation or decision that somebody else may act upon. Before translating, separate the recorded event from the writer’s interpretation of the event. Where the original does not name the responsible person, the date or the scope, do not quietly supply them in the target language. A reader should be able to trace each claim back to a specific element in the source.

A practical check. Identify the explicitly supplied CRS, its identifier and available transformation parameters. Contrast that evidence with the failure pattern: Labelling unspecified values ‘WGS 84’ because a consumer GPS is common creates an unsupported claim. One reviewer should inspect the terminology and a second, suitably qualified owner should confirm the operational interpretation when the consequences are material. A map conversion needs evidence, not a translator’s assumption. If the record cannot support the confident reading, retain its original uncertainty and explain what further confirmation is needed.

5. Separate horizontal from vertical references

Why the wording matters. Height can refer to different vertical models and depth can be measured from various surfaces. International readers may approach the same record through procurement, audit, operations or customer service, and each will be tempted to complete missing context differently. A confident English sentence can sound like an operational assurance even when the source merely reports a provisional observation. Keep that distinction visible in ordinary words. Accurate localisation is not a choice between literal language and readability; it is the work of making the source’s actual scope readable.

Where translations go wrong. Converting ‘height above local datum’ into ‘height above sea level’ is a substantive change. The cure is not to make the sentence longer without purpose. It is to carry over the discriminating details: Preserve the stated reference surface and unit; mark any absent datum as unknown. A misplaced vertical reference can mislead engineering and hazard interpretation. In a bilingual table, place source status, verified target wording and unresolved query in separate fields so readers can see what belongs to the source and what remains editorial work.

6. Read degrees, minutes and seconds carefully

Read the event before the terminology. DMS notation divides angle into components with bounded units; decimal degrees use a different numerical form. Ask what happened, who recorded it and what the record is meant to support. Then test the translation against a second possible situation: would the same translated sentence still seem true if the next decision went the other way? This counterfactual check reveals when a translator has accidentally added approval, certainty or completion. It is especially useful where a source field is short but its operational meaning is narrow.

The common trap. Treating minutes as decimal fractions of a degree produces incorrect positions. A reliable editorial review checks something observable rather than simply asking whether the prose sounds natural. Identify symbols, order and whether the digits represent angular seconds. Record any clarification as a question to the source owner; keep the unanswered question separate from the published translation. A translation must not disguise a conversion error as improved readability. This is why the best final version may be less dramatic, but more useful, than an apparently elegant paraphrase.

7. Distinguish display precision from accuracy

The distinction. Six decimal places suggest numerical resolution, not an instrument’s actual confidence. In geographic point-location records, a phrase is not just vocabulary: it carries a permission, quantity, observation or decision that somebody else may act upon. Before translating, separate the recorded event from the writer’s interpretation of the event. Where the original does not name the responsible person, the date or the scope, do not quietly supply them in the target language. A reader should be able to trace each claim back to a specific element in the source.

A practical check. Retain the source’s reported precision and its separately stated uncertainty. Contrast that evidence with the failure pattern: Adding decimals during a translation makes rough map pins look surveyed. One reviewer should inspect the terminology and a second, suitably qualified owner should confirm the operational interpretation when the consequences are material. Readers need to know what the digits can and cannot establish. If the record cannot support the confident reading, retain its original uncertainty and explain what further confirmation is needed.

8. Handle decimal commas and separators deliberately

Why the wording matters. In several languages the comma is a decimal mark, while other systems use it between coordinates. International readers may approach the same record through procurement, audit, operations or customer service, and each will be tempted to complete missing context differently. A confident English sentence can sound like an operational assurance even when the source merely reports a provisional observation. Keep that distinction visible in ordinary words. Accurate localisation is not a choice between literal language and readability; it is the work of making the source’s actual scope readable.

Where translations go wrong. A locale conversion can split one measurement into two fields. The cure is not to make the sentence longer without purpose. It is to carry over the discriminating details: Specify data format for machines and a readable labelled format for humans. Software parsing errors may silently move or reject a point. In a bilingual table, place source status, verified target wording and unresolved query in separate fields so readers can see what belongs to the source and what remains editorial work.

9. Keep time with location when it matters

Read the event before the terminology. Mobile receivers, vessel reports and moving observations need timestamps and time scales. Ask what happened, who recorded it and what the record is meant to support. Then test the translation against a second possible situation: would the same translated sentence still seem true if the next decision went the other way? This counterfactual check reveals when a translator has accidentally added approval, certainty or completion. It is especially useful where a source field is short but its operational meaning is narrow.

The common trap. A time converted across UTC offsets without a date adjustment can pair a point with the wrong event. A reliable editorial review checks something observable rather than simply asking whether the prose sounds natural. Retain original timezone and converted local date if both are shown. Record any clarification as a question to the source owner; keep the unanswered question separate from the published translation. Temporal errors can invalidate movement reconstruction. This is why the best final version may be less dramatic, but more useful, than an apparently elegant paraphrase.

10. Translate place names as labels, not measurements

The distinction. A named place and its geometric coordinates are related but not synonymous. In geographic point-location records, a phrase is not just vocabulary: it carries a permission, quantity, observation or decision that somebody else may act upon. Before translating, separate the recorded event from the writer’s interpretation of the event. Where the original does not name the responsible person, the date or the scope, do not quietly supply them in the target language. A reader should be able to trace each claim back to a specific element in the source.

A practical check. Preserve the coordinate record and explain the place name as a separate label. Contrast that evidence with the failure pattern: Substituting a nearby landmark for an unfamiliar toponym changes the referenced point. One reviewer should inspect the terminology and a second, suitably qualified owner should confirm the operational interpretation when the consequences are material. An explanatory gloss is not a coordinate correction. If the record cannot support the confident reading, retain its original uncertainty and explain what further confirmation is needed.

11. Avoid silently broadening a point into an area

Why the wording matters. A point can mark a meeting location, centroid, facility entrance or rough vicinity. International readers may approach the same record through procurement, audit, operations or customer service, and each will be tempted to complete missing context differently. A confident English sentence can sound like an operational assurance even when the source merely reports a provisional observation. Keep that distinction visible in ordinary words. Accurate localisation is not a choice between literal language and readability; it is the work of making the source’s actual scope readable.

Where translations go wrong. Writing ‘the district’ where the source specifies a single site can alter routing instructions. The cure is not to make the sentence longer without purpose. It is to carry over the discriminating details: Identify whether the data is a point, boundary, route or geofence. Readers should not confuse location specificity with contextual area. In a bilingual table, place source status, verified target wording and unresolved query in separate fields so readers can see what belongs to the source and what remains editorial work.

12. Protect sensitive location information

Read the event before the terminology. Some coordinates identify homes, endangered habitats or restricted facilities and should not be published casually. Ask what happened, who recorded it and what the record is meant to support. Then test the translation against a second possible situation: would the same translated sentence still seem true if the next decision went the other way? This counterfactual check reveals when a translator has accidentally added approval, certainty or completion. It is especially useful where a source field is short but its operational meaning is narrow.

The common trap. Translation can expand an audience even when the numerals are unchanged. A reliable editorial review checks something observable rather than simply asking whether the prose sounds natural. Check access purpose, audience and permissible level of geographic precision. Record any clarification as a question to the source owner; keep the unanswered question separate from the published translation. Accurate translation and responsible disclosure are separate requirements. This is why the best final version may be less dramatic, but more useful, than an apparently elegant paraphrase.

Part II: worked translation records and corrections

The examples below are invented to expose specific failure modes. They are not extracted from ISO clauses and cannot substitute for laboratory instructions, software schemas, geodetic transformations, security controls or local law. The wrong versions are included only to make the error easy to recognise. A practitioner should not copy numerical examples into real work.

Case 1: Simple signed pair

Fictional source record: “Latitude -33.8650; longitude +151.2094.” Misleading rendering: “33.8650 north, 151.2094 east.” Defensible English rendering: “Latitude 33.8650° S; longitude 151.2094° E.”

Negative latitude indicates south; positive longitude indicates east. Confirm the source declares lat/long order. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Reader decision. A receiving team should not act on the rejected paraphrase. They should retain the narrower reading, ask for the named check and document whether that check changed the record. If a local-language explanation is needed, add it outside the preserved identifier or reported result so that the raw evidence survives a later audit.

Case 2: Axis order declared

Example source: “Fields x=103.85; y=1.29 in schema A.” A rushed translation might say “Latitude 103.85; longitude 1.29.”. A faithful version says “Schema A lists x=103.85 and y=1.29; axis meanings require confirmation.”.

An x/y schema cannot be casually renamed without definition. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Consult schema before labelling latitude and longitude. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Review exercise. Put the source, proposed English and final English in three adjacent columns. Ask a colleague who has not seen the case to identify exactly what is known, unknown and approved. If that colleague cannot distinguish those states, edit the wording before anyone relies on it.

Case 3: CRS missing

Original hypothetical note: “Coordinates: 500000, 4700000; CRS not stated.” Do not write: “GPS latitude 500000, longitude 4700000.”. Write: “Coordinate values 500000 and 4700000; coordinate reference system not specified.”.

Projected coordinates are not automatically angles. Request CRS identifier and axis units. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Handover note. A multilingual recipient needs a clear answer and a clear limit. The answer is the defensible rendering above; the limit is the still-unverified detail. Keep this distinction in the sentence or its immediately adjacent note rather than hiding it in a general disclaimer at the end of a long document.

Case 4: DMS example

Record as received: “51°30′26″N 0°07′39″W.” Overconfident version: “51.3026 N, 0.0739 W.”. Evidence-preserving version: “51 degrees 30 minutes 26 seconds north; 0 degrees 7 minutes 39 seconds west.”.

DMS parts are not decimal suffixes. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Convert only with explicit mathematical method. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Quality gate. Verify numbers and names character by character, then verify the statement’s status: observed, proposed, requested, confirmed or authorised. Do not let a reviewer approve attractive wording before checking whether it changes that status. A correct translation preserves both the sentence and the reason the sentence can be trusted.

Case 5: Approximate pin

Fictional source record: “Approx. location, accuracy ±100 m.” Misleading rendering: “Exact site coordinates.” Defensible English rendering: “Approximate location; reported positional uncertainty is ±100 m.”

Precision and uncertainty must be kept separate. Ask what confidence convention the ± uses. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Case 6: Vertical datum

Example source: “Height 30 m above local benchmark LB-1.” A rushed translation might say “Elevation 30 m above sea level.”. A faithful version says “Height 30 m relative to local benchmark LB-1.”.

Local reference is not automatically mean sea level. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Preserve benchmark identity. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Case 7: Depth statement

Original hypothetical note: “Depth 6 m below chart datum.” Do not write: “6 metres below ground level.”. Write: “Depth 6 m below the stated chart datum.”.

Chart datum and ground surface differ. Retain reference definition. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Case 8: Decimal comma

Record as received: “Latitude 48,8566 N; longitude 2,3522 E, comma denotes decimals.” Overconfident version: “48 and 8566 north; 2 and 3522 east.”. Evidence-preserving version: “Latitude 48.8566° N; longitude 2.3522° E (decimal marks converted).”.

Locale punctuation is structural data here. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Check parser and label converted representation. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Case 9: Unicode minus

Fictional source record: “Latitude −12.34 with mathematical minus glyph.” Misleading rendering: “Latitude 12.34.” Defensible English rendering: “Latitude -12.34, south of equator (ASCII minus in machine field).”

A visually subtle minus can be lost in copying. Validate sign survived export. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Case 10: Latitude limit

Example source: “Latitude 117.2°, source unverified.” A rushed translation might say “117.2° north valid.”. A faithful version says “Source states latitude 117.2°; value requires correction before use.”.

Latitude magnitude cannot exceed 90 degrees. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Escalate impossible coordinate rather than normalising. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Case 11: Longitude near date line

Original hypothetical note: “Longitude 179.9° E.” Do not write: “Longitude 179.9° W.”. Write: “Longitude 179.9° E.”.

Reversing hemisphere near the date line can be disastrous. Confirm directional letter in original. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Case 12: Timestamp across date

Record as received: “Observation 2026-11-07 23:30 UTC.” Overconfident version: “Observation November 7 at 23:30 Singapore.”. Evidence-preserving version: “Observation 2026-11-08 07:30 at UTC+08:00 (original: 2026-11-07 23:30 UTC).”.

Time conversion crosses calendar midnight. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Keep source instant and local conversion labelled. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Case 13: Estimate vs survey

Fictional source record: “Map pin inferred from street address; not field surveyed.” Misleading rendering: “Survey-confirmed coordinate.” Defensible English rendering: “Location estimated from address; no field survey reported.”

Method of location matters as much as its digits. Ask for survey certificate before upgrading claim. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Case 14: Single point vs route

Example source: “Waypoint P4 is one point on walking route.” A rushed translation might say “This is the full walking route.”. A faithful version says “Waypoint P4 marks one point on a wider route.”.

One-point data is not a polyline. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Consult route file for other points. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Case 15: Coordinate pair separated by comma

Original hypothetical note: “String ‘1.3000,103.8000’ with documented lat,lon.” Do not write: “1,3000 and 103,8000 with regional commas.”. Write: “Latitude 1.3000°; longitude 103.8000° under documented lat,lon convention.”.

Separators and decimal notation must be unambiguous. Read back against schema. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Case 16: Identifier versus display

Record as received: “CRS code EPSG:4326 supplied.” Overconfident version: “EPSG:4326 means metres east and north.”. Evidence-preserving version: “CRS identifier EPSG:4326 retained; axis and units follow its definition.”.

A reference code cannot be paraphrased into convenient but wrong units. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Check authoritative CRS metadata. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Case 17: Old datum noted

Fictional source record: “Legacy survey uses local datum LD-1976.” Misleading rendering: “Updated to WGS 84 coordinates.” Defensible English rendering: “Coordinates remain in legacy datum LD-1976; no transformation supplied.”

Updating names without transformation changes the location. Require qualified geodetic conversion. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Case 18: Blank vertical position

Example source: “Latitude and longitude present; altitude null.” A rushed translation might say “Altitude zero.”. A faithful version says “No altitude value was supplied.”.

Null indicates unknown or absent, not a zero measurement. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Keep null in data and write ‘not provided’ to readers. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Case 19: Privacy rounding

Original hypothetical note: “Sensitive nesting site coordinates rounded for public map.” Do not write: “Precise scientific survey location.”. Write: “Public map presents deliberately rounded coordinates to protect site.”.

A rounded representation is not source precision. Distinguish restricted master from public output. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Case 20: Signed zero

Record as received: “Longitude -0.0000 in source system.” Overconfident version: “0.0000 E.”. Evidence-preserving version: “Longitude -0.0000 as recorded; hemisphere convention needs review.”.

Even signed zero may carry a direction convention in a data system. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Check output policy before stripping sign. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Case 21: Relative location

Fictional source record: “Entrance 20 m north of marker K1.” Misleading rendering: “Entrance at latitude 20 north.” Defensible English rendering: “Entrance is approximately 20 m north of marker K1.”

Relative offsets are not absolute coordinates. Retain the marker identity and units. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Case 22: Magnetic vs true bearing

Example source: “Bearing 045° magnetic; position separately listed.” A rushed translation might say “True bearing 045°.”. A faithful version says “Bearing 045° magnetic; geographic point coordinates are separate.”.

Directional bearings require a reference north. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Do not derive one without variation data. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Case 23: Depth sign convention

Original hypothetical note: “z=-2.4 m under downward-negative convention.” Do not write: “Depth is negative 2.4 metres upward.”. Write: “z=-2.4 m, using the document’s stated downward-negative vertical convention.”.

Sign semantics depend on the coordinate model. Preserve sign and convention in the same sentence. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Case 24: Degree symbol OCR error

Record as received: “Latitude 40°12′; OCR returns 4012.” Overconfident version: “Latitude 4012 degrees.”. Evidence-preserving version: “Latitude 40 degrees 12 minutes; OCR character loss identified.”.

Typography can merge components. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Compare scanned original and structured file. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Case 25: Multiple candidate points

Fictional source record: “Two possible entrances listed A and B; no selection.” Misleading rendering: “Official entrance is A.” Defensible English rendering: “Two candidate entrance points, A and B; no final selection recorded.”

Choosing a point is a decision beyond translation. Request owner confirmation before route release. The translation problem is not solved by substituting a technical synonym. Look first at the object, then the event and then the evidentiary status. For this particular record, the misleading version would invite a reader to treat an unsupported conclusion as established fact. Keep identifiers and quantities in a form that another reviewer can compare with the source document, and distinguish a reported value from a conclusion derived elsewhere.

Case 26: Boundary centroid

Example source: “Polygon centroid provided as approximate reference point.” A rushed translation might say “Exact property boundary location.”. A faithful version says “Approximate polygon centroid supplied as reference point; not a boundary survey.”.

A centroid is one location summarising an area. The correct sentence makes the reader’s next decision more defensible because it does not overclaim what the record establishes. Retain geometry type and confidence. If the governing source also contains footnotes or an exception field, the target-language copy should preserve the link between that qualifier and this item. Where a figure is machine-readable, avoid casual punctuation changes; where it is a human instruction, use enough ordinary explanation to prevent a wrong action.

Case 27: Public rescue message

Original hypothetical note: “Caller states ‘near the bridge’, coordinates from phone unverified.” Do not write: “Rescue location is confirmed at coordinates.”. Write: “Caller-reported phone coordinates are unverified; landmark description is ‘near the bridge’.”.

Attribution and uncertainty matter in emergencies. Use emergency authority procedures for verification. An editor can test this pair by asking what a new colleague would believe after reading each version without seeing the source. The weaker version expands, narrows or changes the proposition; the better one preserves the original evidence boundary. Treat any unresolved inference as a query, not as silently polished copy. This keeps the example useful across languages without pretending every grammar has the same sentence structure.

Case 28: Rounding after transformation

Record as received: “Transformation output 12.345678; reporting rule 4 decimals.” Overconfident version: “Original observation was 12.3457.”. Evidence-preserving version: “Converted output reported as 12.3457 after rounding; original observation retained separately.”.

Post-processing precision is not original sensor precision. Notice the difference between stating a fact, recording somebody’s claim and authorising an action. Document transformation and rounding rule. A translation should let readers tell which of those functions the source performs. If further information is needed, specify the missing field or person rather than inserting a plausible value. This is especially important when the same record is reused in public reports, internal dashboards and contractual communication.

Part III: an operational translation and review workflow

1. Intake and permissions

Record the requester, source owner, document purpose, audience, confidentiality classification, permitted file-sharing method and authorised reviewer. A competent translator must know which files can be processed and who can answer a question. A title and a deadline are not enough. When a document is sensitive, do not paste it into an unapproved online service; agree the handling route before starting.

2. Version capture

Copy the complete source with its stable identifier and date. Note any amendment, correction, superseded file or unresolved change request. Preserve a read-only copy. If the source arrives as screenshots, ask whether the original structured fields are available: image extraction can lose minus signs, decimal separators, italics, rows, footnotes and zero-padding.

3. Reader question

Write the question the reader needs answered in plain English, then map every sentence required to answer it to a source line or field. Separate primary facts from background explanation. Where the source cannot answer the question, state the gap, its owner and the consequence of not resolving it. This prevents the article or operational translation from becoming an attractive but ungrounded narrative.

4. Terminology decisions

Construct a small glossary of the domain’s decision-critical terms, not merely its longest words. Give each term a source field, intended meaning, preferred translation, forbidden near-synonyms and a reviewer. Avoid translating immutable codes, identifiers, dates or structured-data keys. For ambiguous terms, write a question instead of improvising a final answer.

5. Numeric and structural checks

Check units, leading zeros, sign, separator, range endpoints, percentages, clocks, timezones, uncertainty values, conditional words, reference identifiers and schema field names. A text may be grammatically excellent and still be unusable if its numbers have shifted. Make two passes: one for human meaning and a separate machine-like pass for character-exact data.

6. Role and decision audit

Highlight every verb indicating request, approval, observation, completion, test, rejection, escalation, release or acceptance. Verify each actor’s authority and each statement’s evidentiary status. Ask whether the target-language reader would believe the process had moved one stage further than the source actually records. That is often the most consequential translation error.

7. Subject expert review

Have a reviewer familiar with the domain inspect technical claims and exceptions, while an editor checks coherence and accessibility. Their jobs are different. The expert can confirm what the document means operationally; the editor can make the explanation easy to follow. Neither should add a new factual claim without recording its source.

8. Reader test

Give a new reader three questions: what happened, what remains uncertain and what action is authorised? If the answers differ from the original record, revise the translation. Include realistic cases with missing data, conflicting statuses and failed approvals, not only easy examples. That test reveals whether the final text teaches the correct decision rather than merely sounding fluent.

9. Sign-off and retention

Store the final version beside its source, correction log, reviewer identity, date and unresolved queries. State whether it is a reference translation, working draft or authorised release. Keep later updates as new revisions instead of silently overwriting the evidentiary history. Readers should be able to determine which version applied to their decision.

10. Correct mistakes transparently

If a material error is found after distribution, identify affected readers and decisions, issue a versioned correction and preserve the previous file for audit according to the applicable retention policy. Distinguish an editorial spelling correction from a changed number, instruction, approval or reported result. Never conceal a substantive correction inside an unannounced cosmetic edit.

Part IV: difficult editorial disputes and how to resolve them

Editorial decision 1: A smooth translation changes the decision

When an editor replaces a narrow status word with an encouraging phrase, compare the action a reader would take under each sentence. If the actions differ, the edit is substantive, not stylistic. Prefer the version that preserves the source’s evidence and record the reason the smoother proposal was rejected.

Apply this decision to geographic point-location records by checking the specific document’s identifiers, version and authorised use. A reviewer should mark the sentence as supported, unsupported or pending clarification rather than giving a single subjective ‘sounds right’ score. The final text should make visible which part comes from the original record and which part is teaching context. If a dispute remains unresolved, retain a narrower wording and name the outstanding question; do not silently convert editorial preference into technical evidence.

Editorial decision 2: A missing value looks obvious

A missing field can often be guessed from previous reports or common industry practice. Do not insert the guess into a translated result. Mark the field as not provided, raise a question to the owner and, if the publication format allows, explain in a clearly labelled note why the information would matter.

Editorial decision 3: Two authoritative-looking sources disagree

The standard’s public title, the client’s procedure and a vendor’s guide may refer to similar terms yet govern different activities. Identify the precise question, edition and authority of each source. A translator must not resolve a legal or technical conflict by quietly choosing whichever sentence reads more naturally.

Editorial decision 4: An identifier sounds strange in the target language

If the strange string is a product ID, sample number, coordinate token, account key or workflow code, do not beautify it. Keep the identifier intact and add an accessible adjacent explanation. This allows the reader to search, audit and compare the record without losing the link to the original.

Editorial decision 5: The source seems to make an impossible claim

Translators should flag contradictory totals, impossible angles, unverified results, implausible versions or missing approval signatures. They should not silently repair the source. Record the suspected issue, quote the affected field briefly in the internal review note and obtain the source owner’s correction.

Editorial decision 6: A published claim looks stronger than its evidence

Marketing, public relations and internal management language can present requests, assumptions or preliminary findings as certainty. Attribute the statement accurately, state its evidentiary scope and do not invent certifications, diagnoses, safety assurances or regulatory approvals in translation.

Editorial decision 7: The target audience needs more context

Add an explicitly identified explanatory paragraph when readers would otherwise misunderstand a specialised distinction. Do not place new explanation inside quotation marks or unlabelled data fields. The goal is understanding, not rewriting the underlying evidence.

Editorial decision 8: The translation will be reused in a machine

Separate a human-facing label from machine-readable data. Test the field mapping, parser behaviour, reserved characters, locale conventions and output validation. If the application requires changes to syntax, treat those as a controlled data transformation requiring its own test and sign-off.

Frequently asked questions

Is the first value always latitude?

No. Follow the declared schema and CRS axis conventions. Human-facing lists often show latitude then longitude, but machine records are not all organised that way.

Can I translate a negative sign into S or W?

Only when the axis and sign convention are known. Preserve the original numeric sign in machine records and explain direction in a separate human-readable display.

What does a missing CRS mean?

You cannot reliably treat a numeric pair as a specific ground location. Request the reference-system definition instead of assuming a popular one.

Are more decimal places better?

They increase numerical granularity, not demonstrated accuracy. Retain the stated measurement method and uncertainty.

What is the difference between a coordinate and a place name?

Coordinates express a numerical location within a reference framework; a place name is a linguistic label that may cover a wider area or change over time.

Should heights be converted automatically?

Convert units only with defined source and target units, and preserve the vertical reference and method. Never equate local datum with sea level by guesswork.

Can translated coordinates be used for navigation immediately?

Not until the location, CRS, axis order, time, precision and intended safety context are verified by the competent user or authority.

Does ISO 6709 cover a whole GIS dataset?

Its public description is about text representation of a single point, and explicitly distinguishes this from files containing multiple points sharing a reference-system identifier.

A final practical test before using the translation

A good result lets a reader answer five questions with the same meaning in every language: What is the exact object or sample? What is the observed state? Which source and version support it? What is still unknown? Who may approve the next step? In geographic point-location records, these questions are more useful than a long list of impressive technical adjectives. If one answer differs from the source after translation, the document is not yet ready for use.

Read the first page again as if you were seeing this subject for the first time. Put the key outcome early, distinguish the cause from the evidence, and define specialist vocabulary at the point of use. Then read it as an auditor: are quantities, units, dates, people, versions and exclusions still intact? Finally read it as an affected reader: does the explanation make an action possible without implying permission or certainty that the source does not grant?