View Configs


UID stands for unique identifier. Every view and track in the higlass view config has a UID. If it’s not specified in the viewconfig it’s randomly generated by the client when the view is created.

initialXDomain and initialYDomain

The fields contain the initial coordinates which are displayed when HiGlass first loads the viewconfig. If the initialYDomain is not present, it is set to equal the initialXDomain. If that isn’t present either, both are assigned values of [0,1]].

    views: [
              "uid": "AhI0wMP6ScybnFp6BmLuPQ",
              "initialXDomain": [
              "initialYDomain": [
            "genomePositionSearchBox": {
                "autocompleteServer": "",
                "autocompleteId": "OHJakQICQD6gTD7skx4EWA",
                "chromInfoServer": "",
                "chromInfoId": "hg19",
                "visible": true


The field trackSourceServers at the root level of the viewconf tells higlass where it can find tracks to load. If you have a local instance running, then http://localhost/api/v1 should be included. Our public instance at also provides access to a number of public datasets.

  "trackSourceServers": [


The exportViewUrl field in the viewconf specifies which server should be used to store exported viewconfs. This server stores exported viewconfs in its database, assigns them a uid, and makes them accessible through its API at /api/v1/viewconfs/uid/.

    "exportViewUrl": "/api/v1/viewconfs",


Tracks can be placed into four distinct areas: top, bottom, left, right or center. The location of the track determines what type of data can be shown in it. Center tracks are used to show data that can be zoomed along two axes. Horizontal (top, bottom) and vertical (left, right) are used to show data that can be zoomed along a single axis.

Each set of tracks is placed within a view.

  "views": [
      "tracks": {
        "top": [],
        "left": [],
        "center": [],
        "bottom": [],
        "right": []