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

Data check error "LABEL_SELFREF" not detected #318

Closed
michihdeu opened this issue Apr 28, 2020 · 4 comments · Fixed by #497
Closed

Data check error "LABEL_SELFREF" not detected #318

michihdeu opened this issue Apr 28, 2020 · 4 comments · Fixed by #497
Labels
data quality datacheck LABEL_SELFREF This is a temporary tag, as several open issues concern this specific datacheck. pending

Comments

@michihdeu
Copy link
Contributor

I had some cases where LABEL_SELFREF where not detected in FRA-IDF and FRA-GES.
I guess it's in combination to the usage of banners for the French D routes.

  • Plain D906 was not detected.
  • Plain D112 was not detected.
  • Plain D120 was not detected.
  • D60 was not detected in D60/D108_W and D60/D108_E.
  • But D33 in D8/D33 was detected!?
@yakra
Copy link
Contributor

yakra commented Apr 28, 2020

  • Plain D906 was not detected.
  • Plain D112 was not detected.
  • Plain D120 was not detected.

if '/' in w.label and r.route[-1].isdigit():

These labels don't contain a /, so we skip over that section of code.

# now the remaining checks
if selfref_found or r.route+r.banner == w.label or re.fullmatch(r.route+r.banner+'[_/].*',w.label):

selfref_found is unchanged, still False. Thus the banner is required to match, and these non-banner "banners" of -54 & -78 are not found in the labels, so nothing else happens.


  • D60 was not detected in D60/D108_W and D60/D108_E.

This label contains a /, so we do enter into the first big if block, but all the checks therein only scan the label starting after the /, so selfref_found remains False and we proceed as before.


  • But D33 in D8/D33 was detected!?

Here, D33 is after the slash.

if w.label[w.label.index('/')+1:] == r.route:
selfref_found = True

And badabing!


Implementing a "fix" for this would require ignoring a route's banner field, which would mean breaking every case where a bannered route's point's label contains its unbannered parent.
...to which I emphatically say Nope! :)

...unless we added in some kind of FRA-specific workaround?

select distinct banner from routes where region like 'FRA%';
select distinct banner from routes where systemName like 'fra%';

It looks like the only banners used in FRA are department numbers.
This makes me bristle a bit though; it just seems like a kluge...

@yakra yakra added the LABEL_SELFREF This is a temporary tag, as several open issues concern this specific datacheck. label Nov 15, 2020
@michihdeu
Copy link
Contributor Author

@michihdeu
Copy link
Contributor Author

@yakra
Copy link
Contributor

yakra commented Nov 15, 2021

...unless we added in some kind of FRA-specific workaround?
...
This makes me bristle a bit though; it just seems like a kluge...

A bit more palatable: Ignore Banners beginning with -.
Right now, these are only used for French department numbers.
Would just have to ensure that any future uses of -XX banners are a similar "non-banner" usage.


Marked FP now:
frahdf.d093962cam;D901/D939;;;LABEL_SELFREF;

  • Currently flagged because after-slash checks still ignore banners.
  • Phase 1 gets rid of it: same route + same "banner"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data quality datacheck LABEL_SELFREF This is a temporary tag, as several open issues concern this specific datacheck. pending
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants