Le programme de la rencontre des utilisateurs de QGIS francophone

L'OSGeo-fr et Montpellier SupAgro organisent une rencontre de deux jours autour de QGIS pour la communauté francophone. Cette rencontre se déroulera les 10 et 11 décembre à Montpellier SupAgro.


Durant la première journée plusieurs conférences seront proposées. Cette année, le thème de cette journée est "QGIS : Quels usages aujourd'hui ? Quels usages demain ?". Pour la soirée nous vous proposons de nous retrouver autour d'un verre dans un lieu qui vous sera indiqué lors de la journée.

La 2ème journée est organisée sous forme de barcamp : des ateliers informels où vous pouvez proposer des sujets, présenter des travaux, échanger, discuter. C'est un moment informel mais organisé pour échanger entre utilisateurs, contributeurs et financeurs. N'hésitez pas à venir découvrir une forme originale de contributions sur QGIS !

Voici quelques sujets pressentis :

  • comment traduire QGIS
  • comment utiliser QGIS sur une tablette (QField)
  • comment créer une carte avec QGIS et la diffuser sur le net
  • coupler PostGIS et QGIS

Si vous souhaitez avoir un retour de la communauté, obtenir de l'aide pour préparer ou discuter d'un sujet particulier avant la journée, venez en discuter sur la liste Francophone.

Le programme détaillé, le formulaire d'inscription et d'autres informations sont disponibles sur la page officiel.

Nous tenons à remercier vivement nos mécènes :

  • la société 3Liz
  • la société Camptocamp
  • le réseau des Conservatoires d'espaces naturels
Erreur | OSGeo-fr

Erreur

Message d'état

Il y a du contenu récemment syndiqué sur Eric Lemoine.

Message d'erreur

  • Warning : Cannot modify header information - headers already sent by (output started at /home/osgeo/www/includes/bootstrap.inc:1368) dans drupal_send_headers() (ligne 1216 dans /home/osgeo/www/includes/bootstrap.inc).
  • PDOException : SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xF0\x9F\x99\x82" ...' for column 'description' at row 1: INSERT INTO {aggregator_item} (title, link, author, description, guid, timestamp, fid) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( [:db_insert_placeholder_0] => MapFish and GeoExt [:db_insert_placeholder_1] => https://erilem.wordpress.com/2009/04/19/mapfish-and-geoext/ [:db_insert_placeholder_2] => erilem [:db_insert_placeholder_3] => <p>Matt Priour recently <a href="http://www.geoext.org/pipermail/users/2009-April/000045.html">asked</a> about the future of the client part of MapFish, and more specifically whether it will be replaced by <a href="http://www.geoext.org">GeoExt</a>. This is actually a question that every MapFish user should be asking<img src="https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" />. Anyway I thought an answer to that question could make a post on my blog. There it is.</p> <p><strong>The short story:</strong> the client part of MapFish will not be replaced by GeoExt.</p> <p><strong>Now the longer story</strong>. As of today the client part of MapFish includes OpenLayers, Ext, and the MapFish JavaScript lib. The latter is itself composed of two parts: <em>core</em> and <em>widgets</em>.</p> <ul> <li><em>core</em> includes classes that are independent of Ext; most of them extend OpenLayers classes like <code>OpenLayers.Control</code>, <code>OpenLayers.Protocol</code>, <code>OpenLayers.Strategy</code>, etc. For example the client-side implementation of the <a href="http://www.mapfish.org/trac/mapfish/wiki/MapFishProtocol">MapFish Protocol</a> is part of <em>core</em>.</li> <li><em>widgets</em> includes Ext-based classes, mostly GUI components (but not only, the FeatureReader and stuff are part of <em>widgets</em>). <em>widgets</em> also has stuff that&#8217;s directly related to the server side of MapFish, the print widgets are a good example.</li> </ul> <p>GeoExt will not replace <em>core</em>, nor will it replace the <em>widgets</em> components that rely on MapFish web services. But basically every new Ext-based component that isn&#8217;t tied to any server-side stuff is going into GeoExt.</p> <p>In addition to OpenLayers and Ext, MapFish will include GeoExt. We had initially planned to integrate GeoExt into MapFish earlier, but finally decided to let things settle down a bit in GeoExt before doing the integration. We&#8217;re currently doing that integration, and we will gradually be deprecating classes as their equivalents are added into GeoExt. For example, the work on FeatureRecord, FeatureReader and FeatureStore we&#8217;ve been doing in GeoExt will deprecate the FeatureReader, FeatureStore and LayerStoreMediator classes in the MapFish JavaScript lib.</p> <p>Also, MapFish, as a framework, aims to provide an integrated solution. For client-side development, this means that the developer doesn&#8217;t need to download Ext, OpenLayers and GeoExt, install them within his application, and think about the organization of his application. Instead, we want that applications created with the MapFish framework are well organized from their creations; with the Ext, OpenLayers, GeoExt and MapFish libs ready, with the JavaScript build tool ready, with the unit test suite ready, etc. I guess I will cover this topic in a later post&#8230;</p> <p>Wooo, two posts in two days, scarry&#8230;<img src="https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p><br /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/erilem.wordpress.com/54/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/erilem.wordpress.com/54/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=erilem.wordpress.com&#038;blog=1932211&#038;post=54&#038;subd=erilem&#038;ref=&#038;feed=1" width="1" height="1" /> [:db_insert_placeholder_4] => http://erilem.wordpress.com/?p=54 [:db_insert_placeholder_5] => 1240173611 [:db_insert_placeholder_6] => 10 ) dans aggregator_save_item() (ligne 163 dans /home/osgeo/www/modules/aggregator/aggregator.processor.inc).
Le site Web a rencontré une erreur inattendue. Veuillez essayer de nouveau plus tard.