This page contains various data dumps from iPath databases, which should give you better understanding of how various data is projected onto the maps. If you notice differences in how your data maps to different iPath versions, check the files below for possible clues, or contact us.
|Data dump file||iPath version||Description|
|cog_from_string7_to_ko20080319_filtered_005.txt.gz||v 1||mapping of COGs to KOs|
|ko20080403.gz||v 1||annotation for KOs used in iPath 1|
|module_20071108.gz||v 1||annotation for KEGG modules used in iPath 1|
|COG.mappings.v7.1.txt.gz||v 1||mapping of STRING proteins to COGs used in iPath 1|
|og2ko_filtered005.txt.gz||v 2||mapping of COGs to KOs|
|ko20101128.gz||v 2||annotation for KOs used in iPath 2|
|module_20101013.gz||v 2||annotation for KEGG modules used in iPath 2|
|COG.mappings.v8.1.txt.gz||v 2||mapping of STRING proteins to COGs used in iPath 2|
If you wish to submit mapping data and other parameters directly to iPath2 from your own scripts or another web server, please use our direct access script.
Use this form to check our database for presence of any number of identifiers. This can be useful when you have a very large number of IDs in your selection, which can cause problems/crashes with our interactive viewer. Put your identifiers into a plain text file, one identifier per line. After processing, this script will return a list of matches in iPath's database, and you can limit your selection to these IDs only.
Element selection generators
Use the tools below to convert your data into iPath element selections. Clicking 'Generate element selection' will create a plain text file, which you can paste or upload into iPath's map customization box. Please contact us if you need help using the tools below, or if you have ideas for other useful data parsers/converters which we could implement.