Open caseycesari opened 7 years ago
This seems more like a configuration error than a bug.
This problem is essentially the same as using an incorrect URL or layer name. If the config has an invalid value, we won't be able to find that layer in the service.
Fixing the configuration or specifying a layer ID (Ref #55) should resolve the problem.
We should also verify if this is a real issue:
I think setting includeAllLayers: "true" for Total Predicted Species Richness prevented subsequent nested layers from drawing (?)
Encountered while debugging #57
To reproduce:
layers.json
.Total Predicted Species Richness
does not have any children and fails to load because of this check.layer.hasChildren
returns true, butserviceLayer.subLayerIds
is empty.