Topic outline

    • Not available unless: You are a(n) Student
  • Preliminary course schedule is as follows.

    Week (dates)

    Learning session

    Exercise session

    9 (1-7.3)

    Learning session 1

    Introduction to course, working in groups, software projects

    No session (project not started)

    10 (8-14.3)

    Learning session 2

    Spatial web services

    Project kickoff session

    11 (15-21.3)

    Learning session 3

    Agent-based modeling

    Support session (obligatory)

    12 (22-28.3)

    Learning session 4

    3D models

    Deadline session

    13 (29.3-4.4)

    Learning session 5

    Software development projects

    Good Friday, no session

    14 (5-11.4)

    Learning session 6

    Project delivery and finalizing a project

    Deadline session

    15 (12-18.4)

    Period IV assessment week (no more learning sessions)

    Support session (optional)

    16 (19-25.4)


    Project mid-term presentation (Deadline session)

    17 (26.4-2.5)


    eve of Wappu, no session

    18 (3-9.5


    Deadline session

    19 (10-16.5)

     Ascension day

    Support session (optional)

    20 (17-23.5)

    Project delivery (21st)

    21 (24-30.5)


    Portfolio delivery (30th)

    22 (31.5-6.6)

     Period V assessment week


    During period IV, there will be a learning session on every Thursday starting at noon (12:15, to be exact). There will be no such events on period V.

    The course project will last 10 weeks (5 SCRUM sprints). The project will start early in period IV, and will last until late period V. Preliminary schedule is to start the project on Friday, March 12th, and have the project delivery on Friday, May 21st. The schedule may be adjusted by one week, if necessary.

    During both periods IV and V, there will be short (max 1h) chance for to meet the course staff regarding the project on Fridays between 10 and 12. Every other of these meetings will be a SCRUM spring review session. Every other session will be a more general session, where the project group can discuss any issues they have with the course staff.

    In the beginning ov period V, there will be a mid-project presentation, where the project groups will describe their project and their work to the whole course.

    At the end of period V, there will be a project delivery seminar, where the groups will present their projects and formally submit them.

  • In order to pass the course, you need to do the following:

    1.      Do the project as part of a group

    2.      Make a learning portfolio

    An overview of the project is given on the GIS development project page. Details of the learning portfolio are given below.

    Learning sessions (lectures) on the course

    On each week, we will hold a four-hour learning session. These learning sessions are not traditional lectures. Instead, we will look at the issues important to the course (such as working in a project, data management for a web service, etc.) together. The sessions will contain some lecture-like elements, but also group work, presenting your group work results, etc.

    The learning sessions will be held on MS Teams on Thursdays at 12-14.

    Exercise sessions on the course

    Also, once per week each project group will have a one-hour session with the course staff to discuss the current state of their project. The sessions are either support sessions, or deadline sessions.

    In support sessions the group can bring forth problems they have had and ask for advice, or otherwise discuss what they need in order to move forward with their work.

    In deadline sessions the current state of the group’s project is reviewed, and the course staff will compare the state to the current Sprint Goals.

    Each group needs to reserve the time for their session beforehand.

    The Learning portfolio

    The learning portfolio consists of the following elements:

    1. A learning diary focusing on your work in the project, but also covering the learning sessions (lectures)
      1. Focus the diary on your part of the work in the project. You can, for example, include some of the following topics in your learning diary: what did you do, how much did you know beforehand and how much did you learn during the project, what did you consider particularly challenging, or particularly enjoyable, and what parts of your own work are you most proud of.
      2. Make sure to write the learning diary so it reflects on your own learning during the project, as well as remember to cover the whole project
      3. One way to structure the diary is also to take into account how the project is structured: the starting phase, two Sprints, and finally finishing the project
      4. The size of a good learning diary can be anything from 5 to 15 pages, depending on your writing style and the level detail you are using
    2. The time keeping you did for the project. You can also keep track of the time you used on the course that was not part of the project work.
    3. Your personal reflection on the project and the group work: what did it feel like working in a software project group, did your group work well together, were there things you think you succeeded particularly well, or things you failed at, etc.Appropriate length for this part of the protfolio is between 1 and 4 pages, depending on how much you feel you need to say, as well as how much you think you need to go into details

    You can also give course feedback in the learning portfolio, but this part is not required and will not affect the grading. You can also give feedback using the course feedback form if you wish for your feedback to be anonymous.

    If you want, you can further structure your learning diary using things like the Gibbs’ reflective cycle. The following web resources might be useful:

  • The description of the software development project done on the course will be added here.

    There will be two project topics for the course. Both will be done by at least one project group duringt he course.

    Agent-based modeling of COVID-19 transmission in grocery stores

    The first topic is modeling COVID-19 transmission in a grocery store setting with Agent-Based Models (see and The group, which takes this topic, will start with existing ABM implementation (in Python). Their initial task is to implement an existing grocery store (A Bloc K-Market) on top of the existing implementation and be able to run the model with that data.

    After the model is running, there are at least two further development paths that should be followed. First, a simple web service should be established, where the model (either the original model with the synthetic store, or the A Bloc K-Market store) can be run with different parameters and the results will be reported to the user. Second, the model should be further developed to take into account, for example, rush hours, store staff, etc. 

    Specific elements to be included in the project will be discussed later.

    Outside view from buildings in Helsinki using 3D city model

    The second topic is creating a "view from a window" -service for Helsinki. Helsinki city has created a freely available 3d city models that cover the whole city (see Using this model, it is possible to create a simulated view from a window from practically every window in every house in Helsinki. The view would be similar to what could be seen from the actual window.

    The initial task in this project would be create meathod for creating a simulated window view for a given address on a given floor, and to a given direction. Thus the parameters would not actually be for a specific window, but for a more generic but "close enough" simulation of such.

    After the initial window view creation works, then it needs to be turned into a web service. Furthermore, using the 3d model, the window view can be analyzed and different characteristics of the view can be calculated. In this project, the following characteristics are focused on:
    1. The farthest distance visible in the view
    2. Visibility and amount of some specific elements, such as the sea, vegetation, or other buildings
    3. Sunlight hours and total amount of sunlight on the window
    Specific elements to be included in the project will be discussed later.