On the client side, MapFish had to make several choices in order to propose one framework for building Rich Internet Applications. The main criteria of this choice was the flexibility, the completeness, the multi browser support and the power. There are probably several technologies or libraries that are able to meet these criteria, so, at the end, a choice is needed. For MapFish, the choice was to use OpenLayers, ExtJS and GeoExt as JavaScript libraries.
And now, the famous questions: Why not JQuery ? Why not Flash/Flex ? Why not Dojo ? Why not etc, etc… ? Easy answer: a choice had to be made. For more arguments, I propose to read two very interesting blogs:
- JQuery and/or ExtJS I like the neutral approach and arguments.
- And of course, the famous blog of Steve Job. I like the non neutral approach and some of the arguments. Of course Adobe has an answer. But about this answer, sorry, I can’t believe the sentence “Create once and deploy on multiple devices”. It’s per definition wrong, other why would you have multiple devices if you would have always the same application ? Needs are different, users are differents, expectations are different… so applications will be different. It’s a nice sentence, but it’s not the reality. And if Adobe has 8 millions download of Flash per day, it’s probably because users have always the wrong flash version installed….
Posts Tagged ‘OpenLayers’
ExtJS – JQuery – Flash
Saturday, May 1st, 2010 by Cédric MoulletMapFish and OpenAddresses podcasted
Tuesday, April 20th, 2010 by Cédric MoulletThe goal of OpenAddresses is to create an open and free database of geolocated addresses. You can learn more about this project in the Directions Magazine podcast or in the press release .
The ease of use and simplicity of MapFish allowed the creation of this site in a few weeks. The very nice thing is that MapFish provides automatically a complete range of REST services (see here ). For OpenAddresses, a powerful Full Text Search has been developed and will be soon integrated in MapFish. On the client side, the usage of ExtJS , OpenLayers and GeoExt is very flexible and proposes an ergonomic UI. This is particularly important in crowd-sourcing efforts because the learning curve has to be very short. Since data are edited, it was also important to facilitate the acquisition work in order to let the user create a large number of addresses in a short time, in another word: efficiency.
On the cartographic server side, MapServer is acting as a cascading WMS. This technology allows the usage of whatever open WMS in the world. MapServer will handle the reprojection work if necessary.
Don’t forget to add your own address
Camptocamp – Sortie du Catalogue 2010 des formations Geospatial
Tuesday, February 2nd, 2010 by Yves Jacolin
Le catalogue 2010 des formations Geospatial de Camptocamp est désormais disponible en ligne . L’ensemble des sessions est axé sur la mise en œuvre et le développement de solutions Geospatial Open Source.
OpenLayers 2.8 is out !
Monday, June 29th, 2009 by Pierre GiraudIn this release, among others, here are some functionnalities / enhancements Camptocamp team focused their efforts on :
- multi-layer feature selection ,
- strategies and protocol, which wouldn’t exist without the great implication from Eric Lemoine,
Some others were almost ready to go or at least initiated by Camptocamp in the sandboxes, and completed by other folks :
- snapping while editing vector features,
- support for drawing text on vector layers.
For the complete set of new features or bug fixes, please see the release notes .
OpenLayers MapTypePanel
Monday, June 8th, 2009 by Pierre GiraudA while ago, I started working on map type controls "ala-google" and the corresponding panel. For those who don’t know what is behind this weird name, it’s simply a control that shows text blocks in the top right corner of the map. Clicking on those blocks allows to switch between the map base layers.
Though it’s not complete, it can be already used, in my opinion.
Should it go to trunk ? Should it be available as an add-in ? Here are good questions.
The code is currently available in an OpenLayers sandbox . You can also have a look at the working demo .
OpenLayers.Format.CSW
Friday, June 5th, 2009 by Eric LemoineIn the context of the GeoBretagne project , which aims at building a spatial infrastructure for the "the Prefecture and Regional Council of Brittany", we are working on improving the connection between the OpenLayers/GeoExt/MapFish world and the cataloging world, with a focus on GeoNetwork and OGC standards.
More specifically we are currently developping a new OpenLayers format for CSW (the OGC’s "Cataloging Service for the Web" standard). This format will allow writing CSW GetRecords requests, for searching cataloging systems supporting the CSW standard (GeoNetwork does), and reading responses sent by those systems. We’re about to open an OpenLayers sandbox for this development, and we’re targeting Release 2.9 of OpenLayers.
We also envision adding a new data type to GeoExt so that CSW records read using the CSW OpenLayers format can easily be added to Ext components, such as grids, combos, dataviews, etc. Here we’re targeting Release 0.6 or 0.7 of GeoExt (the first GeoExt release, GeoExt 0.5, is around the corner at time if this writing).
Stay tuned.
MapFish for hydrology: www.swissrivers.ch
Friday, May 1st, 2009 by Cédric Moulletwww.swissrivers.ch web site is live ! The main goal of this MapFish application is to provide forecast for river flow and lake level. All this information is provided twice a day and is issued from an hydrological software developped by e-dric.ch .
Snap in OpenLayers
Thursday, March 12th, 2009 by Cédric MoulletFrédéric Junod and Eric Lemoine have participated to the development of the new snapping functions of OpenLayers. This function will be part of OL 2.8.
Split is also very nice.
We look forward to use them in the next MapFish build
Toronto Code Sprint
Thursday, March 12th, 2009 by Thomas BonfortThe plot starts with a Toronto hotel on the banks of the Ontario lake booked from the 7th to the 10th of March, 4 whole days initiated by Paul Ramsey gathering the C tribe of Open Source GIS.
Paul successfuly managed to obtain sponsorship and to create the impulsion to unite more than 20 developpers essentially from the MapServer , PostGIS and GDAL communities, but also TinyOWS , libLAS and OpenLayers (a couple of developpers from closed-source MrSid were also present).
A big thanks to him and to Tom Kralidis for looking after the logistics of the events, and to the sponsors for financially participating to allow this to happen.
At first sounding North-American only, the event finally took an international accent with the presence of some european developers, Camptocamp having sent Thomas Bonfort and Olivier Courtin to take part in the sprint.
The event was "back to the roots" for the MapServer tribe, probably more resemblant to the Mapserver User Meetings, these having been superceeded in 2006 by the FOSS4G conferences where highly technical meetings between core developers are greatly reduced.
For the PostGIS tribe, this was trully a new thing, the major actual contributors having beforehand never met physically !
One of the major advantages of this kind of event is to allow a very rapid pace of development for each project, ensured by the physical (or IRC for some) presence of the major contributors who can straight away provide their expertise and visions, take decisions, and be sollicited on specific questions.
There was a strong interaction between members of each project, but also between members of different projects, learning on the way how to make their code best interact
with one another.
The second advantage of these meetings is that they help build up and keep a team dynamic, which is somewhat harder to obtain solely through online discussion and exchanges.
And the building of a dynamic for 20 people spanning a 4 day period was clearly addressed, beginning right at the first evening the day before the sprint at the local bar, a beer in one hand, a burger in the other, with geek Tshirts being the rallying apparel.
Day #1 was mainly passed on discussion and planification of the objectives and actions to take in the following days, as well the individual roadmaps for each project. This lively, noisy, and rich in propositions first day finished on a virile and sportive event, namely
a Hockey game between a Canadian and American team. For us europeans not used to icerings, the show was permanent, passing from intense game periods, to manly fights between players, to entertainment between the game periods (with a musical band, cheerleaders, and superhero contests)
The following days were much more "to the point", alterning intense studious periods where only the keyboards clicking could be heard aside from the AC fan and the cans of pop being opened (the choice of said pops having been longly discussed on the sprint list beforehand, of course !), and animated technical discussions that necessitated or led to the intervention of the concerned gurus.
The daily ending call around 6PM was the sign that our physical needs should take the pace over our intellectual ones (in other words, that it was time for beer and food!).
Nevertheless, these moments weren’t solely fun and games, as many technical and fructuous discussions took place late into the night.
The last day (#4 for the initiated) was somewhat slower, as folks were getting tired and slowly leaving depending on the time of their flight back home.
All in all, it was a real pleasure to meet all these great people, and getting to share some well-spent time together. As you can imagine, the public was essentially masculin, Regina Obe of PostGIS fame being the sole feminine presence on this weekend of the international women’s day!
The theme of the session had been clearly set by Paul beforehand, namely "The Need for Speed", as a beneficial emulation has existed since 2007 between the C and JAVA tribes on the grounds of pure performance.
And you have to know that for the C tribe, being caught up on the grounds of pure performance is in the very least a direct affront, so a proportionate response had to be taken! We do have some margin before we get to throw our gloves on the ground and start a fight like what we saw on the ice ring though!
This post gives the general tone of the event, we’ll elaborate in the next couple of posts on the more technical details of what was accomplished, namely on the performance front, the respect of OGC/ISO standards, and the creation of high quality and high resolution maps.
Thomas Bonfort, Senior Developper (MapServer) & Olivier Courtin, GIS Expert (PotGIS & OGC)
De Cartoweb à MapFish: une évolution logique.
Saturday, January 24th, 2009 by Cédric MoulletNeogeo décrit de manière claire la nécessité de l’évolution de Cartoweb (ou de produits semblables comme MapBuilder,Neapoljs, MapBender, MapGuide 5.x/6.x, liste non exhaustive), à MapFish. Cette évolution est essentiellement d’ordre technologique car elle fait suite à la maturation des protocoles d’échanges cartographiques (WMS, WFS, REST+GeoJSON), à la maturation des techniques AJAX (HTML / CSS / DOM / JavaScript / XMLHttpRequest / XML-JSON), à la maturation des services WEB (SOAP / REST), à la maturation de librairies (OpenLayers, ExtJS, Tilecache, SQLAlchemy, Shapely, JTS) et à la maturation de langages de développement (Javascript / Python / Ruby).
Bon, ceci est la vision du développeur. Comme dans tout bon projet informatique, il faut mettre l’utilisateur au centre des préocupations et ces considérations technologiques ont un impact important sur l’utilisateur, car les applications développées à partir du framework MapFish sont plus réactives, plus interactives, plus intuitives, plus flexibles et peuvent offrir plus de fonctionnalités.
Attention, il ne s’agit pas ici de faire le procès de Cartoweb ou des autres produits cités qui permettent le développement de superbes applications cartographiques, mais plutôt d’expliquer cette évolution logique de Cartoweb à MapFish.








