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

Apply transformations to WKT input according to defined CRS #197

Open
kvndrsslr opened this issue Feb 12, 2019 · 3 comments
Open

Apply transformations to WKT input according to defined CRS #197

kvndrsslr opened this issue Feb 12, 2019 · 3 comments
Assignees
@kvndrsslr
Labels
Priority: Low Status: Available Type: Enhancement
Milestone
Release 2.0

Comments

@kvndrsslr
Copy link
Contributor

GeoSPARQL allows a CRS URL in the start of a WKT string serialization of a geometry.
Currently, LIMES ignores the CRS URL and everything is parsed as default (WGS84).
Should actually implement coordinate transformation based on CRS.

This example code can help.
@kvndrsslr kvndrsslr self-assigned this Feb 12, 2019
@kvndrsslr kvndrsslr mentioned this issue Feb 28, 2019
Merged
@MSherif
Copy link
Contributor

MSherif commented Jul 4, 2019

is this still opened?

@kvndrsslr
Copy link
Contributor Author

It's still a possible enhancement, but has no priority. Right now our partners in SLIPO are aware of this and it is no issue since they do the transformations, if any, and input only WKT literals referencing the same CRS.

@kvndrsslr kvndrsslr added this to the Release 2.0 milestone Jul 2, 2020
@kvndrsslr
Copy link
Contributor Author

Should be handled through plugin system in LIMES 2. Also, should emit warnings when just disregarding the CRS.

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

@kvndrsslr kvndrsslr

Labels
Priority: Low Status: Available Type: Enhancement
Projects
None yet
Milestone
Release 2.0
Development

No branches or pull requests
2 participants
@MSherif @kvndrsslr