-
Notifications
You must be signed in to change notification settings - Fork 2
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
Data format documentation #82
Comments
Right now the only format fully supported is the old cmap tabular format, which was a choice mainly due to availability and ease of support. After the current round of bug fixes and UI tweaks (with the goal to be able to call it moved out of alpha and into beta) I do have plans on revisiting the data loader and expanding file format support. Now is a great time to be requesting additional file formats for support. |
My 2 cents: FPC is a deprecated format and not worth supporting. We would want support for a postgresql database using Chado formatted maps, which would be stored according to the map module presumably. We could code the database interface on our end to interact with Chado to supply cmap-js with, for example, JSON formatted data. So to clarify, we would want to supply cmap-js with a URL query, which we would code in Tripal to return a JSON object with data cmap-js can read. Edit: I guess alternatively we just return a cmap file... |
agreed, I think it would be good for us (including interested adopters) to spend some time specifying a JSON schema for service provider implementations (chado-backed or otherwise) to target. That said, for use cases involving users reading local data for comparison with maps published on sites we will still want to have a few flatfile options based on software for QTL/GWAS mapping (or similar) that is currently being used by the community. But I agree that FPC is probably not being widely used these days, and could be converted into a cmap format without too much effort (IIRC, the old cmap used to be able to handle FPC maps though maybe there was a conversion step involved). |
@sammyjava you will probably want to participate in the discussion of this from the intermine angle too (which must have been in the back of my mind when I wrote: "chado-backed or otherwise") |
I prefer JSON simply because that's what other InterMine displayers use. But otherwise I'm not too particular, I can presumably hack the appropriate file format. |
FYI @awilkey It came up in the May 24th LegumeFed meeting (short discussion about cmap-js) about the request for a spec for the allowed json format(s). |
If there's no other widely-used JSON map data format, a JSON representation of the cmap tab-delimited file format may at least be straightforward to support in cmap-js. |
Hello all,
We recently started using CMap-js (great job btw!), and were wondering about what formats the software accepts. Any information on how to generate data files is also very much appreciated.
We currently have a file in FPC format that doesn't seem to work with the current implementation: https://hardwoodgenomics.org/sites/default/files/physical_map/Chinese_Chestnut_FPC_v4.fpc
Thanks!
The text was updated successfully, but these errors were encountered: