| Sun Oct 26 15:18:03 2014 by Ron Vantreese |
| I discovered this option: -pprojection Specifies projection: m = Mercator (default) p = Peters q = Square s = Stereographic o = Orthographic g = Gnomonic a = Area preserving azimuthal c = Conical (conformal) M = Mollweide S = Sinusoidal h = Heightfield i = Icosahedral f = Find match, see below When trying it (-ph) I noticed a strange behavior. It doesn't create a BMP image. Instead it creates a matrix of numbers. When I processed the numbers it became a round image of heights with orthographic projection. I wasn't able to change the projection shape by adding -pq. So.. how to handle this? |
| Tue Nov 4 08:37:29 2014 by Torben |
| Currently, orthographic is the only option for heightfields. I intended it for maps of local areas, where the choice of projection does not matter very much. I will consider making heightfield a separate option that can be added to any projection. When I get time. |
| Tue Nov 4 18:21:49 2014 by Ron Vantreese |
| Thanks for considering. And what are the minimum/maximum values of **heights? I know it's capable of handling the range from -2 billion to +2 billion. But what range is heightfield() using? |
| Tue Nov 4 21:35:30 2014 by Ron Vantreese |
| The more I read, the more I know. :) Your Manual.txt says it ranges from -1.2 million to +1.2 million. |
| Tue Nov 11 13:30:02 2014 by Torben |
| I have now changed heightfield from a projection option to an output format option: -H will change the output format from a bitmap to a heightfield. So -po -H corresponds to the old -ph and -pM -H makes a heighfild map using the Mollweide projection. |
| Tue Nov 11 15:22:05 2014 by Ron Vantreese |
| :) :D Yay! I'll make those options available in the GUI too. |