> But now all the complex math is hidden away behind abstractions, and the extra computation to do everything in WGS-84 space is insignificant... UTF-8 is now worth it over encoding things using codepages.
There is a reason for having GIS professionals. WGS-84 is not nearly accurate enough for many purposes. Good enough to find your home, not good enough for precision surveys. In my country to get sub-metre (cm) precision using NZGT2000 is necessary.
WGS-84 also has no deformation component. The tectonic plates moves, in parts of my country movement is 5cm/year,and so a WGS-84 coordinate taken at one point in time won't precisely point to the save bit of dirt at a later time. Other geographic coordinate systems can take this into account.
Nobody would use UTF-8 if every 1000th character was lost.
With a dual band survey grade receiver, WGS84 coordinates can be derived to 2cm accuracy in the vertical [0] and even better in the horizontal.
WGS 84 is a time dependent datum - each addition to the ensemble is known as a realization. The software used to convert across time and reference frames is called HTDP [1]. This can also be done for the vertical using VDatum, which wraps HTDP.
The confusion around this issue usually has to do with how analysts actually handle coordinate information in software. For example ESRI, arguably the dominant GIS, does not have time dependent conversion capability. In the US there is also a false equivalence that NAD83 == WGS84. Looks like NZ has a similar issue [2].
Developers also have to deal with this issue, since web mercator and the tiling scheme were designed for convenience and not sub meter accuracy.
> With a dual band survey grade receiver, WGS84 coordinates can be derived to 2cm accuracy in the vertical [0] and even better in the horizontal.
Accuracy or precision? The issue is accuracy, not precision.
> Developers also have to deal with this issue, since web mercator and the tiling scheme were designed for convenience and not sub meter accuracy.
This is a projection problem. All projections are essentially wrong, and tradeoffs need to be made (eg. you can't flatten an orange on a desk without distorting some parts of it) . Unfortunately users don't understand this which is why people get excited when they discover America is smaller, and Africa larger, than they thought. Ideally when zooming into a country a more suitable projection would be used, but at the end of the day it doesn't matter much for consumers.
I think software developers don't give GIS developers enough credit. Software devs will endless debate and be critical of floating point issues, but also not consult with a GIS professional when doing spatial work. People don't know what they don't know.
There is a reason for having GIS professionals. WGS-84 is not nearly accurate enough for many purposes. Good enough to find your home, not good enough for precision surveys. In my country to get sub-metre (cm) precision using NZGT2000 is necessary.
WGS-84 also has no deformation component. The tectonic plates moves, in parts of my country movement is 5cm/year,and so a WGS-84 coordinate taken at one point in time won't precisely point to the save bit of dirt at a later time. Other geographic coordinate systems can take this into account.
Nobody would use UTF-8 if every 1000th character was lost.