3. The partnership policy Aim: to save public money by integrating data already produced and maintained by institutional partners*. * Post Office, Cadastral Agency, Forestry Agency, Electric network company, Railroad network company, Provincial Councils , Fire departments Today’s workflow Periodic bulk exchanges between GIS managers and IGN Partenaire Partner GIS division Bulk exchanges Inform
4. Partnership 2.0 Geo Web, geographic Information , Mashup , cartographic API , Geolocalisation , GeoRSS, Web mapping , Geoportail , Wiki , GPX, KML, Neo -geography, VGI … Make it easy and accelerate partners feedbacks . Federate partners and follow up feedbacks.
5. Contributors (witch crowd?) Media mappers Groupies (map lovers Passive Mapper Experts Value Effort Casual users Mecanical Turks Open mappers (wiki mappers) Experts Source : 1st EuroSDR Workshop - Crowd Sourcing for Updating National Databases - Break-out session No.1 - Interacting with the crowd – August 2009 http://www.eurosdr.net/workshops/crowdsourcing_2009/presentations/d-1.pdf
6. New workflow Partenaire Partner Inform Validate integrate GIS division Validate integrate Share Group Author Administrator Visitor
7.
8.
9.
10.
11. Workflow Web service user Add a new feedback inform email email reformulate amend inform email answer OK ? Experts Administrator authentication integrate inform validate validate inform email email Make feedback Collector RGE OK integrate feedback ? Feedback Database amend show consult consult
12. Next step… share Web partner GIS Partner IGN Web service Share feedback information API share share share Share data information
13. Example Group membership Feedback localization pushpin Géoportail API Search tools Sketch tools Description attachment etc.
First I would present you the French large scale reference system, composed of four components : an orthophoto, the parcel maps, a topographic database and an address component. We are changing from a classical updates to on the fly updating for the vector components. Then classic update using stereorestitution processes makes sure nothing has been forgotten and collects the rest of the information. Annual updates deal with the electric networks, administrative data and other facilities. On the fly updating concerns mains roads, railways, major facilities and more recently addresses. The main difficulties are to be informed of all changes and the capture of geometry.
In order to save public money, we use information's feedbacks from different institutional sources that already collect or produce themselves this information. Today, the workflow consists of periodic bulk exchanges between GIS managers and IGN. This exchanges are mainly manual an the information collected have to be rearranged to be used. As a collector makes a feedback to the partner, either using classical techniques (paper, fax,…) or new technologies, the GIS manager integrates the feedbacks to its database before extracting and sending the new information to us. This is time consuming and quite inefficient (double capture)…
At the same time, new technologies have appeared. We wondered how this new technologies could facilitate the workflow ?
It is a kind of crowd sourcing, as defined at EuroSDR Workshop on crowd Sourcing for national databases. The crowd we are interested in, is the expert group. It has a great value because it deals with data that the partners already collect for their own usage.
So we plan to federate the update collection in a single application as a web service using a cartographic interface (Géoportail API). The updates coming from the sources would be reachable for all users directly. Different roles arise : authors that collect the information, administrator to validate and integrate the information and organize the group and visitor that just consult the service. We can find such roles in content management system (CMS) to publish information on the web. Actually, we want a geographic CMS.
We have developed a service to report new information or errors on our databases Documents can be join to refine the feedbacks. Sketches can be drowned to specify it. Partners can add their own themes to make their own feedbacks on their own domain.
The administration of the feedbacks is shared between IGN and the partners.
The workflow include an answer to inform the contributor that the information has been integrated or not in the database.
So the contributors can consult and follow the integration of its feedbacks and other partners informations can be shared, using classical rss feed and mail or more elaborated formats (KML, …).
The main challenge of the workflow is to find as soon as possible the right person that will integrate the feedback into the database. Input mismatch or bad thematic choice will lead to deadlock as the information won't be understandable to the end-user. At this step, an administrator has to point out the feedback and refine it.
Although the web interface is a good solution for non GIS users, it’s a drawback for professional users that already have implemented a structured system. They want to access to their own data in the application they used to use. Changing for a new interface, even as simple as a web browser, is regarded as time consuming and rejected. So we have developed an API to connect to the web service through an other application or a GIS.