From 0f730fd543a36d668d4d8e3110aca6118ef9d455 Mon Sep 17 00:00:00 2001 From: Gabriele Filomena Date: Tue, 14 Jan 2025 15:31:29 +0000 Subject: [PATCH] docs --- general/assessments.html | 808 -------------------------------------- general/assignmentI.html | 756 ----------------------------------- general/assignmentII.html | 755 ----------------------------------- 3 files changed, 2319 deletions(-) delete mode 100644 general/assessments.html delete mode 100644 general/assignmentI.html delete mode 100644 general/assignmentII.html diff --git a/general/assessments.html b/general/assessments.html deleted file mode 100644 index 8809337..0000000 --- a/general/assessments.html +++ /dev/null @@ -1,808 +0,0 @@ - - - - - - - - - -Assessments: General Remarks – Web Mapping and Geovisualisation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- -
- -
- - -
- - - -
- -
-
-

Assessments: General Remarks

-
- - - -
- - - - -
- - - -
- - -
-

Submission

-

Please follow these templates consistently:

-

Assignment I https://github.com/GDSL-UL/wma/blob/main/templates/Assignment2_template.ipynb Assignment II: https://github.com/GDSL-UL/wma/blob/main/templates/Assignment2_template.ipynb

-

Download the as follows: and edit them accordingly.

-

You will submit through Canvas a .html file obtained from a Python .ipynb Jupyter Notebook file. To do so, in your .ipynb file, follow these steps: File –> Save and Export as.. –> HTML. Prior to this step, the notebook needs to be rendered (i.e. all the cells should be executed).

-

Other file formats will not be accepted.

-

Important for Assignment II, before exporting your .ipynb to a .html file: follow the steps described in the template to include an interactive dashboard in the static html that will be sumbitted as your assignment. This is to guarantee that your dashboard works in the submission file. You are responsible of your dashboard working as expected.

-
-
-

Marking Criteria

-

This course follows the standard marking criteria (the general ones and those relating to GIS assignments in particular) set by the School of Environmental Sciences. Please make sure to check the student handbook and familiarise with them. In addition to these generic criteria, the following specific criteria will be used in cases where computer code is part of the work being assessed:

- --------- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mark RangeDescriptionNarrativeMap(s) and/or Dashboard DesignTechnical SkillsInteractive Map/Dashboard Fully Working (required)API Call (required) (A1)
0-15Minimal or no effort, incomplete, or no functionality.Limited or unclear problem and justification.Minimal effort, lacking justification for design choices.Code does not run, no documentation provided.NoNo
16-39Basic functionality with significant issues or missing components.Problem and justification are somewhat unclear or incomplete.Design choices lack depth or clear connection to the dashboard’s aim.Code does not run or produces incorrect output. Some documentation is provided, but it lacks clarity or detail.PartiallyNo
40-49Meets minimum requirements with some functionality and basic clarity.Problem and justification are clear but not well-integrated into the overall framework.Basic design choices are made, and some connection to the interactive map’s (A1) or dashboard’s aim (A2) is present, but the design lacks refinement.Code runs and produces the expected output. Documentation is present but lacks depth or proper formatting.PartiallyNo
50-59Meets expectations with functional output and clear structure.Clear problem identification and justification, but limited integration with other components.Reasonable design choices are made with some level of thought towards usability and presentation.Code runs and produces the expected output. Extensive documentation explaining the logic is provided.PartiallyYes
60-69Good overall quality with functional and thoughtful design.Problem and justification are clear, and some integration with the overall framework is evident.Thoughtful design choices are made and connected to the interactive map’s (A1) or dashboard’s aim (A2), with some justification for interactivity and widgets (A2).Code runs and produces the expected output. Extensive, properly formatted documentation is provided, showing a good understanding of concepts.YesYes
70-79High-quality work with clear evidence of advanced skills and integration of components.Problem and justification are clear and well-integrated with all components of the assignment, creating a cohesive narrative.Excellent design choices are made, with strong connections to the interactive map’s (A1) or dashboard’s aim (A2) and well-justified interactivity (A1 and A2) and widgets (A2).Code runs and produces the expected output. Evidence of advanced skills is demonstrated in the code design.YesYes
80-100Exceptional work with innovative contributions and flawless execution.Problem and justification are excellently presented and fully integrated into a cohesive, professional-quality narrative.Outstanding design choices with creative elements, advanced interactivity, and exceptional attention to detail in connecting the components to interactive map (A1) or the dashboard (A2).Code runs and produces the expected output. Extensive, properly formatted documentation is provided, including novel contributions (e.g., algorithm optimizations, novel methods to improve functionality).YesYes
-
-
-

DOs and DONTs

-
    -
  • Do not include “temporary” maps unless you really need to specifically show something to your reader.
    -
    • -
  • Do not include maps that have no actual differences, apart from few things (e.g. you changed the zoom level).
    • -
  • Mix the accompanying text, in markdown cells, with the code.
    • -
  • Do not include all the text at the beginning.
    • -
  • Provide some theoretical context and motivation to your topic.
    • -
  • Present 2 or 3 NICE maps and the final interactive map (Assignment I) and the one included in your dashboard (Assignment II)
    • -
