Load custom track via URL with non-default position
7 views
Skip to first unread message
Thomas Sibley
unread,
Jul 19, 2016, 4:52:15 PM7/19/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to gen...@soe.ucsc.edu
Hi,
I’m constructing URLs to load a custom track. The track contains a “browser position” line to set a default position. This works great!
However, any “position” parameter in the URL seems to be ignored, so I can’t construct a URL which loads the track to a non-default position. For example:
Is the current behavior the desired one, or is it supposed to work as I expect?
Cheers,
Thomas
Luvina Guruvadoo
unread,
Jul 19, 2016, 5:55:48 PM7/19/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Thomas Sibley, gen...@soe.ucsc.edu
Hello Thomas,
Thank you for your question. You are correct; if the "position" parameter is defined in the URL, the browser will open to the specified location. However, if you take a look at the example custom track you provided in your email (http://genome.ucsc.edu/goldenPath/help/test.bed), the browser position has already been defined in the first line: browser position chr22:20100000-20140000. This overrides the URL parameter. If you upload the custom track without the browser position line and include the position parameter in your URL (such as chrX), the browser opens to the desired location. I hope this helps clarify things.
If you have any further questions, please reply to
gen...@soe.ucsc.edu. All messages sent to that address are
archived on a publicly-accessible forum. If your question includes
sensitive data, you may send it instead to
genom...@soe.ucsc.edu.