/
2025-01-15 Population Density Data - Meeting Minutes

2025-01-15 Population Density Data - Meeting Minutes

Owned by Jorge Garcia Hospital
Last updated: Jan 16, 2025
3 min read

CAMARA Population Density Dataย APIย - Follow-up meeting #19 - 2025-01-15

January 15th, 2024

Attendees

Name

Company

Name

Company

@Ludovic Robert

Orange

@Gregory Lindner

Ericsson

@Rafal Artych

DT

@Sachin kumar

VDF

@Surajj Jaggernath

VDF

Doug Hutchinson

Vonage

@violeta.gonzalezfernandez@telefonica.com

Telefonica

@Jorge Garcia Hospital

Telefonica

ย 

Population Density Dataย APIย minutes:ย https://lf-camaraproject.atlassian.net/wiki/display/CAM/Population+Density+Data+API+Minutes

Agenda

  • Approval of previous meeting minutes #17 and meeting agenda

  • Open issues and PRs

    • Issues: #40 #48 #50 #51 #56 #58 #61 #62

    • PR #59 #60

  • Timeline and next steps

  • AoB

Open Issues & PRs

#

Company

Summary

#

Company

Summary

Issue#40

Ericsson

Area Data-type

Issue#48

Telefonica

New release scope

Issue#50

Telefonica

Align with guidelines for async responses

Issue#51

Ericsson

Support time Windows in the past

Issue#61

Telefonica

Include notification ID for callback

Issue#67

Orange

Align API with commonalities errors

PR#60

Ericsson

Include past results in API

PR#64

Telefonica

Include Operation ID

Approval of previous meeting minutes & documentation (1)

Meeting Minutes #18

โ†’ Approved

APIย proposal review (2)

Issue#40

Issue opened in commonalities for the alignment on how to define the area types along all the APIs in CAMARA.

AP:ย provide direct feedback on the commonalities issueย Issue #242. Groups is ok to create a homogeneous definition of the area types, as long as each API can later select granularly which types apply (and not getting obligation to support all the types, or getting involved in a complex data model).

Status: Commonalities closed for circle and polygon, enough for PDD.

AP: To align, TEF

Issue#48

Propose new scope for next release.

Included so far:

Status: Alpha release of commonalities getting ready, weโ€™ll adapt API accordingly

ย 

Issue#50

Include alignment with commonalities for the async response mechanism (and any)

Status: Commonalities closed Analysis+of+Commonalities+0.5.0-alpha.1+changes#Analysis. To start with current alpha1 version and wait for any additional change if needed

AP:

Check callback errors
Check callback async mechanism (as done in 0.1.1 jointly with QoD)
Any other

Issue#51

Support time window for past time frames, historical data.

AP: include use cases in the API scope (readme) and yaml/testplan to ensure API is also aligned

Status:

PR#60

Issue#62

Include error status for callback response if area cannot be processed

Status: Align with geofencing when processing the are (in that case area subscription), in case this is covered there in the callback (and not only in the post response)

AP: check with geofencing, also around the 400/422 in the sync mechanism

Issue#67

Align error with commonalities 0.5

Status:

AP: Orange to include PR

ย 

PR#60

Solving 51

Status: to be reviewed

ย 

PR#64

Solving 61

Status: to be merged, as soon as conflicts are resolved

AoB (4)

Next steps:

  • Close current PRs to freeze API content

  • Align commonalities as expected

  • Release tracker created for 0.2.0, RC to be created before 15/01 (next meeting)

Discussion Summary

#

Summary

Status/conclusion

#

Summary

Status/conclusion

Issue#40

Area Data-type

Telefonica to include PR

Issue#48

New Release Scope

ALL to provide more proposals

Issue#50

Aling with guidelines for async responses

ย 

Issue#51

Support time Windows in the past

Review and merge PR60

Issue#61

Include ID in notification to track request-response

PR to be merged

Issue#67

Align API with commonalities errors

Orange to include PR

Next steps

  1. Scope for next release โ†’ #17

  • Next call will be TBD