A checklist of all data for your project

This is a list of all the data that are required to run a project successfully.

Geodesign Hub is a collaboration software with no inherent data or models and all data and content have be linked in to the software.

The Current State: You should have a list of the existing conditions, what works well, who are the key stakeholders, the key institutions in the area.

The Problem: You should have a brief text about “the problem” that you are trying to solve, in addition, a square satellite image of the intended study area helps. This can be taken as a screenshot from Bing or Google maps.

Themes or Systems: Once you have the study area and the geodesign problem finalized, the next step is to finalize the systems that you want to study. We recommend up to 10 systems studied simultaneously.

Once the systems are finalized models and maps need to be prepared using GIS (if available) or can be sketched out as well. Broadly, there are four types of GIS data that can be used:

  1. Evaluation Maps: It is recommended that ten systems be studied simultaneously in a project. Therefore ten evaluation maps need to be constructed in three or five levels using existing data.
  2. Constraints: In some cases there are areas in a design study that cannot and should not be touched or changed, a file is needed that details areas (in polygons) that are constraints on the design.
  3. Boundaries: In some cases, in addition to setting the study area, there might be a need to add administrative, political or jurisdictional boundaries. This is set in a boundaries file that can be uploaded to a project.
  4. Other external data: The tool also enables linking of external data using WMS or WFS services. Usually data such as existing land use, roads, water bodies etc. can be linked to aid in design. These data-files can be in vector (e.g. Geopackage, Shapefile) format (in WGS 1984/EPSG 3857projection)

Files and format: GeoJSON is the standard data format used on Geodesignhub. All files mentioned above should be in GeoJSON.