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
A layer can have a single or a few feature(s) in it, and sometimes it would be developer-friendly to not have to specify the projection via a map-meta element, or even as is sometimes seen (MapServer?) via the text/mapml MIME type projection parameter. It would be developer friendly to allow that layer to just assume that the projection is compatible with the <mapml-viewer projection="value"...> and try that. If it renders, that's good, otherwise it might become a disabled (inert) layer until DOM changes occur that make it not disabled.
Edit: it might not work, but it's worth a try.
The text was updated successfully, but these errors were encountered:
A layer can have a single or a few feature(s) in it, and sometimes it would be developer-friendly to not have to specify the projection via a map-meta element, or even as is sometimes seen (MapServer?) via the text/mapml MIME type
projection
parameter. It would be developer friendly to allow that layer to just assume that the projection is compatible with the<mapml-viewer projection="value"...>
and try that. If it renders, that's good, otherwise it might become a disabled (inert) layer until DOM changes occur that make it not disabled.Edit: it might not work, but it's worth a try.
The text was updated successfully, but these errors were encountered: