Skip to content

OGC API #30

@jokiefer

Description

@jokiefer

Status quo

We provide a RESTful API which does not follow any official specification.

Improvement

The OGC API will be the next step in automatical exchange of data for spatial infrastructures, since it's the first draft for a new specification.

The OGC API has been presented in many videos on YT as well, including a presentation from FOSSGIS 2020 Freiburg,Germany.

The idea of this API follows a modern RESTful design and is therefore extremely interesting!

But since this is just a draft of a final specification, we would have to keep track on changes and maintain them in our system as well

New app

It would be best practice to create a new app ogcApi instead of extending the existing api app. This way we could maintain the code more easily instead of digging through different files, which are not related to the ogc api itself but our regular api.

Specification

It is very important to read and understand the specifications draft before implementation!

All routes have to follow the design and behaviour that is described in there.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: acceptedThis issue has been accepted for implementationstatus: needs milestoneAwaiting prioritization for inclusion with a future MrMap releasetype: featureIntroduction of new functionality to the application

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions