Scale
Coordinates need an order as well as numbers
Two numbers can look precise while pointing to the wrong place. The problem is sometimes their order rather than their arithmetic. A coordinate pair may follow a named grid convention, a latitude and longitude convention, or the input order expected by a particular application. Writing the numbers without those names removes the information needed to interpret them. Before copying a location, read the labels around the original pair. Precision is useful only after the coordinate system, units, and order have been established. A long string of digits cannot repair an unnamed relationship.
Begin with a clearly labelled example from the map you are using. If the margins show a grid, identify its published name and the instructions supplied for reading it. If the display reports latitude and longitude, look for the labels and the format: degrees alone, degrees and minutes, or another stated arrangement. Do not quietly convert between formats by moving a decimal point. A decimal fraction of a degree is not the same as a count of minutes written after that degree. Copy the complete format first, then use an appropriate conversion method only when one is actually needed.
Read the boxes around an input
A search application may provide separate fields, a single search box, or several supported formats. Its examples matter. One application may accept latitude followed by longitude while a data file elsewhere lists longitude first. Avoid assuming that the order used in one context governs every other context. Read the current interface's instructions and retain the labels in your own note. For a simple desk check, use a public, well identified town centre or landmark rather than a sensitive private address. Compare the returned broad location with the place expected.
Direction signs also carry meaning. A coordinate with a negative longitude and a coordinate with the same unsigned number can lie in different parts of the world. Some formats use compass letters instead of signs. Do not add both conventions casually or remove them because the remaining digits appear cleaner. Preserve the publisher's notation. If a copied coordinate unexpectedly lands across an ocean, stop and check the system, order, and signs before adding further digits. More numerical precision makes a mistaken location more precisely mistaken; it does not make the interpretation correct.
A grid reference belongs to its grid
Printed grid references can include letters, zone information, or other identifiers that a reader is tempted to leave out. Those parts may be essential to distinguishing one area from another. Record the grid name and the full reference as supplied, using the map's own reading instructions. A pair of east and north values without the appropriate system can be ambiguous. This is especially easy to overlook when two maps both display square grids but cover different regions. The shared appearance of squares is not evidence that their coordinate labels are interchangeable.
A reference also has a resolution. Adding digits should follow the information available in the source and the method used to read it. If a point was estimated from a small printed map, a copied coordinate with many decimal places can imply confidence the observation did not support. Keep a note about how the position was obtained: a labelled feature on a particular edition, an approximate grid reading, or an application's supplied location. That note helps a later reader distinguish the representation's numerical format from the accuracy of the original observation.
Complete a round trip
A practical check is to copy the complete labelled coordinate into the intended destination, then compare the returned location with the original map. Look at the surrounding place names, the broad region, and the relationship to a recognisable public feature. This is a compatibility check between two representations, not independent confirmation of an exact ground position. If the result disagrees, retain the original note while investigating. Do not overwrite it with the application's output and lose the evidence that would help explain the mismatch.
For a shared note, write the coordinate system or format, the ordered labels, the units, and the source. A compact example might say that the first value is latitude in decimal degrees and the second is longitude in decimal degrees, with the signs preserved from the source. The exact numbers are only part of the record. Keeping the interpretive information beside them makes an ordinary location note easier to use, easier to question, and much less dependent on the reader remembering which application produced it.
Keep reading