Skip to content

API description review finding #121

Description

@MarkusKuemmerle

Problem description
CAMARA Outreach team is reviewing all API descriptions on the CAMARA website using a checklist.

Possible evolution
In case of findings an issue is opened to ask the Sub Project to enhance the API description in the Wiki, and then open an issue at the Marketing repo so that the Outreach team then can update the website.

Alternative solution

Additional context

Findings in Population Density Data:

  • In the first section of the API Description there is a line break after the first sentence which looks bad.
  • A quantitative example illustrating density levels would strengthen the documentation.
  • Use Case section: Please check if you can link exisiting use cases in the GSMA use case library
  • Benefits: Change "Operational efficiency" to "Operational Efficiency"
  • The image should visualize the most interesting use case to attract customers and developers. Please provide us instructions how such a visual should be built and look like. We ask the LF creative team to create the visual. You can put the instructions also in the wiki page below the visual.
  • Location category: Some descriptions could include more explicit discussion of location accuracy, data freshness, and privacy constraints, which are important selection criteria for developers.

Activity

  1. albertoramosmonagas commented on May 19, 2026

    @albertoramosmonagas
    Contributor

    Hi @MarkusKuemmerle. I have prepared a proposal for review by the Sub Project owners (@camaraproject/population-density-data_codeowners) based on the guidelines created by the Marketing team: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/808452114/Population+Density+Data+API+description+v2

    For Population Density Data, I suggest updating the API description to make it more developer-centric and focused on anonymized, aggregated population density estimations for a given area and time interval.

    I also suggest positioning drone/SORA ground risk assessment as the primary use case, since it is the most differentiated and telco-specific scenario, while keeping emergency response, urban planning and event management as additional examples.

    The proposal also updates the Use Cases and Benefits sections, includes the requested capitalization change to “Operational Efficiency”, and recommends replacing the current image with a workflow-style visual showing drone route planning using Population Density Data before flight authorization.

    The visual should represent the flow from defining a flight area and time window, calling the API through Open Gateway, receiving density estimations, and using the result to support safer flight decisions and ground risk assessment.

    Suggested visual concept: “Drone route planning using population density before flight authorization”. The visual should show a simple developer workflow where a drone operator or U-space application defines a flight area and time window, calls the CAMARA Population Density Data API through Open Gateway, receives anonymized and aggregated grid/cell-based population density estimations, and uses them to decide whether to proceed with the planned route, choose an alternative route, change the time window, apply mitigations or reject the flight plan. The image should avoid individual tracking, people/device-level data or a generic city heatmap, and instead emphasize a privacy-preserving telco API supporting safer drone operations and SORA-related ground risk assessment.

  2. albertoramosmonagas commented on Jun 23, 2026

    @albertoramosmonagas
    Contributor

    Any comments on the new version? @sachinvodafone, @maheshc01

  3. jgarciahospital commented on Sep 14, 2026

    @jgarciahospital
    Collaborator

    Close as continued in camaraproject/Marketing#88

  4. MarkusKuemmerle commented on Sep 15, 2026

    @MarkusKuemmerle
    ContributorAuthor

    Website updated 15.09.2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions