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

support for importing Menpo Mesh JSON files (.mjson) #390

Merged
merged 2 commits into from Jul 9, 2014

Conversation

Projects
None yet
2 participants
@jabooth
Member

jabooth commented Jul 8, 2014

All our TriMesh classes already have tojson() methods that return a very simple dictionary format suitable for JSON serialisation. This is useful for the landmarkerio-server, which needs to be able to communicate meshes to landmarkerio clients.

This simply adds support for ingesting these files to menpo.io, so these meshes can be used. As JSON is a very popular format we tweak the file extension to .mjson to avoid ambiguity. In the future we should probably move landmarks from the current .json to .ljson to avoid clashes going forwards.

jabooth added some commits Jul 8, 2014

@jabooth

This comment has been minimized.

Member

jabooth commented Jul 9, 2014

Note that I have made the update of the landmark file from .json to .ljson.

@patricksnape

This comment has been minimized.

Contributor

patricksnape commented Jul 9, 2014

OK +1

jabooth added a commit that referenced this pull request Jul 9, 2014

Merge pull request #390 from jabooth/mjson
support for importing Menpo Mesh JSON files (.mjson)

@jabooth jabooth merged commit 59bfd56 into menpo:master Jul 9, 2014

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details

@jabooth jabooth deleted the jabooth:mjson branch Jul 9, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment