GeoConnections - Canadian Geospatial Data Infrastructure

Working Group Meeting

Tools for Framework Data 
Creation and Integration

May 31st, 1999
Ottawa

Timothy V. Evangelatos
GeoConnections Secretariat
June 11th, 1999

Quick Links

1- Introduction:

Peter Paul opened the workshop by welcoming the more than 70 participants. He noted that the composition of the workshop was about 1/3 from industry and the remainder from federal and provincial government agencies. He felt that this was a good mix for the exchange of ideas. He then introduced Pierre Lafond who was the facilitator for the workshop.

Using a slide presentation (Attachment 3) Pierre Lafond provided a brief background and context for the workshop. Although a focus for GeoConnections is on making geospatial accessible through the Internet, the provision and use of such data will depend heavily upon the availability of appropriate tools and the community is looking to the commercial sector to provide them. The first workshop on data integration and tools (Reference 1) was hosted by the NRCan Center for Topographic Information in November 1998, and the conclusions reached are described in the next presentation. In February 99 and April 99 the GeoConnections Secretariat also organized two national meetings to deal with framework data and a number of related issues. Reports on these meetings are available (Attachment 2 and 3). In February 1999 the federal government announced the $60M GeoConnections program which includes a component for partnering with industry which will be the topic of a 3rd presentation. These presentations would be followed by reports on a number of related activities. Pierre introduced the workshop objectives which were:

Pierre acknowledged that the goals were very ambitious but he would do his best to accomplish as much of them as possible. Pierre noted that the concept and the specifications for framework data are still evolving but he reviewed the formal definitions for framework data, core data, and framework data architecture that were proposed at the first CGDI National Meeting, in February 1999, and he provided some examples of the ideas for national framework data that have been discussed by the Inter-Agency Committee on Geomatics (Attachment 3). After discussing the goals in more detail Pierre categorized the set of requirements for tools as follows: 2- Presentations:

1) Data Integration Tools Workshop: Sylvain Latour had organized and chaired the first workshop on tools. He saw that agencies such as the Inter-Agency Committee on Geomatics and Canadian Council On Geomatics were focusing heavily on data but not paying enough attention to the ensuring that appropriate tools would be available for creating, integrating, and using the framework data. In his experience, when users try to integrate geospatial data, they may spend over 80% of their time and resources in trying to integrate data from various sources. His vision is to reduce this effort by 1 or two orders of magnitude. At the last workshop, a consensus was achieved on four important aspects (Attachment 4) which are summarized below:

  1. Vision: Total data integration, done on-line and effort reduced from 80% to 1%
  2. The Precepts: International Standards (ISO and OGC), Service Architecture.
  3. Data Integration Services: • Align Geometry • Align Scale

  4. • Conflate • Translate Format
    • Evaluate Quality • Associate
    • Match Semantic
  5. Time Line:
Version 0.1: Discovery and access now
Version I: Format/Interface 1998/2002
Version II: Basic Data Integration 2002/2005
Version III: National Framework 2005/2008
Version IV: Interoperability 2008/2012
Version V: National CGDI 2012
A white paper on Data Integration was distributed to participants and is included as Attachment 5.

Henry Kucera felt that the time-line suggested by the first tools workshop was fairly conservative and he felt that it could be cut in half. Sylvan agreed that if we can work together effectively the full CGDI infrastructure could be realized much sooner.

Costas Armenakis inquired about the inclusion of a server for image based data in the CGDI vision. Sylvan replied that such data would be handled in the similar ways as other types of data and his discussion really applies to all forms of geospatial data.

2) Information Interoperability Institute (III): Bill Lalonde is the acting president of III, a not-for-profit organization, whose goal is to foster global information interoperability through such standards as OGDI (Open Geospatial Datastore Interface) and RDA (Remote Data Access), two related elements that must become part of the CGDI implementation strategy. OGDI is a Application Programmer’s Interface (API) that "opens" the door to geospatial data, whereas RDA is a similar specification for non-spatial data. The Secretary of State is providing $436K to establish III and an additional $400K is expected from DND and GTIS, to cover R & D and the integration of RDA and OGDI. The proposed III business plan predicts a $1.5M budget over five years which will be achieved through memberships and related R&D projects. 

