Edit - Geographic Information Systems Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

I cannot advocate this method high enough. One might be able to figure out the zone based on ballpark figures of eastings and northings but there are so many projections that are similar but not quite (e.g. every time one projection is superceded by another like GDA94 -> GDA2020). A guess will always be just a guess and one cannot make accurate inferences based on a guess. Spatial data that can't be geolocated is often better discarded.
– Paul Childs
Commented Aug 19, 2021 at 4:23

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »