Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Is it possible to have more than one layer in the same wms-service of orthophotos? #71

Closed
sebros123 opened this issue Nov 29, 2021 · 11 comments

Comments

@sebros123
Copy link

Hello!

According to the specification "inspire_dataspecification_oi_v3.0" it looks like this:

ortotg

Lantmäteriet has several different orthophotos in the same WMS-service, how should one think here?
Is OI.OrthoimageCoverage a prefix that can be used? Or does the spec say that there should only be one orthophoto per viewing service?

Mvh Sebastian

@sebros123 sebros123 changed the title Is it possible to have more than one layer in the wms-service of orthophotos? Is it possible to have more than one layer in the same wms-service of orthophotos? Nov 29, 2021
@sMorrone
Copy link
Collaborator

sMorrone commented Dec 16, 2021

Dear @sebros123,
it is possible to provide several different orthophotos in the same WMS-service. You can create a "Layer Group" named OI.OrthoimageCoverage and provide the orthophotos as layers of this group. There is no fixed naming rule for the layers in the group.

@sebros123
Copy link
Author

Thank you very much for your answer, it helps us to move forward :)

@sMorrone
Copy link
Collaborator

sMorrone commented Dec 17, 2021

@sebros123
can we proceed with closing this issue? (Clearly you could re-open / open a new one should you have any other questions)

@sebros123
Copy link
Author

@sMorrone
Yes we can do that, thank you

@sebros123
Copy link
Author

Hi again! @sMorrone

The name of the top layer is ‘OI.OrthoimageCoverage’ but the ETF validator still says we have bad layer names for the layers inside the group.

You wrote earlier that "There is no fixed naming rule for the layers in the group". Is it the case that the layers must have the prefix OI.?

Or can ju give me a hint how the layergroup must be configured?

@sMorrone sMorrone reopened this Feb 1, 2022
@sMorrone
Copy link
Collaborator

sMorrone commented Feb 1, 2022

@sebros123
could you provide the WMS service endpoint (so that we can have a look and in case open an issue in the INSPIRE-validator helpdesk)?

@sMorrone
Copy link
Collaborator

sMorrone commented Feb 1, 2022

@jescriu
could you provide your OI expert support to this discussion? Thank you

@sebros123
Copy link
Author

@sMorrone @jescriu

Here is the GetCapabilities-file from the production ortofoto WMS-service.
Orthofoto_Inspire_WMS_TEST.txt

I can ask if our developer can join the diskussion

@fabiovinci
Copy link
Collaborator

fabiovinci commented Feb 2, 2022

Dear @sebros123,

please have a look at this comment which explains the status of this issue.

I tried to validate your WMS in the staging instance, using the local copy of the GetCapabilities document, and there is no error for the "at39-getcapabilities-layer-name" test.

So that means your implementation is right.

Please do a test using the online version of the GetCapabilities document and let us know if everything is ok.

@sebros123
Copy link
Author

@fabiovinci Thank you,

I'll do it and get back to you.

// Sebastian

@jescriu
Copy link
Contributor

jescriu commented Feb 9, 2022

Dear @sMorrone,

Although this issue was originated with a view service related to the the Orthoimagery theme, I think that the overlying problem is related to implementation of view services in general.

Thanks @fabiovinci for pointing to Issue #39 in the helpdesk of the INSPIRE Reference Validator, which is in the pipeline for addressing the problem.

@INSPIRE-MIF INSPIRE-MIF locked and limited conversation to collaborators Aug 25, 2022
@sMorrone sMorrone converted this issue into discussion #124 Aug 25, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants