What version of Parcels are you running?
v4
Is your feature request related to a problem?
Parent models don't always define positions on globe/spherical coordinates. Hard-setting the names of the particle positions to .lon, .lat, and .depth implies that this is indeed the norm. Many high resolution regional simulation use cartesian coordinates and users of these kinds of models often just use x y and z .
Describe the solution you'd like
I would propose that particles use attributes x y and z as the names for the particle position attributes (rather than lon, lat, and depth). This would also mean that the increments in position be recorded as dx, dy, dz.
The interpretation of the meaning of the generic x y and z is in the hands (minds?) of the parcels user and in the units aligned with each dimension (degrees longitude/latitude for spherical coordinates or meters for cartesian).
Describe alternatives you've considered
No response
Additional context
No response
What version of Parcels are you running?
v4
Is your feature request related to a problem?
Parent models don't always define positions on globe/spherical coordinates. Hard-setting the names of the particle positions to
.lon,.lat, and.depthimplies that this is indeed the norm. Many high resolution regional simulation use cartesian coordinates and users of these kinds of models often just usexyandz.Describe the solution you'd like
I would propose that
particlesuse attributesxyandzas the names for the particle position attributes (rather thanlon,lat, anddepth). This would also mean that the increments in position be recorded asdx,dy,dz.The interpretation of the meaning of the generic
xyandzis in the hands (minds?) of the parcels user and in the units aligned with each dimension (degrees longitude/latitude for spherical coordinates or meters for cartesian).Describe alternatives you've considered
No response
Additional context
No response