Incorrect cntbn.cc values

[joewdavies]

It seems that some cntbn features do not have the correct cc property:

I discovered this while testing CSS in eurostat-map by targeting and hiding boundary elements that had 'oth' but not 'co' or 'cc':

            .em-bn-oth:not(.em-bn-co):not(.em-bn-cc) {
                stroke-width: 0 !important;
            }

It would seem that (at least for NUTS2) all cntbn have cc set to F

[hannesaddec]

Which exact file is that on ? depends on the answer it might be for Mike or Uldis

[joewdavies]

This file:
https://raw.githubusercontent.com/eurostat/Nuts2json/master/pub/v2/2024/3035/60M/2.json

Some example IDs in cntbn where this occurs are 131 and 156.

[hannesaddec]

1. in gisco distribution V2 in the column CC-FLAG I see F and T 2. if I load the designated file from nut2json into QGIS F and T is there. see screenshot 3. I can not find the empty segments - see screenshot Are you sure that’s in the data and not an artifact from the applied code in the browser ? ***@***.*** ***@***.*** ***@***.*** From: Joe Davies ***@***.***> Sent: Monday, November 18, 2024 10:55 AM To: eurostat/Nuts2json ***@***.***> Cc: REUTER Hannes (ESTAT) ***@***.***>; Comment ***@***.***> Subject: Re: [eurostat/Nuts2json] Incorrect cntbn.cc values (Issue #45) This file: https://raw.githubusercontent.com/eurostat/Nuts2json/master/pub/v2/2024/3035/60M/2.json<https://urldefense.com/v3/__https:/raw.githubusercontent.com/eurostat/Nuts2json/master/pub/v2/2024/3035/60M/2.json__;!!DOxrgLBm!BbXVNB0uI90gSTqW_Y4j9Evp9m99rruFFzS9ZU_OPh2FXerso5krVddDhMyOSoh0CbyKo3zuInhPY8tA6-8poKR0niSJnGw$> Some example IDs in cntbn where this occurs are 131 and 156. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/eurostat/Nuts2json/issues/45*issuecomment-2482467491__;Iw!!DOxrgLBm!BbXVNB0uI90gSTqW_Y4j9Evp9m99rruFFzS9ZU_OPh2FXerso5krVddDhMyOSoh0CbyKo3zuInhPY8tA6-8poKR0doS6y7g$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ADE7MMJ6MBCNZ7EBMUJQXW32BG2PRAVCNFSM6AAAAABR4WXMKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSGQ3DONBZGE__;!!DOxrgLBm!BbXVNB0uI90gSTqW_Y4j9Evp9m99rruFFzS9ZU_OPh2FXerso5krVddDhMyOSoh0CbyKo3zuInhPY8tA6-8poKR0w1Dtkig$>. You are receiving this because you commented.Message ID: ***@***.***>

[joewdavies]

1. They are incorrect (please read the issue carefully).
   

2. No, the point is that they are incorrect.
   

3. I dont know what you mean by empty segments.

4. Yes, I am sure.

Please refrain from filling comments with emails. Its messy! Also, you did not attach a screenshot.

[joewdavies]

Michael is aware of the issue and will fix it.