Since that, open feature classes have been rethought and new values set to database.
For example METS will not be published as open data.
New feature classes are added in LTJ every now and then, and their open data_values are managed straight in database.
-> “set_open_feature_classes” should be eliminated so that it doesn´t set/change open_data values in any situation later.
Earlier: During delelopment, field “open_data” was added in database to define feature classes that can be published as open data (in REST API). And True values were set to selected feature classes: https://github.com/City-of-Helsinki/ltj/blob/master/nature/migrations/0004_open_feature_classes.py
Since that, open feature classes have been rethought and new values set to database. For example METS will not be published as open data. New feature classes are added in LTJ every now and then, and their open data_values are managed straight in database.
-> “set_open_feature_classes” should be eliminated so that it doesn´t set/change open_data values in any situation later.