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

Issue on the Lithology codelist #38

Open
GloaguenBRGM opened this issue Oct 6, 2022 · 8 comments
Open

Issue on the Lithology codelist #38

GloaguenBRGM opened this issue Oct 6, 2022 · 8 comments

Comments

@GloaguenBRGM
Copy link

Hi,
the lithology codelist with terms like granite, schist and so has completely disappeared and his currently remplaced by a very short list of 11 entries (concrete, mine dump, topsoil, ...) that have nothing to do with a lithology codelist.

Thank you in advance for correcting this error.

Regards,
E. Gloaguen, BRGM, the french geological survey.

@arantzaetxebarria arantzaetxebarria added the under analysis A first analysis is being performed label Oct 7, 2022
@arantzaetxebarria
Copy link
Collaborator

Dear @GloaguenBRGM,

Thanks for reporting the issue, an analysis is being done. We will keep you informed about our discoveries, and we will try to provide an answer as soon as possible.

Regards,

Arantza

@arantzaetxebarria
Copy link
Collaborator

Dear @GloaguenBRGM,

The new version of the INSPIRE Registry implements a new way of browsing hierarchical codelist, level by level in the hierarchy.
For example, if you access to granite item, you can see that by accessing higher levels through the Parent, you end up accessing Lithology.

As a result, the whole list of values of the code list is not directly browseable through the INSPIRE Registry UI, only level by level. However, they are directly accessible through the API.

Regards

@arantzaetxebarria arantzaetxebarria removed the under analysis A first analysis is being performed label Oct 7, 2022
@GloaguenBRGM
Copy link
Author

Dear @arantzaetxebarria ,
First, thank you very much for your quick reply.
Second, I have no issue with a hierarchical codelist, nevertheless something is basically wrong in this lithology codelist. Lithos in greek means stone. Thus, various main class of stones (magmatic stones, sedimentary stones, metamorphic stone, ...) should appear at this hierarchical level and this is not the case. Moreover the current list of terms that appears in lithology codelist are not stones....
Regards,
E. Gloaguen

@arantzaetxebarria arantzaetxebarria added the under analysis A first analysis is being performed label Oct 7, 2022
@arantzaetxebarria
Copy link
Collaborator

Dear @GloaguenBRGM,

You may be able to find the values you are looking for within the Lithology XML format, this XML contains all the Lithology related values specified in the Geology TG.

Regards,

Arantza

@GloaguenBRGM
Copy link
Author

Dear @arantzaetxebarria ,

thank you for your message.
From my knowledge, the best way to get the full codelist is from this page https://inspire.ec.europa.eu/register-federation/index.jsp?type=registers
using the filter label tool you will get quickly the html page that contains all the values for a given codelist, example:
https://inspire.ec.europa.eu/register-federation/detail.jsp?type=registers&id=cb0868d7e904d4f1290cfa7627261ffc

Nevertheless, an issue remains in this page https://inspire.ec.europa.eu/codelist/LithologyValue as already mentionned.

Best regards,
eric

@arantzaetxebarria
Copy link
Collaborator

Dear @GloaguenBRGM

You are right, the full codelist is also accessible from this page https://inspire.ec.europa.eu/register-federation/index.jsp?type=registers, but in the same way, XML https://inspire.ec.europa.eu/codelist/LithologyValue/LithologyValue.en.xml or JSON https://inspire.ec.europa.eu/codelist/LithologyValue/LithologyValue.en.json files contain all the values from Lithology. The same as those indicated in the Geology TG https://inspire.ec.europa.eu/id/document/tg/ge .

Now on this page, https://inspire.ec.europa.eu/codelist/LithologyValue the values are present in a hierarchical way, this means that not all values will be visible at the first level, it will be necessary to navigate through each value.

In any case, if you have any further concerns, you can open a change proposal through the corresponding submitting organisation of your country.

Regards,

Arantza

@arantzaetxebarria
Copy link
Collaborator

Dear @GloaguenBRGM

We will proceed to close this issue as the values are accessible by browsing hierarchically. In any case, we are working on improving this hierarchical navigation to make it more accessible to the community.
If you have any suggestions, feel free to share them with us.

Regards,

Arantza

@arantzaetxebarria arantzaetxebarria removed the under analysis A first analysis is being performed label Oct 27, 2022
@juanpelegrina
Copy link

I am reopening the issue to keep track, we need further investigation since the TG document seems to have got a wrong set of values when compared to the IR.

@juanpelegrina juanpelegrina reopened this Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants