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
I am writing a MapML explainer, and I while I'm bothered by the profusion of attributes on <input type="location"...>, I'm even slightly more concerned that too many <input> types is worse.
So, although zoom isn't strictly speaking an axis, could it be treated like one by <input type="location">, or more generally, in the notion of location in Web maps altogether? It is clear that scale is an integral part of maps, so maybe making zoom (scale's proxy) part of location would be possible. I don't think it is too much of a stretch given the tight integration of zoom in the concept of Tiled Coordinate Reference Systems.
If the location event carried more properties, such as zoom, and even width and height, we could eliminate <input>s for those properties.
The text was updated successfully, but these errors were encountered:
prushforth
changed the title
Could / should <input type="zoom" ...> be replaced bye <input type="location" axis="zoom" ...>
Could / should <input type="zoom" ...> be replaced by <input type="location" axis="zoom" ...>
Dec 29, 2019
I am writing a MapML explainer, and I while I'm bothered by the profusion of attributes on
<input type="location"...>
, I'm even slightly more concerned that too many<input>
types is worse.So, although zoom isn't strictly speaking an axis, could it be treated like one by
<input type="location">
, or more generally, in the notion of location in Web maps altogether? It is clear that scale is an integral part of maps, so maybe making zoom (scale's proxy) part of location would be possible. I don't think it is too much of a stretch given the tight integration of zoom in the concept of Tiled Coordinate Reference Systems.If the location event carried more properties, such as zoom, and even width and height, we could eliminate
<input>
s for those properties.The text was updated successfully, but these errors were encountered: