Coordinates now saved with more decimals

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Franky

    (@liedekef)

    If facebook provides more decimals, then this will happen. Nothing changed on my side.

    Plugin Author mlplus

    (@mlplus)

    Yes something must have changed. It’s not only facebook locations. Before creating a location you saved 4 decimals but now more!

    Plugin Author mlplus

    (@mlplus)

    If I input more decimals the value was before truncated to 4 decimals

    Plugin Author mlplus

    (@mlplus)

    But this might be related to EME not the sync part

    Plugin Author Franky

    (@liedekef)

    Before I was storing it in mysql as float, which (according to the doc on mysql):

    FLOAT[(M[,D])] [ZEROFILL] stores floating point numbers in the range of -3.402823466E+38 to -1.175494351E-38 and 1.175494351E-38 to 3.402823466E+38. If precision isn’t specified, or <= 24, it’s SINGLE precision, otherwise FLOAT is DOUBLE precision. When specified alone, precision can range from 0 to 53. If the scale is defined, too, precision may be up to 255, scale up to 253.

    Because of comparison issues, I now store the values as strings so mysql never touches them. Maybe your mysql cuts basic floating points at 4 decimals (btw: I have older locations with 5 decimals). Using strings this is a thing of the past and all coordinates are kept as they come in.
    Maybe that has the effect you’re seeing (that change was done in eme version 2.0.25 (from 26 March).

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Coordinates now saved with more decimals’ is closed to new replies.