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
Currently the HexJSON format does not specify where the origin for the offset coordinate system is, and the documentation assumes that it will be at the bottom left, with the row number increasing from bottom to top).
However, many packages follow the offset coordinate system set out on the Red Blob Games blog, which places the origin at the top left, with r values increasing from top to bottom.
Could we add an 'origin' property into the specification, supporting the values "topLeft", "bottomLeft", "topRight", "bottomRight"?
This way, the file can specify which offset coordinate system has been used to compute the q and r values, and we can avoid issues where hexmaps are rendered the wrong way around when using a renderer that defaults to a different origin?
The text was updated successfully, but these errors were encountered:
Currently the HexJSON format does not specify where the origin for the offset coordinate system is, and the documentation assumes that it will be at the bottom left, with the row number increasing from bottom to top).
However, many packages follow the offset coordinate system set out on the Red Blob Games blog, which places the origin at the top left, with r values increasing from top to bottom.
Could we add an 'origin' property into the specification, supporting the values "topLeft", "bottomLeft", "topRight", "bottomRight"?
This way, the file can specify which offset coordinate system has been used to compute the q and r values, and we can avoid issues where hexmaps are rendered the wrong way around when using a renderer that defaults to a different origin?
The text was updated successfully, but these errors were encountered: