MapRequest with more than one DatatypeId

[links-ads-admin]

Original report by Luca Bruno (Bitbucket: lukkia, GitHub: lucabruno91).

---

User shall have the possibility to associate more than one ‘on demand’ layer to a single map request.

Based on Map Request’s frequency, on the bus there will be a message with an update of the layer.

At the moment, all the messages contain update as type

Edit MapRequest table to store the list of DataTypeId.

Edit the body of the map request message according to:

‌

{
    "datatype_id": 36001,
    "start": "2021-09-08T00:00:00.000",
    "end": "2021-09-15T23:00:00.000",
    "geometry": {
        "type": "Polygon",
        "coordinates": [
            [
                [
                    -5.29,
                    36.57
                ],
                [
                    -5.14,
                    36.57
                ],
                [
                    -5.14,
                    36.38
                ],
                [
                    -5.29,
                    36.38
                ],
                [
                    -5.29,
                    36.57
                ]
            ]
        ]
    },
    "frequency": 0,
    "metadata": null
}

‌

[links-ads-admin]

Original comment by Luca Bruno (Bitbucket: lukkia, GitHub: lucabruno91).

---

maprequest_layers table added ref #82

[links-ads-admin]

Original comment by Luca Bruno (Bitbucket: lukkia, GitHub: lucabruno91).

---

MapRequest with more than one DataypeId added ref #82

[links-ads-admin]

Original changes by Luca Bruno (Bitbucket: lukkia, GitHub: lucabruno91).

---

• edited description
• set assignee_account_id to "557058:7cb67940-da6b-4810-91f2-d6abf8b0af67"

[links-ads-admin]

Original changes by Luca Bruno (Bitbucket: lukkia, GitHub: lucabruno91).

---

• edited description

[links-ads-admin]

Original changes by Luca Bruno (Bitbucket: lukkia, GitHub: lucabruno91).

---

• changed state from "new" to "resolved"