Currently there are multiple config items that use Lat and Long related to a spot:
NOAA ERDDAP Sea Surface Temperature (SST) and DarkSky both use Lat/Lon pairs to access data.
ERDDAP is more sensitive to fidelity of lat/lon and may sometimes return a null sea surface temperature. DarkySky is less fussy and will return the nearest forecast data...
Based on options for global tide data, that will also use Lat/Long to pull data.
SO...standardize for config and directions.
Proposed:
spotLat - Latitude
spotLong - Longitude
These coordinates will then be used to access DarkySky, ERDDAP, and Tide data...hopefully. Needs testing and error case discovery.
Currently there are multiple config items that use Lat and Long related to a spot:
NOAA ERDDAP Sea Surface Temperature (SST) and DarkSky both use Lat/Lon pairs to access data.
ERDDAP is more sensitive to fidelity of lat/lon and may sometimes return a null sea surface temperature. DarkySky is less fussy and will return the nearest forecast data...
Based on options for global tide data, that will also use Lat/Long to pull data.
SO...standardize for config and directions.
Proposed: spotLat - Latitude spotLong - Longitude
These coordinates will then be used to access DarkySky, ERDDAP, and Tide data...hopefully. Needs testing and error case discovery.