Handle null peak_mass_flow in map components

Updated Map and MapTooltip components to safely handle cases where 'peak_mass_flow' may be null or undefined. This prevents potential runtime errors and ensures consistent tooltip and layer rendering.

Author: reyery

src/features/map/components/Map/Map.jsx

@@ -220,15 +220,15 @@ const useMapLayers = (onHover = () => {}) => {
             data: mapLayers[name]?.edges,
             getLineWidth: (f) =>
               normalizeLineWidth(
-                f.properties['peak_mass_flow'],
+                f.properties?.['peak_mass_flow'] ?? 0,
                 min,
                 max,
                 1,
                 7 * scale,
               ),
             getLineColor: edgeColour,
             getDashArray: (f) =>
-              f.properties['peak_mass_flow'] ? [0, 0] : [8, 4],
+              f.properties?.['peak_mass_flow'] != null ? [0, 0] : [8, 4],
             dashJustified: true,
             dashGapPickable: true,
             extensions: [new PathStyleExtension({ dash: true })],

src/features/map/components/Map/MapTooltip.jsx

@@ -176,9 +176,10 @@ const MapTooltip = ({ info }) => {
         ? Math.round(Number(properties.pipe_DN) * 100) / 100
         : null;
 
-      const peakMassFlow = properties?.peak_mass_flow
-        ? Math.round(Number(properties.peak_mass_flow) * 1000) / 1000
-        : null;
+      const peakMassFlow =
+        properties?.peak_mass_flow != null
+          ? Math.round(Number(properties.peak_mass_flow) * 1000) / 1000
+          : null;
 
       return (
         <div className="tooltip-content">