Map web page reports invalid latitude/longitude values in EMSL MONet data

[eecavanna]

I visited the map web page tonight and noticed it showed a blank, white page. I checked the web browser's DevTools and saw a couple error messages related to latitude/longitude in EMSL MONet data. I suspect this has to do with the values in monet_samples_schema-9-16-2025.json being nested within a coordinates object instead of being at the top level. The map web page looks for them at the top level of each object.

CC: @JamesCarrPNNL, @madettmann

[eecavanna]

I think the fix will be pretty straightforward. I'll start working on this now (editing the JavaScript code, not the data file).

[eecavanna]

I implemented a fix in PR #112 (ready for review/merge).

[JamesCarrPNNL]

Just adding that this discussion happened towards the end of the day and it was concluded that the data should follow the schema format going forward- that was the reason for the nesting.

[eecavanna]

Thanks, @JamesCarrPNNL.

@shreddd and I may pair on BERtron stuff later today (on the parts of the BERtron system that are downstream from the data source-specific ingest scripts we worked on during the hackathon).

One of the things we might work on is updating the map to pull data from either schema-compliant files (like this) or from a new BERtron API endpoint (TBD) that returns data, maybe in a map-optimized format.

I think this experience of updating the map web page to handle the schema-compliant monet_samples_schema-9-16-2025.json file will come in handy in our decision-making and, if we end up taking the former approach, our coding, too.