-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation suggestions (pain points) #38
Comments
dimension names are fixed, which is OK because CF documentation states: "This convention does not standardize any variable or dimension names". Must be x,y,z,t. But maybe need to adjust the incoming data. |
Some attributes seem to be defined by these routines. Are they overwriting the ones I define? |
@eldobbins Good call on the There is actually a way around the fixed dimension names. You can pass an axes mapping to many of the pocean functions if you don't want to use the predefined For example: axes = {
't': 'time',
'x': 'lon',
'y': 'lat',
'sample': 'obs',
}
ncd = IncompleteMultidimensionalTrajectory.from_dataframe(df, axes=axes, output=somefile) Will make a file with the dimensions/variables named |
@kwilcox asked me to let him know where documentation would be helpful. If it's OK, I'd like to track it here.
First up, Installation. For instance, I did:
The text was updated successfully, but these errors were encountered: