| PubMed | Nucleotide | Protein | Genome | Structure | Taxonomy |
| Lycopersicon esculentum genome data and search tips | Revised June 2, 2003 |
| The Map Viewer help document describes how to use the Map Viewer software. This page describes the data available for Lycopersicon esculentum (tomato), and the search tips specific to that organism. You may return to the Lycopersicon esculentum genome overview page to follow links to on-line help for Lycopersicon esculentum bioinformatics. The Map Viewer home page allows you to search the genome data of any organism represented in MapViewer. |
|
|
| Three points about genetic maps need to be emphasized. First, genetic maps usually are generated as a close-ended project. When the map is offered to the public there is little refinement afterwards. Second, the unit of a genetic map is the cM, computed from the frequency of recombination between two segregating loci. Thus the determined size of a chromosome, in cM, depends upon the extent of the chromosome between the most separated markers and may vary between different genetic maps. Third, correlation between genetic maps is only possible to the extent of comparison between the loci common to the maps under comparison. To facilitate comparison between genetic maps, MapViewer can graphically indicate a locus that is common to adjacent maps. This capability is user-controlled via the "Display settings" link at the top of the MapView page. Checking (mouse clicking) the "Show connections" option in the "Display settings" dialog box invokes the capability. The order of genetic map presentation (left to right across the window) is also chosen in the "Display settings" dialog box.
The "Verbose" mode, chosen in the "Display settings" dialog box, shows the GenBank accession(s) associated with the molecular probe. |
| Frequency of Updates to Map Viewer Data |
|
| The maps are all completed endeavors. |
|
|
| Currently four maps are available. As other map data is acquired, these maps will be noted as being available. |
| Genetic map, 1992 |
|
| This map was built using an F2 population from a backcross to L. pennelli of the interspecific cross of L. esculentum (LA1500) X L. pennellii (LA716). The data was previously published in Bernhatzky R and Tanksley SD; Genetics 1986; 112:887-898. Map units are cM. |
| L. esculentum X L. pennellii; 1986 |
|
| This is the first plant genetic map where most of the loci are detected by DNA molecular markers. The map was built using an F2 population from a backcross to L. pennelli of the interspecific cross of L. esculentum (LA1500) X L. pennellii (LA716). The work was published previously in Bernhatzky R and Tanksley SD; Genetics 1986; 112:887-898. Map units are cM. |
| L. esculentum X L. pennellii; 1992 |
|
| This map was built using an F2 population derived from the interspecific cross of L. esculentum cv VF36-Tm2a X L. pennelli LA716. The details of the work are available in Tanksley SD et al (1992). Map units are cM. |
| L. esculentum X L. pennellii; 2000 |
|
| This is the tomato genetic map of conserved ortholog set (COS) markers for dicotyledon plants. The details of the work are available in Fulton TM et al (2000). Map units are cM. |
|
|
| Searchable Terms |
|
| Text terms |
|
The current version implements searching of flat files. The viewer supports searching on any text term that may describe an element on the map. These include:
|
|
| Map Positions |
|
As noted in the Search By Position section of the Entrez Map Viewer general help document,
there are three main ways to search by map position from the
Map View of a chromosome:
|
| Query options |
|
| Boolean Operators |
|
| Boolean operators in a query are not currently supported. |
| Advanced Search Page |
|
| The Advanced Search page is currently under development. |
|
|
| If you would like to create WWW links to the Map Viewer, the instructions for constructing URLs are given in the general Map Viewer Help document. You can construct URLs that either perform a search or display a specific mapped object or chromosomal region. |
| Questions or comments: Write to NCBI Service Desk |