Lat/long in first data set and extension data set makes things go sideways in Bricks API

[esjewett]

The issue is that the scope.descriptiveDim is set to the first latlong type field and is then pulled into the layer descriptiveDim in the import. We need to look up the correct descriptiveDim during the import, I guess.