When loading the processed csv into ERDDAP, the geometry column creates an issue. When a user accesses the .geoJson endpoint, ERDDAP adds a geometry column. This results in two geometry columns, which breaks the geoJson specification.
In the end, just remove the geometry field when saving as .csv for ERDDAP.
When loading the processed csv into ERDDAP, the
geometrycolumn creates an issue. When a user accesses the.geoJsonendpoint, ERDDAP adds ageometrycolumn. This results in two geometry columns, which breaks the geoJson specification.In the end, just remove the geometry field when saving as .csv for ERDDAP.