Closed loraine-gueguen closed 5 years ago
Ah, just had the same problem today, I ended up removing the start/stop attributes from GFF. I guess it's the tabix indexing that interprets badly the start attributes
Yes I think so
technically this is due to the jbrowse feature model. JBrowse has the "SimpleFeature" type that just does
feature.get('start') to refer to the column 3, and then it ends up overwriting that with the attribute named start
We would have to emulate the behavior of NCLIst e.g. renaming it 'start2' to make it work
added my proposed fix to the dev branch. hope that is acceptable!
We have such a GFF3 file:
case 1- In GFF3Tabix mode, this GFF3 results in wrong coordinates for the mRNA:
case 2- Removing the "start" and "stop" attributes in last column results in right coordinates:
case 3- In NCList mode, keeping the original GFF3, results in right coordinates, with a "start2" attribute displayed in the popup window:
I guess, in case 1, the "start" attribute in last column of the GFF3 is used as the start coordinate for the feature sequence whereas it should not.