Max. GPS coodinates size in search
I've noticed that if I right-click in Google Maps to select a GPS reference I can't paste directly into ABRP (browser) unless I reduce its size. This is sometimes useful to pin down site entrances as the base maps used by Open Street Map can be slightly out depending on where the source data came from.
For the GPS pasting query:
e.g. If I select the centre of Westminster Bridge in London on Google Maps it gives me this GPS ref: 51.50082813878995, -0.12202284524924678
If I try to paste that into ABRP it doesn't resolve (I assume because it's too long), but if I put 51.500, -0.122 it resolves to the middle of the Thames. I need to add an extra two characters to get there... 51.50085, -0.12202 seems OK but I still have to manually adjust the coordinates by deleting half the string.
Is there a hard-coded limit to how many decimal places ABRP can cope with compared to Google's native output?
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments4
Johannes ABRP
Feb 6
Hi Rob, thanks for reporting your finding, the issue has been resolved. This is done in the backend, meaning it has instant effect. Google’s resolution is truncated, precisely as you suggested, but you will have to answer to the quarks trying to navigate with ABRP.
Enjoy your ride!
Bo (ABRP)
Feb 4
Good catch! Our backen for some reason fails with too high precision - we will look into that and fix it.
Rob
Feb 4
That’s great, thank you for the update. I’ve only been using ABRP for a week and I’m very impressed so far.
Rob
Feb 3
Clearly 16 decimals is massive overkill from Google (it’s less than 1/10 the diameter of a hydrogen atom) - perhaps an option to paste GPS which auto-truncates the string down to 1m resolution (5 decimals = xx.xxxxx)?