- - -
- -
- - -
- - - - - - \ No newline at end of file diff --git a/general/assignmentI.html b/general/assignmentI.html deleted file mode 100644 index 8e9b9a1..0000000 --- a/general/assignmentI.html +++ /dev/null @@ -1,756 +0,0 @@ - - - - - - - - - -Assignment I – Web Mapping and Geovisualisation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- -
- -
- - -
- - - -
- -
-
-

Assignment I

-
- - - -
- - - - -
- - - -
- - -
    -
  • Title: Exploring APIs and Interactive Maps in Python.
    • -
  • Type: Coursework.
    • -
  • Due: Thursday March 3rd (2.00 pm) - Week 6.
    • -
  • 50% of the final mark.
    • -
  • Submission on Canvas, .html files only.
    • -
-

Context, Design, Data, and Assemblage

-

In this assessment, you will have the opportunity to explore different sources and combine them in a map that can be explored interactively through a web browser. This assignment requires you to identify a research problem from literature, source relevant data from the web in different formats, assemble them, and document the process. To be successful, you will need to demonstrate your understanding not only of the technical aspects involved in the process but also of the conceptual notions underpinning them. Below are the required components for your submission:

-
    -
  1. Context and Problem: Identify a research problem with a geographical connotation. Discuss concisely recent research around it in physical or human geography (around 7–8 references). Introduce how you will explore and visualise dimensions of the problem (e.g., gentrification, access to healthy food in cities, urban heat islands, etc.).
    2. -
  2. Data and Backend: Draft a list of spatial datasets relevant to your research problem and demonstrate your ability to develop your own API request function in Python. Include datasets containing spatial information or linkable to other spatial sources. Highlight the data/variables worth considering and their role in representing the problem. Demonstrate your understanding of core “backend” web mapping concepts. Include an explanation of how tilesets, client-server architecture, and APIs are implemented and contribute to your map’s functionality.
    3. -
  3. Design: Create Good Looking static maps to represent your datasets, focusing on spatial units (e.g., buildings, cities). Move onto interactive visualisation with folium, incorporating interactivity for categorical and numerical variables. Seek feedback to refine your ideas. Use inspiration from web map examples discussed in the course to ensure effective representation of data.
    4. -
  4. Assemblage: Enhance your map by incorporating widgets for dataset exploration and experimenting with tilesets, such as creating your own in Mapbox. Address design considerations, including the map’s extent, zoom levels, and variable visibility at different zoom levels. Ensure consistency and aesthetic appeal to complete this stage successfully.
    5. -
-
-

Expected Content

-
-

Code

-
    -
  • Introductory Static Maps (2 to 3), presenting the topic and the geographic context.
    • -
  • An API request written by your own.
    • -
  • All the necessary steps for making your API work and for data cleaning/exploration.
    • -
  • An interactive final map. This should be fed with data obtained through the API request.
    • -
-

You CANNOT employ for your main maps the following libraries: Holoviews, Geoviews, and Plotly

-
-
-

Text in Markdown Cells, 1,000 words, distributed across the notebook:

-
    -
  • About 250 words introducing the research problem, the context, and existing recent research on the topic.
    • -
  • About 200 words presenting and motivating the chosen data sources, in relation to your research problem. Here you should engage not only with what data you are using but why and what they bring to the map. Everything should be in the map for a reason.
    • -
  • About 200 words with your description of what your API is, how it works and how it will made your map possible.
    • -
  • About 200 words with a description of how your interactive map works, its components and your design ideas.
    • -
  • About 150 words to summarise your research problem and how you tackled it by means of geovisualisation tools (Conclusion).
    • -
-
-
-
-

Evaulation

-

The assignment will be evaluated based on 3 main pillars, on which you will have to be successful to achieve a good mark:

-
    -
  1. Narrative. The ability to identify and present a research problem, motivate and justify one’s map, as well as the ability to bring each component of the assignment into a coherent whole that “fits together”.
    2. -
  2. Map design abilities. The ability to demonstrate the understanding of geovisualisation and interactivity design principles.
    3. -
  3. Technical skills. The ability to master Python scripting and technologies that allow one to create a compelling map, but also to access interesting and sophisticated data sources.
    4. -
-
-
-

How is this assignment useful?

-

This assessment includes several elements that will help you improve critical aspects of your web mapping skills:

-
    -
  • Design: this is not about making maps, this is about making good maps. And behind every good map there is a set of conscious choices that you will have to think throug to be successful (what map? what data? how to present the data? etc.).
    • -
  • Technology: at the end of the day, building good web maps requires solid understanding of current technology that goes beyond what the average person can be expected to know. In this assignment, you will need to demonstrate you are proficient in a series of tasks manipulating geospatial data in a web environment.
    • -
  • Presentation: in many real-world contexts, your work is as good as it can come across to the audience it is intended to. This means that it is vital to be able to communicate not only what you are doing but why and on what building blocks it is based on.
    • -
