Those of you working in groups will have an additional written delivery, as announced earlier.  The theme for this writing assignment will be chosen by you.  It could be inspired by background literature used in your project, a discussion of particular findings in your study etc.  It doesn’t necessarily have to be linked directly with your project, but it must be within the theme of the course.

The themes must be approved by Harald.  Any questions relating to the structure of the document will be handled by Berit.

Program

• Geospatial standards and formats
• Web Services
• Web Map Services (WMS)
• WFS, WCS, WTS, W3DS
• Open Web APIs
• GeoRSS

Slides: PPT / PDF.

Resource sites

The announced WMS lecture on the 19th is postponed until the 26th.  Correspondingly, the J2ME crash course is moved to March 5th.

Øyvinds presentation and code examples are now available.

You can also help Øyvind by visiting his storyteller web site and provide him with feedback.
As suggested at today’s lecture, those of you who haven’t yet made your own mashup are encouraged to do so.  Go to http://www.google.com/apis/maps/ and register for an API key.  A getting started document shows you how to get going.

You might also want to take a look at Mapstraction, a library that provides a common API for making it easier to deal with the different mapping services from Google, Yahoo! and Microsoft.  Mapstraction also works with Open Street Map, which makes it even more interesting.

There are no lectures next week. You should use the extra time to work on your project tasks. If you have questions, don’t hesitate to contact:

Rune Winther

Monica Kristiansen

Abstract

The abstract is a summary of the document. As a rule of thumb, everything appearing in the abstract should also appear somewhere in the main document (not necessarily as the exact same formulations, though). Do not assume that the reader is familiar with your project, however, it’s OK to assume that the reader is familiar with the main technologies and concepts you’re dealing with.

Problem statement

The problem statement should be a short and concise formulation of the the question(s) you’re trying to answer in your project. Common practise is to present one main goal, along with a few sub questions to provide more detail.

A well formulated problem statement helps you keep your focus through the project period, and makes it much easier to wrap up your project in the discussion/conclusion part of the report.

Methodology

Here you explain how you are going to find answers to the questions raised in the problem statement, through literature surveys, implementations of proof-of-concept prototypes, user tests and the like. The detail level highly depends on the nature of your objectives.

Living document

We strongly encourage you to establish your final project report as a “living document”, with the proper structure, abstract, introduction, references etc., where you fill in content as you go, as a draft.

Regular guidance will be given on Thursdays on the times listed below. Please note the prerequisites for attending the guidance session:

• Send an e-mail to Harald and Gunnar by lunch the day before, where you tell us what you want to focus on during the session.
• Remember to blog regularly about your progress (diary style).
• Use the Trac system actively.

Harald and Gunnar will alternate between guiding the morning and afternoon session. This Thursday (February 8th), Gunnar will do both sessions. In week seven, Harald will do the morning session, and Gunnar the afternoon session. In week eight, Gunnar does the morning session, and Harald the afternoon session, and so on.

Update: Løken/Olsen has switched times with Olsen/Bakken.

09:10 PyS60 BM Client (Bergh)
09:30 .net mobile BM Client (Jamissen)
09:50 GreenPhone BM Client (Arnesen)
10:10 J2ME BM Client (Gundersen)
10:30 Content Queuing (Flesjø)
10:50 BT proximity (Dervis / Henriksen)
11:10 Context sensitive route planning (D. T. Olsen / Bakken)
(Lunch)

12:00 Context for diabetics (Wasfy)
12:20 Context models (Engen / Paulsen)
12:40 OSM/Client (Toppe / Sætre)
13:00 OSM/HCI (Refsvik)
13:20 Context sensitive POI’s (Akerbæk / Reier)
13:40 Trusted Networks (Løken / T.Olsen)
14:00 User testing of context systems (Ludvigsen)

Program

• Maps
• Coordinate systems
• Projections
• Datum
• Scale
• Raster maps
• Vector maps
• Ortophoto
• Remote sensing (Satellite /aerial imagery)
• GPS
• Project OneMap

Slides: PPT / PDF.

Resource sites

Blogs

I’ve updated the schedule with notes from today’s lecture. You’ll find pointers to a number of SVN clients, as well as general SVN and Trac info.

Please spend some time familiarizing yourself with the tools, and create the required folders for your project. Remember that the project plan should be checked into Subversion by 16:00 this afternoon.