Last week III hosted a 2-day technical workshop. The first day dealt with presentations by software vendors who have implemented the ODGI API. They described, and in some cases also demonstrated their solutions. Nine vendors discussed their work and some of the problems they had in implementing the OGDI specification. Up-to-now OGDI has been supported by an ad hoc group and the lack of a totally fixed, robust, well defined specification has caused some difficulties as various implementations differ slightly. As Bill explained, the purpose of the III is to solve issues such as these. The emphasis on the second day of the workshop was on what III is all about. Many issues were discussed, for example the processes to be implemented to deal with extensions to the core specification, OGDI support and promotion, relationship of III to the international standards bodies, where III are actively participating and in some cases leading certain initiative (e.g. OGC Web Mapping Testbed). A report on the III Technical Workshop is being prepared and will be available shortly. A new temporary web site is being installed at http://132.156.30.81/iii and a permanent home will be available soon.

Rupert Brooks wondered about the relationship of OGDI with other international standards efforts and if III would use their model. Bill replied that a key activity of III is to contribute to ISO TC211, ISO SC34 (SQL/MM), and OGC, as well as CGDI. In response to Henry Kucera’s question about memberships Bill noted that a preliminary list is on the III web site.

3) Funding Opportunities for Framework Tools Development: Paula Rojas provided a summary of the GeoConnections seven program elements which are reproduced below (Attachment 6):

Paula Rojas briefly reviewed efforts to define framework data and reported that the co-chairs of the Program Advisory Committee on Framework Data will be François Faucher (NRCan), and Brad Fay (NS Housing & Municipal Affairs) and new Secretariat member. She then described in some detail the GeoInnovations component of the program (Attachment 6). This is the GeoConnections partnership program with industry and has the following target areas:
    1. Development of Commercial Geospatial Infrastructure Technologies, Tools and Services
    2. Preparation of High Quality Databases for Connection to CGDI & Connection to CGDI
    3. Connection of High Quality Databases to CGDI
    4. Geomatics Applications
    5. Atlas of Canada and GeoGratis
The presentation focused on Target Area 1 as it relates to Tools for Framework Data. A competitive RFP process will be used to select proposals. Proposals for areas 1 & 2 must be submitted by September 1st, 99 and for areas 3, 4 and 5, they must be submitted by June 14th, 99. Paula closed by explaining how to get more information and to keep in touch with GeoConnections by consulting the web site at www.geoconnections.org. GeoConnections is also maintaining a database of those interested in receiving announcements and she invited participants to register on the web site. Antoine Terjanian asked Paula to clarify the IP aspects that may be impacted by co-funded projects. She indicated that for tool development, IP is still under discussion, but she felt that IP would remain the property of the contractor who would only be obliged to provide a license. Antoine then inquired if there was a list of available tools that they should use. Paula felt that the secretariat could provide references but suggested that the tools developers would be aware of what is available. To Antoine’s final question on how proposals will be evaluated, Paula responded that this would be managed through the secretariat who are creating teams composed of volunteers from federal and provincial agencies who will conduct the evaluations 

Henry Kucera asked about the skills network. He wondered if there were opportunities for skills transfer. Paula argued that although training is important, there are other programs that are focusing on that aspect. 

As a public servant that may be involved in proposal evaluation as well as the program advisory committee, and at the same time a probable partner in some of those proposals, Rick Morrison was concerned about the possibility of a conflict of interest. Paula noted that evaluators would be excluded from rating any project in which they were partnering. Rick continued with a concern about what he called the practice of "geoconnectivism"- which is a challenge, and that of "vendorism" - which is easy to do. He asked the workshop: how do we avoid the latter and move the former ahead? Paula commented that the vision for CGDI is that of a shared leadership and we must work together to make CGDI successful. 

Neil Anderson added that the Canadian Market is quite small and often governments do a disservice to small businesses. The government may help get a business or service created in Canada, but then the company finds that the local market is too small to support the business and it folds. This led to Neil’s question about the opportunity for leveraging potential projects with international partners. Paula replied that this is fine. The proposal must come from a Canadian company but there are no restrictions about who it partners with. (I thought that the IP had to remain in Canadian hands.)

4) GEOIDE R&D Investment Program: Daood Aidroos provided an overview of this $10M program which may provide opportunities for leveraging resources to build the CGDI. Over 30 SME’s, 25 universities, and 6 government departments, are collaborating in 20 projects (Attachment 7). Daood described the organizational and legal structure and gave examples on why GEOIDE has been formed. A problem for the country are the large number of geomatic data islands that need to become linked to enable decision makers to make informed decisions. He concluded with a description of a proposed evaluation framework for the projects and the program itself 

