Infrastructure documentation

Infrastructure Documentation

The software has 2 main parts:

The Frontend:

• The front facing interface of the software built with ReactJS.

• The code's repository is at WB-rezoning-explorer.

• The frontend uses MapBox to display the map.

The Backend:

• The backend of the application providing access to a list of API calls that can be explored at API-docs

• The backbend's code is at WB-rezoning-explorer-api

Backend architecture:

Depending on the API calls made, some different parts of the infrastructure will be triggered

Export endpoint:
The backend will put a request into the SQS export queue. A separate queue processing code will process the export request and in the meantime an export id will be returned to the caller. The caller waits asynchronously for the export to finish and investigates the export progress using the API end point '/v1/export/status/{id}'

Filter endpoint: Will take a tile from a dataset stored in the data S3 bucket and apply filters to it and return a Tile.

Zone, LCOE, score endpoint: Will do same calculations on an area using data stored in the data S3 bucket. For a detailed description of calculations please refer to the REZone User Guide

Layers endpoint: Will return the list of layers or a tile from that layer.

Additional dependencies:

• Airtable: A table that stores IRENA dataset needed by the application.

• Vector Tile Server: Some vector tile layers are hosted in this address.

Software components:

• Frontend app server.
• Backend API server.
• AWS SQS queue.
• AWS S3 Export bucket.
• AWS S3 Data bucket.
• AWS SQS queue processor (rezoning-explorer-api/export/export.py).
• Airtable: IRENA dataset.
• Vector Tile Server: Vector tiles server.