Limits...
A simple method for serving Web hypermaps with dynamic database drill-down.

Boulos MN, Roudsari AV, Carson ER - Int J Health Geogr (2002)

Bottom Line: WebView, the Internet extension to ArcView, publishes HealthCyberMap ArcView Views as Web client-side imagemaps.This paper describes HealthCyberMap simple, low-cost method for "patching" WebView to serve hypermaps with dynamic database drill-down functionality on the Web.CONCLUSION: The authors believe their map serving approach as adopted in HealthCyberMap has been very successful, especially in cases when only map attribute data change without a corresponding effect on map appearance.

View Article: PubMed Central - HTML - PubMed

Affiliation: Centre for Measurement and Information in Medicine, School of Informatics, City University, London EC1V 0HB, UK. M.Nabih-Kamel-Boulos@city.ac.uk

ABSTRACT
BACKGROUND: HealthCyberMap http://healthcybermap.semanticweb.org aims at mapping parts of health information cyberspace in novel ways to deliver a semantically superior user experience. This is achieved through "intelligent" categorisation and interactive hypermedia visualisation of health resources using metadata, clinical codes and GIS. HealthCyberMap is an ArcView 3.1 project. WebView, the Internet extension to ArcView, publishes HealthCyberMap ArcView Views as Web client-side imagemaps. The basic WebView set-up does not support any GIS database connection, and published Web maps become disconnected from the original project. A dedicated Internet map server would be the best way to serve HealthCyberMap database-driven interactive Web maps, but is an expensive and complex solution to acquire, run and maintain. This paper describes HealthCyberMap simple, low-cost method for "patching" WebView to serve hypermaps with dynamic database drill-down functionality on the Web. RESULTS: The proposed solution is currently used for publishing HealthCyberMap GIS-generated navigational information maps on the Web while maintaining their links with the underlying resource metadata base. CONCLUSION: The authors believe their map serving approach as adopted in HealthCyberMap has been very successful, especially in cases when only map attribute data change without a corresponding effect on map appearance. It should be also possible to use the same solution to publish other interactive GIS-driven maps on the Web, e.g., maps of real world health problems.

No MeSH data available.


BodyViewer linking to resources within ArcView BodyViewer linking of its views to the underlying resource metadata table within ArcView GIS can only be done using one DC subject field at a time. In this regard, the corresponding HCM human body maps on the Web are superior since the linking query looks in all three DC subject fields in the underlying metadata base (see below).
© Copyright Policy
Related In: Results  -  Collection


getmorefigures.php?uid=PMC131013&req=5

Figure 15: BodyViewer linking to resources within ArcView BodyViewer linking of its views to the underlying resource metadata table within ArcView GIS can only be done using one DC subject field at a time. In this regard, the corresponding HCM human body maps on the Web are superior since the linking query looks in all three DC subject fields in the underlying metadata base (see below).

Mentions: In ArcView, BodyViewer views are not hot-linked to the underlying resource metadata table (within ArcView) until we perform what is called "Link Patients" in BodyViewer, though in this case we will be linking resources not patients. Although BodyViewer was able to aggregate three ICD fields in the previous step, the linking can only be done using one DC subject field at a time (Figure 15). The result of the linking in ArcView is shown in Figure 16. In this regard, the corresponding HCM human body maps on the Web are superior since the linking query (running on HCM Web server) looks in all three DC subject fields in the underlying metadata base. To export BodyViewer maps (views) to the Web using WebView, we have to first select a Map Unit ("meters") for the view or else WebView will not be able to determine a scale for rendering the detail map and will abort the process (Figure 17). We inserted a HotLink field in BodyViewer map tables to store the Web addresses of corresponding ASP query pages that will run on HCM Web server; this field is associated with the HotLink mouse event feature of WebView (Figure 18).


A simple method for serving Web hypermaps with dynamic database drill-down.

Boulos MN, Roudsari AV, Carson ER - Int J Health Geogr (2002)

BodyViewer linking to resources within ArcView BodyViewer linking of its views to the underlying resource metadata table within ArcView GIS can only be done using one DC subject field at a time. In this regard, the corresponding HCM human body maps on the Web are superior since the linking query looks in all three DC subject fields in the underlying metadata base (see below).
© Copyright Policy
Related In: Results  -  Collection

Show All Figures
getmorefigures.php?uid=PMC131013&req=5

Figure 15: BodyViewer linking to resources within ArcView BodyViewer linking of its views to the underlying resource metadata table within ArcView GIS can only be done using one DC subject field at a time. In this regard, the corresponding HCM human body maps on the Web are superior since the linking query looks in all three DC subject fields in the underlying metadata base (see below).
Mentions: In ArcView, BodyViewer views are not hot-linked to the underlying resource metadata table (within ArcView) until we perform what is called "Link Patients" in BodyViewer, though in this case we will be linking resources not patients. Although BodyViewer was able to aggregate three ICD fields in the previous step, the linking can only be done using one DC subject field at a time (Figure 15). The result of the linking in ArcView is shown in Figure 16. In this regard, the corresponding HCM human body maps on the Web are superior since the linking query (running on HCM Web server) looks in all three DC subject fields in the underlying metadata base. To export BodyViewer maps (views) to the Web using WebView, we have to first select a Map Unit ("meters") for the view or else WebView will not be able to determine a scale for rendering the detail map and will abort the process (Figure 17). We inserted a HotLink field in BodyViewer map tables to store the Web addresses of corresponding ASP query pages that will run on HCM Web server; this field is associated with the HotLink mouse event feature of WebView (Figure 18).

Bottom Line: WebView, the Internet extension to ArcView, publishes HealthCyberMap ArcView Views as Web client-side imagemaps.This paper describes HealthCyberMap simple, low-cost method for "patching" WebView to serve hypermaps with dynamic database drill-down functionality on the Web.CONCLUSION: The authors believe their map serving approach as adopted in HealthCyberMap has been very successful, especially in cases when only map attribute data change without a corresponding effect on map appearance.

View Article: PubMed Central - HTML - PubMed

Affiliation: Centre for Measurement and Information in Medicine, School of Informatics, City University, London EC1V 0HB, UK. M.Nabih-Kamel-Boulos@city.ac.uk

ABSTRACT
BACKGROUND: HealthCyberMap http://healthcybermap.semanticweb.org aims at mapping parts of health information cyberspace in novel ways to deliver a semantically superior user experience. This is achieved through "intelligent" categorisation and interactive hypermedia visualisation of health resources using metadata, clinical codes and GIS. HealthCyberMap is an ArcView 3.1 project. WebView, the Internet extension to ArcView, publishes HealthCyberMap ArcView Views as Web client-side imagemaps. The basic WebView set-up does not support any GIS database connection, and published Web maps become disconnected from the original project. A dedicated Internet map server would be the best way to serve HealthCyberMap database-driven interactive Web maps, but is an expensive and complex solution to acquire, run and maintain. This paper describes HealthCyberMap simple, low-cost method for "patching" WebView to serve hypermaps with dynamic database drill-down functionality on the Web. RESULTS: The proposed solution is currently used for publishing HealthCyberMap GIS-generated navigational information maps on the Web while maintaining their links with the underlying resource metadata base. CONCLUSION: The authors believe their map serving approach as adopted in HealthCyberMap has been very successful, especially in cases when only map attribute data change without a corresponding effect on map appearance. It should be also possible to use the same solution to publish other interactive GIS-driven maps on the Web, e.g., maps of real world health problems.

No MeSH data available.