14.06.2013 Views

Databases and Systems

Databases and Systems

Databases and Systems

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

94<br />

positional querying semantics, the integration algorithm, <strong>and</strong> the graphic display of<br />

integrated maps.<br />

Map Display<br />

The MapView 2.0 Java applet currently used in GDB can display multiple maps<br />

with alignment lines between common markers (figure 9).<br />

Figure 9: MapView 2.0 shows the same region in several maps.<br />

One problem with such displays is that the number of maps keeps increasing.<br />

After doing a positional query the user is currently asked to select which of the maps<br />

intersecting the query region they wish to see in the viewer. That list keeps getting<br />

longer, <strong>and</strong> the user often has no intelligent basis for making the choice. We would<br />

like to provide a robust default for this choice: an integrated map whose content<br />

synthesizes that of all the other maps.<br />

Integrated maps can be constructed based on piecewise-linear alignments. To<br />

produce these maps the various universal coordinate localizations for a locus must be<br />

combined into a single interval; at GDB we use a modified form of unioning which<br />

throws out poor localizations that are consistent with tighter ones. The resulting<br />

integrated or comprehensive map (figure 10) can be useful for certain purposes, but<br />

must be treated with some skepticism. Anyone wanting detailed order information in<br />

particular is well advised to look at the original maps, not the integrated one.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!