Include city codes in our City/Region taxonomy

[patrickkaleta]

Our city/region taxonomy so far only stores the Country it belongs to and the EEA city profile name (which btw is missing in 5-10% of our cities -> @humerh or @therter could this cause any troubles for Emikat our our map/table components?).

We noticed some issues with the calculations in Emikat, which are partly caused by mismatches between City labels (explained here by Heinrich). One solution would be to include city codes in Drupal, so that Emikat can then do the matching based on those city codes.

To do:
@humerh & @negroscuro can you agree on a definition for those city codes, which @negroscuro then makes available, so that @therter can update the Cities/Regions in Drupal using his script. I will then take care of passing these city codes along to Emikat everytime it gets triggered by CSIS.

[negroscuro]

@heinrich, as we discused already for mortality importing in Atos database, indeed you explained to me, how this codes work, so, what about to remove last 2 digits/letters from a city code which corresponds to city outskirts? so I can provide such fixed city codes for CSIS to import. Is this ok?

I just implemented it but just to be sure I would like confirmation from your side.

@therter now mortality layer is providing such reduced city code as well as boundary fo every available city.

[patrickkaleta]

I already added a City code field to our Cities/Region taxonomy (machine name: field_city_code), so that we can store the codes in Drupal. I will now prepare the CSIS helpers module to be able to work with this new field.

[therter]

I have reimported the cities taxonomy with the data from the mortality layer. The field City code is filled, now.

[patrickkaleta]

Ok, from now on the city code is being sent to Emikat with each new Study or Study update, so @humerh you can now do your matching based on the city codes instead of the city names.

FYI: I've also added the city code to our $studyInfo JSON object, just in case that our components should ever need it as well.

Closing this issue, since from Drupal-side everything is done now.