Daily and latest GeoJSON does not agree with csv files?

[smalers]

I've added the SNODAS daily GeoJSON to the Poudre Information Website using the LatestDate file. Although the pattern of precipitation looks reasonable, I'm not sure that the map properties are correct. I've been looking at the map in the SNODAS application compared to the layer in Poudre Basin Information, for example for CLAFTCM.

The existing web application is as follows:

The file included in Poudre Basin Information website is:

The CSV files agree with the displayed maps in the legacy application and the graphs. The application processes the CSV into the layer attributes so that makes sense. This needs to be checked ASAP to make sure that the information products are accurate and consistent. Unfortunately, it is cumbersome working with files on S3 because the AWS console pages the files and I'm having some issues with gutil ls running on Windows.

[smalers]

I compared the SnodasStatisticsByDate_LatestDate.geojson and SnodasStatisticsByDate_LatestDate.zip (shapefile) and the shapefile agrees with the csv but the GeoJSON is different. There might be something going on where GeoJSON values are recomputed for its projection and shapefile is using UTM Zone 13. However, even if that were done the snow coverage should be the same and it is not. I updated the Poudre Basin Information workflow to process the shapefile into GeoJSON so that the map is consistent with CSV data. We need to regenerate the GeoJSON to use the latest format and at that point can check the values in the GeoJSON file. Keep this issue open as a reminder to deal with that.