Abstract With the proliferation of various geographic databases on the Internet, we have seen increasing needs for accessing them concurrently and remotely via the Web for high‐level decision making. In this paper, we present Middleware for Efficient Access to Databases through OpenGIS Wrappers (MEADOW), an object‐oriented middleware system we have developed to meet these needs. Current OpenGIS standard addresses many interoperability issues involved in such a global utilization of geographic databases. However, existing Simple Feature specification for CORBA (SFCORBA) implementations of OpenGIS proved to be insufficient for MEADOW. The main problems are the complexity of system development and maintenance, and the inefficiency of accessing remote data servers for processing region queries. We resolved the complexity problem by automatically generating a major portion of the application code, specifically wrappers on database servers and client library modules called transparent access providers. A MEADOW view definition language was developed as a high‐level specification language for this purpose. The efficiency problem was resolved by using a region‐based group prefetching of spatial objects from a geographic region. In addition, we implemented an OID‐based semijoin for efficient global query processing, and a region‐level locking to enhance the level of concurrency among region queries. Copyright © 2002 John Wiley & Sons, Ltd

With the proliferation of various geographic database servers on the Internet, the need to access them simultaneously through the Web arises frequently for high-level decision making. The ongoing OpenGIS standard addresses many of the interoperability issues to make such global utilization of geographic databases possible. Based on the OpenGIS standard, the paper presents an object oriented architecture for the efficient Web based access to multiple geographic databases on the Internet. Called MEADOW, it provides a pair of automatically generated modules: the OpenGIS wrapper on the server side and the matching transparent access provider (TAP) on the client side. In cooperation with the wrapper, TAP supports an application's efficient access to the databases through prefetching and caching of remote objects.