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
In writing the explainer for this, it occurs to me that <input rel="..."> is a bit weird, and certainly not found in HTML (?). It would be less weird if the location event that is being serialized through the <input> actually identified what it was related to i.e. the tile, the map extent, or even the pixel.
To do that, I'm not sure, but I think the <link rel="tile" ...> or <link rel="query" ...> would have to add that information to the event when generating it. It seems possible for a <link rel="image or tile"> but <link rel="query"...> can carry parameters that are tile-specific or extent-specific (WMTS vs WMS, respectively).
Anyway, leaving this here if anyone has some ideas, they would be welcome.
The text was updated successfully, but these errors were encountered:
In writing the explainer for this, it occurs to me that
<input rel="...">
is a bit weird, and certainly not found in HTML (?). It would be less weird if the location event that is being serialized through the<input>
actually identified what it was related to i.e. the tile, the map extent, or even the pixel.To do that, I'm not sure, but I think the
<link rel="tile" ...>
or<link rel="query" ...>
would have to add that information to the event when generating it. It seems possible for a<link rel="image or tile">
but<link rel="query"...>
can carry parameters that are tile-specific or extent-specific (WMTS vs WMS, respectively).Anyway, leaving this here if anyone has some ideas, they would be welcome.
The text was updated successfully, but these errors were encountered: