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

Implement spatial extent filter support in API V2 #162

Open
Samweli opened this issue Apr 28, 2021 · 0 comments · May be fixed by #169
Open

Implement spatial extent filter support in API V2 #162

Samweli opened this issue Apr 28, 2021 · 0 comments · May be fixed by #169
Assignees
Labels
size: 5 Takes between half-day and a full day (four to eight hours) to do type: enhancement New feature or request

Comments

@Samweli
Copy link
Collaborator

Samweli commented Apr 28, 2021

Looking at the API V2 implementation here GeoNode/geonode@44470b9 it seems the spatial extent filter can be used by passing extent parameter in the API V2 layers fetching endpoint without using the filter{} parameter.

example
https://master.demo.geonode.org/api/v2/layers?extent=-10,-10,-1,-1

returned layers

{
    "links": {
        "next": "https://master.demo.geonode.org/api/v2/layers?extent=-10%2C-10%2C-1%2C-1&page=2",
        "previous": null
    },
    "total": 79,
    "page": 1,
    "page_size": 10,
    "layers": [
        {...
@ricardogsilva ricardogsilva added size: 5 Takes between half-day and a full day (four to eight hours) to do type: enhancement New feature or request labels May 5, 2021
@ricardogsilva ricardogsilva added this to the Beta release milestone May 5, 2021
@Samweli Samweli linked a pull request May 11, 2021 that will close this issue
@ricardogsilva ricardogsilva removed this from the Beta release milestone Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size: 5 Takes between half-day and a full day (four to eight hours) to do type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants