From 704cd03d968de630b3f350f4db8dde9269dfb0f8 Mon Sep 17 00:00:00 2001 From: Greg Gianforcaro Date: Mon, 17 Jul 2017 17:53:39 -0400 Subject: [PATCH] Fix Graticule use of incorrect min/maxLon values Appears to have just been a typeo, using the minLon_, maxLon_ member variables rather than the function parameters provided. This was creating very wide lines of parallel which were sometimes very slow in Chrome. --- src/ol/graticule.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ol/graticule.js b/src/ol/graticule.js index 53ce851ad2..a371528f2c 100644 --- a/src/ol/graticule.js +++ b/src/ol/graticule.js @@ -519,7 +519,7 @@ ol.Graticule.prototype.getMeridians = function() { ol.Graticule.prototype.getParallel_ = function(lat, minLon, maxLon, squaredTolerance, index) { var flatCoordinates = ol.geom.flat.geodesic.parallel(lat, - this.minLon_, this.maxLon_, this.projection_, squaredTolerance); + minLon, maxLon, this.projection_, squaredTolerance); var lineString = this.parallels_[index] !== undefined ? this.parallels_[index] : new ol.geom.LineString(null); lineString.setFlatCoordinates(ol.geom.GeometryLayout.XY, flatCoordinates);