Conversation
|
Think you are mistaken here. The +U|u at the end of a grid does that scaling, but it is not the +u that belongs to -R. So the docs you linked is the right place and should not be added to -R |
|
I added stuff about +U not +u (which was already there). So, where do we document +U? The CookBook is not the right place for it. |
|
Well, first half of cookbook is documentation and the examples etc are cookbook. We have tons of explanations (pen, fill, text, etc) in the technical reference section. We have extensive discussion of netCDF files and how to pull out a named variable, how to scale CPT z-values etc. This is no different (+U|uunit is also used for CPTs). |
|
But we already have +u in -R. Why not have the +U too? Relying in the CookBook to find an obscure -R flag is the same ~= nothing. |
|
In -R, +uk means xmin/xmax/ymin/ymax are projected coordinates given in km and we scale by 1000 and then inverse project to get lon/lat. As grid file modifier, +uk means scale grid xmin/xmax/ymin/ymax by 1000, but no inverting takes place. +u|U is also available for things like -Cmy.cpt+Uk. We can chat about these things at the summit and make a list of tasks that are good things for some of our collaborators to deal with. I also think we should break the cookbook into separate documents: Technical Reference for all this stuff, and Gallery for the examples. |
|
Could this be merged? |
|
We should either merge or close this. Paul was not very favorable because this option applies to more than -R but I still feel that if don't do this partial documentation it won't be mentioned anywhere. |
|
I agree with Paul that this is not the correct place to document -R. Perhaps it's better to document it at line 35 in the same file? |
Fix #7537