…nder

…do intersection with simple features (sf)

…, cc @tim-salabim

… editable spot for feature attributes

…non-standard styling as begin rewrite

… to use ControlStore

…trol

…/proj4leaflet

…working

…with layerControl (viewRGB); cc @tim-salabim

The default zIndex for TileLayer and GridLayer is now 1. In
Leaflet 0.7 it was null. In our R code, the default was NULL,
which we pass to the Leaflet code. Therefore, in Leaflet 1.x
we actually override the default zIndex of 1 and change it to
"auto".

However, for addRaster, we've never allowed the zIndex to be
set, so we don't override the new default zIndex of 1. So we
end up with a tile layer with zIndex "auto" and a grid layer
with a zIndex of 1. For "stacking context" reasons that I do
not understand, auto always renders in front of non-auto.

Setting the default for tiles to 1 fixes the problem.

The getImageData(callback) function as previously written
would invoke the callback immediately if image data was
already loaded, or asynchronously if image data was not.
(I knew this was weird so I noted this in the function's
comment.) This turns out to be a problem with Leaflet 1.x
because it expects createTile's callback (done) function
to only be invoked after createTile has returned. If done
is called too soon, then it's ignored, because done first
checks the GridLayer's tile cache to see if the tile that's
done is even still wanted. Since createTile hasn't returned
the tile isn't in the cache yet, and done becomes a no-op.