Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: If a layer has dynamicExtent variables and uses a bounding box, but returns a list of geojson, it won't render #538

Open
tamarmot opened this issue May 2, 2024 · 0 comments
Labels
bug Something isn't working outdated? This needs to be checked for relevancy

Comments

@tamarmot
Copy link

tamarmot commented May 2, 2024

Checked for duplicates

Yes - I've already checked

Describe the bug

I created a new layer that had variables of
{
"dynamicExtent": true,
"dynamicExtentMoveThreshold": "200000/z"
}

and a url that included a bbox.

I created a similar layer without those variables.
The urls returned almost identical results, which was a list of FeatureCollections. The one without the dynamicExtent worked, the one with dynamicExtent gave an error in the console:

globeLithoLayerHelper: function() {
var e = (0,
R.Z)((0,
I.Z)().mark((function e(t, i) {
return (0,
I.Z)().wrap((function(e) {
for (; ; )
switch (e.prev = e.next) {
case 0:
if (!ue.Globe_) {
e.next = 7;
break
}
if (!ue.layers.on[t.name]) {
e.next = 7;
break
}

where t was not defined.

What did you expect?

I expected the layers to work in the same way, to render the geojson from a list of feature collections.

Reproducible steps

1. have a url that returns a list of feature collections
2. create a layer with dynamicExtent that returns the contents of that url
3. it should render

Environment

- Version of this software develop built 04/25/24
@tamarmot tamarmot added the bug Something isn't working label May 2, 2024
@tariqksoliman tariqksoliman added the outdated? This needs to be checked for relevancy label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working outdated? This needs to be checked for relevancy
Projects
None yet
Development

No branches or pull requests

2 participants