Maps display true 0,0 lat/long instead of treating 0,0 as no change in position

This isn't only an issue with MP, but with QGC as well. The MAVLINK command parameter specs say that using 0,0 as latitude, longitude means "no change in latitude/longitude position." However, the mapping displays for these GCSes treat 0,0 as a physical global position, completely distorting flight path maps and distance calculations. Is this a bug? It doesn't seem like a feature!

Start by reproducing the issue in Mission Planner's mapping display and tracing how MAVLINK command parameters are interpreted. Compare the handling of latitude/longitude 0,0 with the MAVLINK specification; done means 0,0 is treated as no position change and no longer distorts flight paths or distance calculations.

Written by the indexing model from the issue text.