For an unknown reason, now and then "POINT(NaN, NaN)" WKT vectors get pushed into the saved geocoverage strings on NeatlineDataRecords. On some systems, the presence of these geometry-less vectors breaks the zoom bounds calculation.
Fix needs to either (a) stop the empty vectors from getting committed in the first place or (b) block the strings at save. Preferably the former.
For an unknown reason, now and then "POINT(NaN, NaN)" WKT vectors get pushed into the saved geocoverage strings on NeatlineDataRecords. On some systems, the presence of these geometry-less vectors breaks the zoom bounds calculation.
Fix needs to either (a) stop the empty vectors from getting committed in the first place or (b) block the strings at save. Preferably the former.