Null geometry feature makes fitBounds throw null is not an object

• Console: TypeError: null is not an object (evaluating 'bounds.extend').
• The map stays at its initial view and none of the layers appear.
• Exactly 2 of 500 records have geometry: null; the other 498 are valid.

1. Iterate the features and count how many have geometry === null.
2. Call L.geoJSON(f).getBounds() on one null feature and confirm it returns empty bounds.
3. Move fitBounds out of the init chain or wrap it in try/catch to see whether other features also fail.
4. Trace the data source: null geometry usually comes from LEFT JOIN rows or fields that were blanked.
5. Check turf.bbox on the same feature; it returns NaN rather than throwing.

Filter out features without geometry before they reach the render layer while keeping their properties for list views, or synthesise a point from lon/lat when a location is known, then call fitBounds on the filtered set.

Uncaught TypeError: Cannot read properties of null (reading 'lat')
    at L.LatLngBounds.extend (leaflet.js:5)
    at L.Map.fitBounds (leaflet.js:5)

const nulls = fc.features.filter(f => f.geometry === null);
console.log(nulls.length);                   // 2
console.log(nulls[0].properties);            // { id: 517, name: '未定位点' }

• Wrapping the whole init in try/catch, which hides the exception but leaves the layer unadded.
• Assuming turf.bbox tolerates null geometry and passing its NaN result straight to fitBounds.