5) The GEOIDE Network - Opportunities for strategic investments: Jeff Edwards provided a description of the investment opportunites and priorities for GEOIDE (Attachment 8), which are reproduced below :

GEOIDE’s funding priorities are organized around a matrix of Users and Technologies Jeff Edwards illustrated how the various user thrusts will interact with 3 technology themes of data acqusition, management, and decision support, and then gave a list of a dozen examples of existing GEOIDE projects. Jeff concluded by listing the opportunities provided by GEOIDE for private industry, researchers, and users. Several current projects deal with framework data and there is room to expand these.

As Pierre Lafond had mentioned in his introduction the three background papers would be followed by short presentations from several federal agencies who are involved with some aspect of framework data tools.

6) Marine Geomatics/DFO: Paul Bellemare gave an overview of DFO’s activities which cover a wide range of tasks involving geospatial data. Some of these are:
  • Coastal Zone Management and Monitoring
  • Fisheries Management
  • Vessel Surveillance
  • Habitat Management
  • Navigable Waters Protection
  • Navigation and Safety
  • Emergency response
  • Small craft harbour management
  • Coastal and Ocean Mapping
  • Fisheries and Ocean Research
  • Paul listed the wide variety of geospatial data sets collected by DFO (Attachment 9) and then focused on the following three data sets that have been identified as being part of CGDI framework data:

    Paul noted that the CGDI thrust has helped motivate action within DFO to work towards a more integrated approach, and to begin the activities needed to identify, standardize, and structure its data holdings prior to making them more accessible on a network. Due to its special needs to collect and disseminate large volumes of up-to-date multi-dimensional data, DFO has had to lead in the development of a number of tools that are now finding their way into the broader community. He reported that DFO would be working with the Canadian Centre for Marine Communications to create a MSDI. In addition to identifying additional base data such as boundaries and limits they plan to hold a workshop on Marine Geomatics later this year. 

    Tim Evangelatos asked if the work done by the ACZISC on standards such as developing a single definition for "coastline" would be incorporated in the new effort for the MSDI. Paul responded affirmatively. He sees the ACZISC being an active participant in the work.

    Henry Kucera noted that members of the Mercator Alliance have been looking at the coastal zone marine infrastructure requirements. Paul acknowledged that priorities for the coastal zone are recognized and things are moving. He added that ACZISC is pulling parts of this together.

    Daood Aidroos asked if there were any "killer" applications identified in the coastal zone or marine areas. Paul felt that there were many opportunities to help make data available to so that managers could make better critical decisions. One example that he suggested was the management of the ecosystem. 

    7) DND Framework Activities: As Dave McKellar had been called away, Jennifer Hum-Millar was asked by DND to prepare and give the presentation. Currently DND’s framework activities cover the three areas of:

    RADARSAT images are being investigated to see if certain features can be extracted and used to update or improve the products that DND requires. Once this data is extracted from the remotely sensed images it would have to be generalized and attributed in an automated or semi-automated process. An important requirement is to update the shoreline (high-water line) for DNC and WVS products. They would like to have a single shoreline for all products. This work is being done with US partners such as NOAA and NIMA.

    With regard to GEOIDE, they have two related projects. One is to improve decision making using WWW and the second is the development of automated techniques to extract, generalize and access geospatial information from hyperspatial remotely sensed data (Attachment 10).

    Henry Kucera asked about the requirements for a dynamic model for sensor input to help determine where the coastline is. Jennifier acknowledged the need for such a model, but they are still investigating what aspects of the imagery can be exploited. Paul Bellemare thought that this was an excellent project. In the marine world there is a pressing requirement to define a vertical datum for water, as currently exists on land, and he argued that DND’s work should be accelerated.

    Neil Anderson noted that issues of the timely updating of geospatial data has not been adequately addressed and should be a major consideration. Diane Richardson added that the updating process is being investigated in certain GEOIDE projects. Similar to DND’s work they are looking at extracting features from satellite imagery, but a lot of research is still required.

    8) Statistics Canada and Elections Canada: These two agencies have been collaborating on creating a National Road Network and Sheila Rambeau and Pierre Lermusieaux chose to give a joint presentation. According to Sheila, Statistics Canada’s main application is the census and they require a national network upon which to conduct the enumeration. It is important for them to have data on roads and street addresses. Elections Canada require similar information as they must know where people live As the two agencies have common requirements, a partnership between the two agencies was created to maintain the road and address data base. Formats and software compatibility are issues and Pierre will expand on them later. Other features such as coastline are also important in order to provide context for the roads boundary data.

    Pierre reported that the joint program is ambitious but is progressing very well. Elections Canada wish to enrich the data base with data from many sources, and getting that data into a standard format is a challenge. Updating this data is a second challenge but as the two agencies want to avoid duplication and provide more effective services, updating is an important requirement and they are creating various layers to meet specific needs. The inclusion of appropriate metadata in data updates is becoming very important. They need to know the source, date of collection, lineage, etc. Another goal is to make accesss and use easier for returning officers and enumerators.

    Sheila concluded the presentation by listing a wish list for the two agencies. It includes: 

    Henry Kucera was concerned about the requirement for a common format. Common interfaces and models are being developed by Canadian industry and he sees opportunities for them to supply the tools required by the two agencies. Further he noted that one of Statistics Canada’s staff (Ron Graves) is one of the drivers of the ISO metadata standard. 

    Antoine Terjanian was interested in the problem of rural addressing. He reported that in Quebec civic addresses exist for all citizens and wondered if Statistics Canada was taking advantage of that. Sheila responded that there is a great deal of variety in how rural addresses are handled across Canada. Provinces like NS and NB that have implemented 911 are in good shape. In general this has been more of a municipal and telephone company activity rather than a provincial responsibility. The prairies have little 911 coverage. She added that getting access to appropriate data, which is often owned by the telephone companies and can be a problem. Further the assignment of new addresses is not done consistently across the country. 

    9) Center for Topographic Information: Christine Parent and Pierre-Yves Boisvert also provided a joint presentation. Christine provided an overview of what has been happening at the Centre for Topographic Information (CTI) with respect to the CGDI Data Alignment Layer (CDAL), while Yves described plans for the NTDB.

    Christine described the background of the CGDI Data Alignment Layer, a concept proposed by the IACG in 1997, and funded by WINS /NRCan in 1998. The objective is to provide georeferencing points for geospatial information throughout Canada in order to facilitate the integration of geospatial data sets. Presently 7M points are available from the CDAL Web Site at "http://cdal.geoconnections.org". Currently a flat ASCII file, a DBMS will be implemented to make access, data management, and use much easier. They also plan to improve the accuracy of the database through the use of provincial data and/or from the National Landsat 7 coverage. Commercial tools to facilitate CDAL use are required (Attachment 11).

    Pierre-Yves described the four main areas of interest for CTI (Attachment 12). These include

    Diane Richardson asked for more details on the use of Landsat 7 data as CCRS has similar interests. Sylvain Latour responded that when they have national coverage from Landsat 7, CTI will update the accuracy of the NTDB and the upgrading of CDAL will occur as a by-product of this activity. Sylvain added that only part of Canada will be updated, but with partners it would become possible to do all of Canada. To achieve this they are pursuing joint efforts with the provinces. To Diane’s next question as to whether the CDAL tool set would also be applicable to raster data, Sylvain replied that it would.

    Antoine Terjanian noted that there are other sources for updating the NTDB besides the Landsat 7 data. A major upgrade of the cadastre has just been completed in Quebec, and could be used. Sylvain agreed and CTI would prefer to work with the provinces. 

    10) Framework Tools Requirements of the Atlas of Canada: Rupert Brooks described the efforts of his division to bring together many different data sets into a solid framework to support a variety of mapping applications at scales of 1:1M and smaller. A base is being built from VMap Level 0 data and there are a number of requirements for new tools. The three main areas where tools are needed are generalisation, conflation and toponymy/text placement (Attachment 13). From the 1:1M base, generalisation to various scales down to 1/30M are required. In addition, generalisation operators for aggregation, smoothing/ simplification, selection, symbolisation and exaggeration are required. Internally to realize these goals two projects are underway. The first one in cooperation with Dr. Diane Richardson (CCRS) involves the generalisation of hydrology networks, and the second one on developing polygon aggregation routines is being done in collaboration with Dr. Lesley Chorlton (GSC). Rupert concluded by expressing interest in working with other partners to improve and develop the tools needed to carry out their work. Rick Morrison asked if users would be allowed to extract data from the National Atlas and use it in other applications. Rupert replied that through GeoGratis users are able to obtain some National Atlas Data. More will be available soon once they have completed their upgrades to make the data more analytically sound. Hydrology is the first priority with roads coming next. Rick further noted that GeoGratis provides a file-based download and he wondered about plans for providing an API for direct access to the National Atlas. Rupert noted that there will be an on-line map-making program with an available API that allows users to create maps on-line and then view them on the screen as a GIF file. Peter Paul added that images are provided because they do not have the right to provide all the vector data free of charge. As for providing vector data, chunks of the VMap Level 0 data are available at no charge but there are no plans to provide a custom extracting mechanism. Henry Kucera indicated that the data warehouse implemented at NRCan has the capability to both extract the data and to provide GIF images.

    11) Agriculture Canada: Peter Schut gave a short overview of the situation in the area of national soil data. Canadians have being collecting soil data since the early part of this century. Many surveys have been conducted, and in the 1970’s much of this data was digitized and used in GIS applications. Until 1990 things were going well and 75% of Canada had been mapped through provincial/federal cooperation. Now funding to maintain and support this data has been drooped at both federal and provincial levels. At present Ontario has three (different) copies of the database. Manitoba, Nova Scotia, and the federal government each have their own copy. Each data set has been worked on independently and so they all differ. The challenge for Peter is how to bring all these datasets together. He is proposing that under the CGDI banner, we try to develop the tools to not only bring such national data sets together but also to ensure that it can be effectively maintained. Daood Aidroos noted that insights like that from the past could help us avoid similar mistakes in the future. He asked Peter: based upon what he was hearing at this workshop was he more optimistic that we will be able to create initiatives that will be sustainable, and further, is the private sector the entity that will make it work? Peter argued that the private sector must be able to make a profit and in areas where this may not be feasible the government has a responsibility to act. In some cases the community will have to pressure the government. Neil Anderson added that in the development of infrastructure, as exemplified in the development of utilities (e.g. electricity, telephone, etc.), whether they are private or public, the community as a whole is now looking at out-sourcing to the private sector. Organizational structure must be examined since there may be better structures for the management of geospatial data and he suggested it would be of value for government agencies to look at out-sourcing the geospatial "stuff."

    Return to Top of PageTOP

    3- Breakout Groups:

    After lunch Pierre Lafond and the organizing committee suggested following five topics for discussion in breakout groups: 

      1) Generalization:
      2) Alignment: 3) Vector/Imagery Extraction
      4) Updating of Framework Core Data: 5) Presentation Issues due to Data Integration


      Following a short discussion it was decided to combine topics 1) and 5) and create three breakout groups to deal with different aspects of generalization. The context for the discussions were the tool requirements and the groups were given approximately one hour to work on their topic and then provide a summary of their conclusions to the rest of the group.

      1) Cartographic Generalization: Peter Paul reported for this groups which included several government agencies and one industry representative. Discussions centered upon weeding out detail for map presentations and the group considered the problem from four aspects:

      1. Have tools to quantify and attach priorities to the data before and after generalization. These priorities would be based upon aspects such as source and accuracy of the data, and the process must be repeatable.
      2. Need for tools to provide real-time generalization. This would apply to situations where users extract and integrate selected areas of the national framework data.
      3. Tools to ensure that the relationships between features are retained during the process of generalization
      4. The user must have the ability to exaggerate certain features that are important to their particular application. Peter suggested an example of an impact crater in Saskatchewan that could be lost at smaller scales.
        The group also looked at how end users would employ these tools in a computer application. For example they may begin with the name of a place or a geological feature, system would then extract appropriate layers and generalize them. This led to a discussion on how to add geographical names to a generalized data set and then deal with the cartographic problems associated with adding names and still producing a useful product. 

      2) Database Generalization: Rupert Brooks reported for the group that discussed this aspect of generalization. He noted that there were a large variety of views and many different opinions in the group. One of the first conclusions was that there are some categories of features that can be broken into super and sub-types hierarchies, and tools to handle these categories are somewhat in reach. However, there are other categories of features, that do not fit this model and will be much more difficult to handle. Other conclusions were:


      Henry Kucera urged the consideration of a common model. He felt that we must have a canonical model with common data types and repository tools to help specify domain models. This could lead to the realization of developing the rule-based systems for improved generalization as suggested by the group.

      3) Visualization Generalization: Pierre Lafond reported on the discussions of this group. A lot of time was spent on discussing the problems associated with "names." Doug O’Brien had described the progress of ISO TC211 with the handling of names. Some of the problems of visualization of the names of objects that were identified are:


      The group felt that the handling of text for paper maps was well understood but the visualization of text for the "digital world" is quite different. We require rules to be added to tools for parsing of the text. These should follow the work being done by TC211 and become a part of CGDI. Some of the rules suggested for visualization are:


      Rick Morrison felt that text placement was not as critical as other aspects of tools to support the CGDI. He suggested that the systems just provide a list of the names and then let the users massage them. Henry Kucera added that a feature-based model developed in BC several years ago would help resolve many of the text visualization problems that have been raised.

      Peter Paul noted that from the National Atlas point of view, users are really interested in a pretty cartographic product, and similarly for the large body of non-specialist users there is still a need for good quality cartographic product.

      In response to a question about how much do we know about the needs of CGDI users, Paula Rojas responded that, at present, the GeoConnections Secretariat has assumed that the stakeholders know their clientele and/or are looking at their needs. Paula also acknowledged that there is a large group of potential non-specialist users who need to be communicated with and suggested that efforts with sustainable communities may help with that task. Phyllis Charlesworth added that, except for our traditional users, we really don’t know much about future users of the CGDI, and we must avoid assuming that we do. Henry Kucera agreed, and felt that we will see a major growth in on-line use and we must put the appropriate tools in place to log information about the users and provide feedback. Doug O’Brien felt that you will never know who all your users are and using text placement as an example, where we have identified two distinct kinds of users, he argued that it was important to ensure that enough information is carried with the data so that it will satisfy all users.

      4) Alignment: Phyllis Charlesworth reported that her group discussed data integration and conflation in the context of the Data Alignment Layer (CDAL). Their initial observation was that CDAL does not meet all of the perceived requirements. Tools are needed to update it. Further we must manage expectations since the group felt that if CDAL did not meet the users’ need they would not come back again even when the full CDAL DBMS is implemented. In addition the group discussed the following topics:


      Peter Schut suggested that one of the most frequent users of CDAL is for integrating satellite imagery and he wondered if CTI had any case studies that they could make available on the web. Christine Parent responded affirmatively. The DAL web site is being enhanced and CTI would be willing to add such case studies to it.

      5) Vector/Imagery Extraction: Jeff Edwards used a slide presentation to report on this group (Attachment 14). Three applications were discussed and the technology issues associated with them identified. The applications were:

      1. Extraction of semantic information from imagery
      1. Change and discrepancy detection
      1. Use of existing vector databases with image extraction
      The five technology issues that were identified by the group were:
      1. Two ways to integrate
      1. Accuracy and Reliability of data
      1. Automatisaton
      1. Registration and control points
      1. Links to other topic groups
      Henry Kucera noted that the integration of vector and raster data was well covered but he wondered if the group had discussed the integration of vector data with other types of images (e.g. raster scanned maps or charts). One of the other participants responded that since the basic operations are scaling and registration, it should be possible to use very similar tools.

      6) Updating of Framework Core Data: Paula Rojas reported that her group was composed of 15 people split evenly between data supplier agencies and vendors. The group began with a roundtable on the philosophy of updating national framework data. National coverage will be provided through an evolving distributed environment determined by our stakeholders and some form of distributed updating capabilities. Following a discussion of a number of issues it was found that the tools could be grouped into three categories such as:

      A) Tools to compare differences in data and find changes

      B) Tools for the management of the changes C) Metadata Management Some of the issues discussed were:


      Paula concluded by re-iterating the underlaying importance of an overall model for CGDI to which everything would be mapped.

      Costas Armenakis inquired if the group had considered data set versions to keep track of changes to the features, or would the features be updated every time there is be a change. Paula felt that both were feasible, and Tim Evangelatos noted the use of both schemes in the CHS where new electronic charts are issued periodically with actual feature updates being carried out between the issuance of the new versions of the charts. All of this is done using an international standard, namely S57.

      Ron Graves is recommending that his agency, Statistics Canada, adopt a business model that would support "time travel", i.e., the ability to look at data over time. He acknowledged that this would be a more complex model than is in place now. Paula noted that the group discussed the importance of the data model and it will be up to the framework node of the CGDI Program Advisory Committee to lead the development/implemetation of it.

      The idea of a dynamic database bothered Phyllis Charlesworth. Keeping track of people’s actions in a distributed environment, with multiple sources of data, all integrated and presented on a single window, did not make sense to her. This led to a discussion on how to track changes which, unfortunately, had to be curtailed before reaching firm conclusions due to lack of time. Phyllis ended the discussion by commenting that she would not invest resources in such complex tools.

      Return to Top of PageTOP
    4- Conclusions:

    Pierre Lafond began a summary of the workshop by asking participants where do we go now? He felt that the presentations had been appropriate and highlighted the requirements for data integration tools. He acknowledged that although a set of tools in relation to framework data integration had been achieved we did not have enough time to prioritize them and Pierre asked what should be done with the list.

    Henry Kucera suggested that GeoConnections should be charged with determining the tool priorities and feed recommendations back to the community for future work. Paula added that those considering the submission of proposals to GeoInnovations 99 can use what they learned from the workshop. This knowledge will also so be used when GeoInnovations 2000 is developed. A report on the workshop will be prepared and made available on the GeoConnections web site.

    Henry Kucera argued that it was important to maintain the momentum that has been generated at the workshop and suggested that there is a need for a formal way to track and measure progress. Sylvain Latour felt, however, that the actual tool development should not be done at these open workshops but should be done elsewhere.

    Due to the pressure of time Pierre Lafond has to stop the discussion. He closed the workshop by thanking Sheila Rambeau and Statistics Canada for organizing and making the Simon Goldberg Conference Room available. He also thanked the Secretariat for organizing the workshop. Paula Rojas thanked Peter Paul and Rupert Brooks for proposing the workshop and developing the program.

      Return to Top of PageTOP
    5- Attachments:
    1. List of Participants
    2. Workshop Agenda
    3. Introduction: Presentation by Pierre Lafond
    4. "Data Integration Tools Workshop,"Presentation by Sylvain Latour
    5. White Paper on Data Integration by Sylvain Latour
    6. "Funding Opportunities for Framework Tools Development," Presentation by Paula Rojas
    7. "Geoide R&D Investment Program," Presentation by Daood Aidroos
    8. "The GEIODE Network – Opportunities for Strategic Investments," Presentation by Jeff Edwards
    9. "Marine Geomatics," Presentation by Paul Bellemare
    10. "DND Framework Activities," Presentation by Jennifer Hum-Miller
    11. "CGDI Data Alignment Layer," Christine Parent
    12. "Centre for Topographic Information," Presentation by Pierre-Yves Boisvert
    13. Presentation: "Framework Tools Requirements of the Atlas of Canada," Rupert Brooks
    14. Presentation Group 4: Vector/Imagery Integration, Jeff Edwards
    15. Precise Positioning in Canada Using Satellite Systems – Gordon Garrard, Geodetic Survey Division
    16. Web-Based Data – Jay Terrill, AutoDesk
    17. Toponymy – Peter Williams, Center for Topographic Information
    18. Dynamic distribution and synchronization of network computing processes. Prof. M.B. Zaremba
    19. National Forest Information System – Rick Morrison, National Forest Service

    Note: In the invitation to this workshop, participants were invited to submit a short description of their ongoing framework work and a wish-list of projects they would like to be involved in. Attachments 11, 15, 16, 17, 18, and 19 are of this type.

    Return to Top of PageTOP

    6- References:

    1. Evangelatos, T.V. Data Integration Tools for Framework Data," Sherbrooke, November 3 and 4th, 1998.
    2. Evangelatos, T.V. "National Coordination Meeting on Geospatial Data Infrastructure," Ottawa, February 8, 9, and 10th, 1999. 
    3. Evangelatos, T.V. "National Coordination Meeting on Geospatial Data Infrastructure," Ottawa, February 8, 9, and 10th, 1999 (in preparation).
    4. Coleman, D.J. et al, Towards a Conceptual Framework Architecture to Support the Canadian Geospatial Data Infrastructure (CGDI), Fredericton, NB, May 5, 1999.