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

Use WKT instead of GeoJSON #78

Open
aaronc opened this issue Dec 6, 2023 · 1 comment · May be fixed by #80
Open

Use WKT instead of GeoJSON #78

aaronc opened this issue Dec 6, 2023 · 1 comment · May be fixed by #80

Comments

@aaronc
Copy link
Member

aaronc commented Dec 6, 2023 •
edited
Loading

GeoSPARQL implementations generally assume that geometries are encoded in Well Known Text (WKT) format. GeoJSON support may be added more broadly in the future with GeoSPARQL 1.1, but for now we should aim to make our geometries queryable by off the shelf RDF databases with GeoSPARQL support which seem to mainly support WKT.
@aaronc aaronc changed the title Use WKT instead of GeoJSOn Use WKT instead of GeoJSON Dec 6, 2023
@aaronc aaronc linked a pull request Dec 6, 2023 that will close this issue
Open
6 tasks
@blushi
Copy link
Member

blushi commented Dec 18, 2023

@blushi to create 1 follow-up issue in regen-web: update location form and map to use wkt.
This issue will be to track any further back-end work for this (and potentially updating the existing data).

@aaronc aaronc mentioned this issue Jan 18, 2024
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.

refactor!: switch from GeoJSON to WKT for GeoSPARQL support regen-network/regen-registry-standards
2 participants
@aaronc @blushi