- - -
- -
- - -
- - - - - - \ No newline at end of file diff --git a/general/assignmentII.html b/general/assignmentII.html deleted file mode 100644 index ff14a41..0000000 --- a/general/assignmentII.html +++ /dev/null @@ -1,755 +0,0 @@ - - - - - - - - - -Assignment II – Web Mapping and Geovisualisation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- -
- -
- - -
- - - -
- -
-
-

Assignment II

-
- - - -
- - - - -
- - - -
- - -
    -
  • Title: A dashboard that explores a Spatial Dataset.
    • -
  • Type: Coursework.
    • -
  • Due: Thursday May 8th (2.00 pm) - Week 12.
    • -
  • 50% of the final mark.
    • -
  • Submission on Canvas, .html files only.
    • -
-

This assignment requires you to build a dashboard for a spatial data set of your choice. To be successful, you will need to demonstrate your understanding not only of technical elements, but of the design process required to create a product that can communicate complex ideas effectively. There are three core building blocks you will have to assemble to build your dashboard: the main maps(s), base map, and widgets.

-
    -
  1. Context and Problem: Identify a research problem with a geographical connotation. Discuss concisely recent research around it in physical or human geography (around 7–8 references). Introduce how you will explore and visualise dimensions of the problem (e.g., gentrification, access to healthy food in cities, urban heat islands, etc.).
    2. -
  2. The Dashboard. Import your data and start building a dashboard with panel. Think about what you want to show, which interactive elements you will allow the user to access and how they will let them modify the experience of your dashboard. The dashboard must incorporate interactive map(s), besides allowing the user to play with the dataset. Interactive maps should be built with folium or (optionally) with pydeck.
    3. -
  3. The basemap. Design your own basemap through scripting (e.g. assembling a basemap with OpenStreetMap features in a unique layer) or use available TileSets. Think about the data in the background, which colors, the zoom levels that will be allowed, and how it all comes together to create a backdrop for your main message that is conducent to the experience you want to create. Use the basemap to enhance the visualisation experience of the user.
    4. -
  4. Additional widgets. One of the advantages of dashboards in comparison to standard web maps is that they allow to bring elements of analysis to a more finished product. Think about what you want your users to be able to analyse, why, and how that will modify the main map.
    5. -
-
-

Expected Content

-
-

Code

-
    -
  • Introductory Static Maps (2 to 3), presenting the topic and the geographic context.
    • -
  • An API request (optional) data calls, and necessary data cleaning operations.
    • -
  • All the necessary steps for building and refining the funcitoning of your Dashboard with panel.
    • -
  • An interactive final dashboard (one) that also incoporates an interactive map.
    • -
-

You CANNOT employ for your main maps the following libraries: Holoviews, Geoviews, and Plotly

-
-
-

Text in Markdown Cells, 1,000 words, distributed across the notebook

-
    -
  • About 250 words introducing the research problem, the context, and existing recent research on the topic.
    • -
  • About 200 words presenting and motivating the chosen data sources, in relation to your research problem. Here you should engage not only with what data you are using but why and what they bring to the dashboard.
    • -
  • About 200 words for the overall idea of the dashboard. What do you want to communicate? What is the story you want to tell?
    • -
  • About 200 words where you describe your design choices around interactivity, including both cartographic elements (e.g. zooming, panning) as well as additional interactivity built around components such as widgets.
    • -
  • About 150 words to summarise your research problem and how you tackled it by means of geovisualisation tools (Conclusion).
    • -
-
-
-
-

Evaluation

-

The assignment will be evaluated based on 3 main pillars, on which you will have to be successful to achieve a good mark:

-
    -
  1. Narrative. The ability to identify and present a research problem, motivate and justify one’s map, as well as the ability to bring each component of the assignment into a coherent whole that “fits together”.
    2. -
  2. Dashboard and Map(s) design. It is very important to think through every step of preparing this assignment as if it was part of something bigger towards which it contributes. Critically introduce every aspect considered when designing the map(s), by explicitly connecting it to the overall aim of the dashboard. One should clearly and critically describe how they engaged with every design choice (e.g. adding certain widgets or interactivity functions in the dashboard).
    3. -
  3. Technical skills. The ability to master Python scripting and technologies that allow one to create an interactive, informative and compelling (geographic) dashboard, as well as to access interesting and sophisticated data sources.
    4. -
-
-
-

How is this assignment useful?

-

This assignment combines several elements that will help you improve critical aspects of web mapping:

-
    -
  • Design: this is not about making maps, this is about making good maps. And behind every good map there is a set of conscious choices that you will have to think through to be successful (what map? what data? how to present the data? etc.).
    • -
  • Technology: at the end of the day, building good web maps requires familiarity with the state-of-the-art in terms of web mapping tools. In this assignment, you will need to demonstrate your mastery of some of the key tools that are leading both industry and academia.
    • -
  • Presentation: in many real-world contexts, your work is as good as it can come across to the audience it is intended to. This means that it is vital to be able to communicate not only what you are doing but why and on what building blocks it is based on.
    • -
- - -
- -
- - -
- - - - - - \ No newline at end of file