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

Geographic datatypes should not be assigned to string category #338

Closed
mdesalvo opened this issue May 28, 2024 · 1 comment
Closed

Geographic datatypes should not be assigned to string category #338

mdesalvo opened this issue May 28, 2024 · 1 comment
Assignees
@mdesalvo
Labels
bug Indicates a glitch in existing logics, causing crashes or any unexpected behaviour
Milestone
v3.12.0

Comments

@mdesalvo
Copy link
Owner

Being semantic datatypes, GeoSPARQL geometries should not be assigned to string category: we should assign them to a new specific geographic category so that they are not threated and compared as strings anymore but rather as true geographic entities.
@mdesalvo mdesalvo added the bug Indicates a glitch in existing logics, causing crashes or any unexpected behaviour label May 28, 2024
@mdesalvo mdesalvo added this to the v3.12.0 milestone May 28, 2024
@mdesalvo mdesalvo self-assigned this May 28, 2024
@mdesalvo
Copy link
Owner Author

Addressed with commits 26266cf and 737b91a

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

@mdesalvo mdesalvo

Labels
bug Indicates a glitch in existing logics, causing crashes or any unexpected behaviour
Projects
None yet
Milestone
v3.12.0
Development

No branches or pull requests
1 participant
@mdesalvo