CAMARA Population Density Data API - Follow-up meeting #17 - 2024-11-20
November 20th, 2024
Attendees
Name | Company |
|---|---|
Population Density Data API minutes: https://lf-camaraproject.atlassian.net/wiki/display/CAM/Population+Density+Data+API+Minutes
Agenda
Approval of previous meeting minutes #15 and meeting agenda
Open issues and PRs
Issues: #40 #48 #50 #51
PR
Timeline and next steps
AoB
Open Issues & PRs
# | Company | Summary |
|---|---|---|
Ericsson | Area Data-type | |
Telefonica | New release scope | |
Telefonica | Aling with guidelines for async responses | |
Ericsson | Support time Windows in the past | |
Telefonica | Add linting rules | |
Orange | Make the API more developer friendly | |
Orange | Change maxPplDensity, minPplDensity and pplDensity datatype |
Approval of previous meeting minutes & documentation (1)
→
API proposal review (2)
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:
Propose new scope for next release.
Included so far:
Include alignment with commonalities for the async response mechanism.
Status:
Support time window for past time frames, historical data.
Status:
Include linting rules to the API repo, and adapt required actions to clean-up code (both included in https://github.com/camaraproject/PopulationDensityData/pull/55 )
Status:
Easing code parameters and polymorphic formats
Status:
Value format (double/integer) for density data
Status:
AoB (4)
Next steps:
Discussion Summary
# | Summary | Status/conclusion |
|---|---|---|
Area Data-type | ALL to provide feedback into commonalities issue | |
New Release Scope | ALL to provide more proposals | |
Aling with guidelines for async responses | ||
Support time Windows in the past |
Next steps
Scope for next release → #17
Next call will be TBD