Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created version 1.0.0 of HexJSON #2

Open
wants to merge 2 commits into
base: gh-pages
Choose a base branch
from

Conversation

ronaldkunenborg
Copy link

I crated a new version of the specification for HexJSON. This version includes semantic version numbering and a more complete layout description. Using these additions the layout of the map should be unambiguous. I am proposing this extension as a precursor to modifications to the relevant code in d3-hexJSON and hexmaps. Feel free to comment on this proposal.

I created a different branch given the possible impact. However, since this is my first pull request ever it's highly likely that isnt done completely right :). So if you want this done in another way please contact me. My mailadres is on my website.

@ronaldkunenborg
Copy link
Author

Hmm... and a comment: I think the maxCoordinates might better be off when it's the minCoordinates, as this is an intuitive natural fit for the origin with most layouts. For axial layouts it still provides the same benefit as maxCoordinates. Anyway, please let me know what you think. Otherwise I'll just go on with adding some things to d3-hexjson.

…e origin in most cases. Changed version to use only two levels instead of three.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant