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.

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

New geolocation type to be processed by Cygnus #1833

Open
fgalan opened this issue Mar 12, 2020 · 1 comment
Open

New geolocation type to be processed by Cygnus #1833

fgalan opened this issue Mar 12, 2020 · 1 comment
Labels

Comments

@fgalan
Copy link
Member

fgalan commented Mar 12, 2020

In some use cases, we need to define an attribute meaning location (although the CB doesn't pay attention to it, due to the actual location of the entity is in another attribute) and Cygnus to process that attribute as location.

For instance, we have an entity with two attributes: location (of type geo:json, the actual location of the entity) and areaServer (of type geo:json:extra, thus ignored by CB). Both attributes should be parsed as locations in Cygnus (as the corresponding column in the postgis table is of type location).

However, Cygnus only processes geo:json and geo:point at the present moment. Thus, we should extend the functionality to take also into account geo:json:extra.

NOTE: geo:json:extra is just an example. Maybe there are better alternatives for this literal. The only requirement is that it must not conflit with the ones that Orion uses for geolocation (otherwise Orion will reject the entity, given it only allows one geolocation attribute, more detail: https://fiware-orion.readthedocs.io/en/master/user/ngsiv2_implementation_notes/index.html#limit-to-attributes-for-entity-location)

@fgalan fgalan added the backlog label Mar 12, 2020
@fgalan
Copy link
Member Author

fgalan commented Jun 28, 2024

geo:point is to be removed (#2391)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant