Difference between revisions of "FOSS4G 2006 Webmap BOF"
m (→Notes) |
Wiki-Dpatton (talk | contribs) m (add Category:FOSS4G2006) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
== Summary == | == Summary == | ||
| − | Christopher Schmidt posted a [https://mail.osgeo.org/servlets/ReadMsg?list=webmap-discuss&msgNo=119 summary of the meeting] to the [https://mail.osgeo.org/servlets/SummarizeList?listName=webmap-discuss OSGeo webmap-discuss mailing list]. ( | + | Christopher Schmidt posted a [https://mail.osgeo.org/servlets/ReadMsg?list=webmap-discuss&msgNo=119 summary of the meeting] to the [https://mail.osgeo.org/servlets/SummarizeList?listName=webmap-discuss OSGeo webmap-discuss mailing list]. (To actively join discussion mailto:webmap-discuss-subscribe@mail.osgeo.org and reply to the confirmation mail in order to subscribe.) |
== Projects == | == Projects == | ||
| Line 19: | Line 19: | ||
== Conclusion == | == Conclusion == | ||
| − | The meeting participants agreed that the simplest and most effective place to start integrating code between projects would be to select a map tile display engine and abstract it into a library. The map and layer rendering core from OpenLayers was selected for this task. By the end of October, the OpenLayers team will spec out an API (tentatively to be called '''webmap.js''') and begin to split out the minimal necessary portions of the OpenLayers code base into this separate library. By that time, each of the participating projects (hopefully ka-Map, OpenLayers, MapBuilder, and Mapbender, at a minimum) will evaluate their needs for a core tile display API and offer recommendations on how best to design the webmap.js library to offer maximum utility to everyone. | + | The meeting participants agreed that the simplest and most effective place to start integrating code between projects would be to select a map tile display engine and abstract it into a library. The map and layer rendering core from OpenLayers was selected for this task, due to its relative simplicity and modularity. By the end of October, the OpenLayers team will spec out an API (tentatively to be called '''webmap.js''') and begin to split out the minimal necessary portions of the OpenLayers code base into this separate library. By that time, each of the participating projects (hopefully ka-Map, OpenLayers, MapBuilder, and Mapbender, at a minimum) will evaluate their needs for a core tile display API and offer recommendations on how best to design the webmap.js library to offer maximum utility to everyone. |
| + | |||
| + | Our hope is that, in the future, the new core display library will ultimately be integrated into each project, and be developed collaboratively between the participating projects thereafter. | ||
== Notes == | == Notes == | ||
| Line 56: | Line 58: | ||
* Coordinate projections | * Coordinate projections | ||
* Event handling (higher level map semantics? and/or lower level browser semantics?) | * Event handling (higher level map semantics? and/or lower level browser semantics?) | ||
| − | * Documentation!!! | + | * Documentation!!!!! (lack thereof not a business strategy) |
* Unit tests | * Unit tests | ||
* Framework issues??? or none at all | * Framework issues??? or none at all | ||
| Line 65: | Line 67: | ||
---- | ---- | ||
| + | [[Category:FOSS4G2006]] | ||
Latest revision as of 21:03, 8 July 2007
The Web Map Client Bird of a Feather (BOF) session (also referred to as the ka-Map/OpenLayers merger BOF or AJAX Map Client BOF) at FOSS4G 2006 met from 1800 - 2000 on Wed 13 Sep 2006, with the intention of identifying common components that could be abstracted and shared between the various Free and Open web map client libraries.
Summary
Christopher Schmidt posted a summary of the meeting to the OSGeo webmap-discuss mailing list. (To actively join discussion mailto:webmap-discuss-subscribe@mail.osgeo.org and reply to the confirmation mail in order to subscribe.)
Projects
The following projects (at a minimum) were represented at the BOF:
Conclusion
The meeting participants agreed that the simplest and most effective place to start integrating code between projects would be to select a map tile display engine and abstract it into a library. The map and layer rendering core from OpenLayers was selected for this task, due to its relative simplicity and modularity. By the end of October, the OpenLayers team will spec out an API (tentatively to be called webmap.js) and begin to split out the minimal necessary portions of the OpenLayers code base into this separate library. By that time, each of the participating projects (hopefully ka-Map, OpenLayers, MapBuilder, and Mapbender, at a minimum) will evaluate their needs for a core tile display API and offer recommendations on how best to design the webmap.js library to offer maximum utility to everyone.
Our hope is that, in the future, the new core display library will ultimately be integrated into each project, and be developed collaboratively between the participating projects thereafter.
Notes
The following were the notes collected on the overhead screen during the meeting.
Possible Web Map Subsystems?
- Map display
- Layer
- Features
- Controls (UI widgets)
- Pan / zoom buttons
- Zoom bar
- Modal tools
- Link to this view
- Scale ratio
- Scale bar
- Ruler
- Measure area
- Legend generation
- Mouse actions
- Keyboard shortcuts
- Overlays
- Popups / info windows
- Client-side vector drawing
- Zorn
- SVG
- VML
- Canvas
- digitization
- Printing (generating PDF on the server?)
- Server-side tile generation
- Coordinate projections
- Event handling (higher level map semantics? and/or lower level browser semantics?)
- Documentation!!!!! (lack thereof not a business strategy)
- Unit tests
- Framework issues??? or none at all
- XML processing
- Licensing? BSD/LGPL preferred for reusability
webmap-discuss@lists.osgeo.org