Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

How to understand the response parameter area in the device retrieval API #255

Open
chinaunicomyangfan opened this issue Sep 2, 2024 · 3 comments · May be fixed by #262
Open

How to understand the response parameter area in the device retrieval API #255

chinaunicomyangfan opened this issue Sep 2, 2024 · 3 comments · May be fixed by #262

Comments

@chinaunicomyangfan
Copy link

Problem description
Hi Teams,
About the location retrieval API, we are currently implementing this API and have encountered a problem. Regarding the region in the response parameters (including the type and size of the region), how is it obtained? Is it defined by the operator themselves? Are there any related constraints (such as not allowing the return area to be too large) and whether the actual location of device needs to be within the return area.
@jlurien
Copy link
Collaborator

jlurien commented Sep 2, 2024

Hi @chinaunicomyangfan, the returned area is only restricted to be compliant with the schema. It is up to the implementation to decide between a circle or polygon, but size is not limited, and currently client cannot request a maximum size to be returned, as for age. It is assumed that device is within the returned area (according to the information maintained by the operator), as that is the purpose of the service.

It may be a question to discuss if we should allow customers to define a threshold for a maximum area, similiar to maxAge, so implementations which cannot comply with the requirement do not returned a bigger area. cc @bigludo7

@chinaunicomyangfan
Copy link
Author

If the size of the return area is not constrained, returning a large area does not violate the definition of the API, but for users, this result is obviously meaningless

@bigludo7
Copy link
Collaborator

bigludo7 commented Sep 3, 2024

This is a fair point !

As we have a maxAge having a maxSurface could make sense.
Let's discuss this point for our next release with the team durng Tuesday call.

@bigludo7 bigludo7 linked a pull request Oct 1, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update location-retrieval with add maxSurface management camaraproject/DeviceLocation
3 participants
@jlurien @bigludo7 @chinaunicomyangfan