Remove tile url and attributions

api/src/database/mongoDb/dbSchemas/mapLayersSchema.ts

@@ -95,8 +95,6 @@ export const OneMapLayerData = new mongoose.Schema(
     featureId: String,
     style: StyleSchema,
     legend: [LegendSchema],
-    tileDataUrl: String,
-    tileAttributions: String,
   },
   { _id: false },
 );
@@ -122,8 +120,6 @@ export const MapLayerSchema = new mongoose.Schema({
   layers: [LayerSchema],
   layerOptions: LayerOptionsSchema,
   style: mongoose.Schema.Types.Mixed,
-  tileDataUrl: String,
-  tileAttributions: String,
 });
 
 export const MapLayer = mongoose.model('MapLayer', MapLayerSchema, 'mapLayers');

doc/data-structures/config-files.md

@@ -117,6 +117,8 @@ _or with geodata file provided in folder './initial-data-load/data/{COUNTRY}/geo
   apiUrl: "urlInApiThatReturnsStoredGeodata"
 ```
 
+for returning data from API, but not storing them in the database just use apiUrl. (for example for tile data)
+
 ## mapLayers.yml
 
 This config file is one long array with settings for layers in map. As there are multiple types of layers (regions, points on map, any geometrical objects or even combination of them and tile layers) and also multiple sources of data for one layer, the structure of items in array may vary greatly.
@@ -139,11 +141,6 @@ This config file is one long array with settings for layers in map. As there are
 - **dateText**: description of date, if it should be displayed,
 
 **featureId**: property in Feature in geojson file under which the value for 'featureId' in attributes is stored,
-
-**tileDataUrl**: url of map tile layer data source,
-
-**tileAttributions**: attributions of the tile layer data source,
-
 **metadata**: informations about data in layer, they are shown when you click on info button aside from map layer in layers menu
 
 - **description**:,

frontend/src/ol/staticLayers/layerTypes/tiles.js

@@ -9,8 +9,8 @@ const tileLayer = (layerData) => {
     featureId: layerData.featureId,
     type: layerData.layerType,
     source: new XYZ({
-      url: layerData.tileDataUrl,
-      attributions: layerData.tileAttributions,
+      url: layerData.geoDataUrl,
+      attributions: layerData.metadata && layerData.metadata.geoMetadata && layerData.metadata.geoMetadata.attributions,
     }),
     zIndex: 0,
     layerOptions: layerData.layerOptions,

initial-data-load/src/database/mongoDb/layers.ts

@@ -65,8 +65,6 @@ const oneMapLayerItem = async (data: MapLayerConfigItem) => {
     style: data.style,
     legend: data.legend,
     layerOptions: data.layerOptions,
-    tileDataUrl: data.tileDataUrl,
-    tileAttributions: data.tileAttributions,
   };
 };
 

initial-data-load/src/database/mongoDb/schemas/mapLayersSchema.ts

@@ -79,8 +79,6 @@ const OneMapLayerData = new mongoose.Schema(
     featureId: String,
     style: StyleSchema,
     legend: [LegendSchema],
-    tileDataUrl: String,
-    tileAttributions: String,
   },
   { _id: false },
 );
@@ -100,8 +98,6 @@ const MapLayerSchema = new mongoose.Schema({
   metadata: MetadataSchema,
   timeseries: Boolean,
   layerOptions: LayerOptionsSchema,
-  tileDataUrl: String,
-  tileAttributions: String,
 });
 
 export const MapLayer = mongoose.model('MapLayer', MapLayerSchema, 'mapLayers');

initial-data-load/src/types.ts

@@ -117,8 +117,6 @@ export interface MapLayerConfigItem {
     };
   }>;
   metadata: object;
-  tileDataUrl: string;
-  tileAttributions: string;
 }
 
 // MONGODB //
@@ -166,8 +164,6 @@ export interface MongoDbMapLayer {
     };
   }>;
   metadata: object;
-  tileDataUrl: string;
-  tileAttributions: string;
 }
 
 export interface MongoDbRegionAttribute {