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

Problem with the feature catalogue example #198

Closed
heidivanparys opened this issue Apr 12, 2019 · 3 comments
Closed

Problem with the feature catalogue example #198

heidivanparys opened this issue Apr 12, 2019 · 3 comments
Assignees
Labels
OGC API: Common Issue related to general resources or requirements (see #190) Part 1: Core Issue related to Part 1 - Core progress: pull request available

Comments

@heidivanparys
Copy link
Contributor

Recommendation 7 states the following:

image

So, an example of a resource that describes the dataset (and therefore, as a consequence, also the dataset distribution) is a feature catalogue.

However, in the example provided later on, a feature catalogue is given as an example of a resource that describes a feature collection, not a dataset:

image

@cportele
Copy link
Member

I think the example is consistent with the text. The recommendation states:

  • If a resource describes the dataset, the link should be in the links object on the top-level.
  • If a resource describes a collection in the dataset (in this case the buildings), the link should be in the links object of the collection.

In the example, the feature catalogue is just about buildings and thus in the links object of the building collection object while the XSD is for the whole dataset and therefore in the links object at the top.

@heidivanparys
Copy link
Contributor Author

In the example, the feature catalogue is just about buildings and thus in the links object of the building collection object while the XSD is for the whole dataset and therefore in the links object at the top.

The example may be too simple in order to be able to illustrate the difference between a dataset, distribution and a feature collection? As both the dataset (distribution) and the feature collection are about buildings:

This document uses a simple example throughout the document: The dataset contains buildings and the server provides access to them through a single feature collection ("buildings")

I think the main reason for my confusion is that normal practice where I work is to consider a feature catalogue as a description of a data set, and not to relate a feature catalogue to only to one of the distributions of the dataset (GML, SHP, WFS, ...) or to a subset of the features in a dataset.

Resources associated with dataset and distribution

Of course the WFS standard should not dictate how to organize data, metadata and related resources. On the other hand, if many others use the same way of doing this, it may confuse other people than me too.

@cportele
Copy link
Member

OK, it is clearly not the idea to confuse, so probably the easiest is to simplify the example by removing the feature catalogue. It is an example after all and the feature catalogue itself is irrelevant, at least for the specification.

The topic of which descriptive metadata should be associated with which resource (in order to be useful to users / developers) is still a relevant topic, but not something for the Core.

@cportele cportele added Part 1: Core Issue related to Part 1 - Core OGC API: Common Issue related to general resources or requirements (see #190) labels Apr 15, 2019
@cportele cportele self-assigned this Apr 15, 2019
@cportele cportele added this to the Part 1, Second Draft Release milestone Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OGC API: Common Issue related to general resources or requirements (see #190) Part 1: Core Issue related to Part 1 - Core progress: pull request available
Projects
Development

No branches or pull requests

2 participants