CAMARA Population Density Data API - Follow-up meeting #4 - 2024-03-20
March 20th, 2024
Attendees
Gregory Liokumovich (Ericsson) |
Rafal Artych (DT) |
Violeta Gonzalez Fernandez (Telefonica) |
Sachin Kumar (Vodafone) |
Jorge Garcia Hospital (Telefonica) |
Population Density Data API minutes: https://wikilf-camaraproject.camaraprojectatlassian.orgnet/wiki/display/CAM/Population+Density+Data+API+Minutes
Agenda
- Approval of previous meeting minutes #3 and meeting agenda
- Open issues and PRs
- PRs: #5
- Issues: #6 #7 #10
- Initial algorithm proposal review
- Timeline and next steps
- AoB
Open Issues & PRs
ITEM | WHO | DESCRIPTION |
---|---|---|
PR#5 | Telefonica | Initial contribution of the Population Density API spec |
Issue#6 | Telefonica | Information in water zones discussion |
Issue#7 | Telefonica | Default and limit values for the API Characteristics |
Issue#10 | Telefonica | Management of "big" responses |
Approval of previous meeting minutes & documentation (1)
API proposal review (2)
Different discussions raised during the API review:
Issue#6 Information in water zones: Operators and therefore API can only provide data of those zones where it is operating. Full water or hybrid scenarios to be covered.
Status parameter is proposed for handling both situations:
- Partial response, if only some areas are not included in the response due to the
- Empty response, if no area is managed by operator and, therefore, no information can be provided.
Proposed values (to be agreed):
→ Values for status (initial proposal): "enum": ["
OK_SUPPORTED_AREA" → "AREA_SUPPORTED", "PART_OF_ AREA_NOT_SUPPORTED", "AREA_NOT_SUPPORTED"]
Agreed WF
→ offline discussion on partial responses.
...
Initial algorithm proposal (3)
Population Density API - Algorithm.pdf
Feedback:
Agreed WF
→ Issue to be opened to keep the discussion offline.
Discussion
Item | Discussion |
---|---|
PR#5 | Initial contribution of the Population Density API spec → To be merged into main to continue discussion |
Issue#6 | Information in water zones discussion → Agreed status values, open mechanism for partial result |
Issue#7 | Default and limit values for the API Characteristics → Open on level and max area |
Issue#10 | Management of "big" responses → Open discussion on mechanism |
AoB | - |
Next steps
- Feedback on algorithm proposal→ Follow-up meeting #5
- Feedback on the big responses management #5
- RC API spec agreement → Follow-up meeting #6
...