Developer Friendlyness use case - Geonovum/ogc-api-testbed GitHub Wiki

Developer Friendlyness is a term introduced by topic3 of the geo4web testbed. It is an indication how much time is needed so any unaware web developer is able to make his first successful call to the service.

This use case aims to set up a service including documentation to evaluate how (non spatial) developers will be able to understand and bind to (or are blocked by) an OGC API Features service. Conventions such as registering the service at api communities can be success factors here.

The default GeoJSON encoding of OGC API for example is a bit an awkward format, especially if the properties object of the item is not modelled out in YAML. Providig a json-ld encoding of the item could be an interesting alternative. But how do you make the developer aware that both json encodings exist?