Mean position as metadata instead of user-defined position?

[PennyHow]

We preference using the user-defined latitude and longitude information (defined in the station config .toml file) in the metadata.

pypromice/src/pypromice/process/L1toL2.py

Lines 67 to 72 in c5613a9

	if hasattr(ds, 'latitude') and hasattr(ds, 'longitude'):
	lat = ds.attrs['latitude'] # TODO Why is mean GPS lat lon not preferred for calcs?
	lon = ds.attrs['longitude']
	else:
	lat = ds['gps_lat'].mean()
	lon = ds['gps_lon'].mean()

However, it may be better to use the mean latitude and longitude from the dataset. Would this affect the metadata drastically?

[BaptisteVandecrux]

Since #294, mean latitude/longitude/altitude are now stored as an attribute in the NetCDF files. The metadata files AWS_sites_metadata.csv and AWS_stations_metadata.csv now contain installation and last valid coordinates. Feel free to reopen if this should be adjusted.