-
Notifications
You must be signed in to change notification settings - Fork 1
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
Describe apis and components #35
Conversation
* parameterise the profile of the geometry representation for a Loc-I Feature (geometry of a feature with a resolution in metres, bounding box, centroid, simplified vs. complex geom, projection/CRS) | ||
|
||
![Geometry Data Service architecture](images/geometry-data-service.png "Geometry Data Service architecture") | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could put a GDS API over DGGS service?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably could... do you mean over a DGGS engine? GA have an example here:
http://ec2-52-63-73-113.ap-southeast-2.compute.amazonaws.com/AusPIX-DGGS-dataset/ausPIX/R78523
I think we could explore - it would enable interfaces to be standardised, though we'd need to think about how we interface a DGGS engine vs. Postgres DB.
geometry-data-service.md
Outdated
|
||
## Find the respective feature(s) from the geometry | ||
|
||
Given a geometry description, we can follow links back to respective geometry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to the associated feature ?
updating diagrams to add ld apis in system overview