C++: routes and connectedRoutes are written to the DB with 17 & 15 sig figs respectively.
Meanwhile, Python seems to keep a pretty consistent 16 with its str(double).
Could %.16g be the magic bullet?
Edit: Nope. %.17g then?
egrep -c '[1-9][0-9.]{17}'~/ytm/DataProcessing/siteupdate/python-teresco/TravelMapping.sql
414823...Nope again. Lat / long coords want 15 sig figs. Any more and we can get lots of 0s followed by another digit appended after the real value.
Looks like I was on the right track originally - 15 sig figs in some cases, 17 in others.
C++:
routesandconnectedRoutesare written to the DB with 17 & 15 sig figs respectively.Meanwhile, Python seems to keep a pretty consistent 16 with its
str(double).Could
%.16gbe the magic bullet?Edit: Nope.
%.17gthen?...Nope again. Lat / long coords want 15 sig figs. Any more and we can get lots of 0s followed by another digit appended after the real value.
Looks like I was on the right track originally - 15 sig figs in some cases, 17 in others.
This can get squashed into the ongoing changes on the "r4" branch.
Would it help in practice? (No. But anyway.)