You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Likely not related to the hidden layer problem, but the query that gets executed indicates that there are two features being returned, but there is only one in fact. The actually query link template is a bit fake in this example, because it is hard-coded to return the legend graphic from each of the datacube layers as an entry in a table in a map-feature's map-properties. That's probably what it is counting as two features tbd.
Possibly a bug, or perhaps related to the fact that the mapml document is not returned as text/mapml from github, just as application/octet-stream (or similar)
Likely not related to the
hidden
layer problem, but the query that gets executed indicates that there are two features being returned, but there is only one in fact. The actually query link template is a bit fake in this example, because it is hard-coded to return the legend graphic from each of the datacube layers as an entry in a table in a map-feature's map-properties. That's probably what it is counting as two features tbd.Originally posted by @prushforth in #909 (comment)
The text was updated successfully, but these errors were encountered: