Pixel tiling functions for the celestial sphere.
The k
parameter for the HEALPix functions is the
HEALPix order, which can be in the range 0<=k<=29.
This is the logarithm to base 2 of the HEALPix NSIDE parameter.
At order k
, there are 12*4^k pixels on the sphere.
htmIndex( level, lon, lat )
level
(integer): HTM levellon
(floating point): longitude in degreeslat
(floating point): latitude in degreeshealpixNestIndex( k, lon, lat )
k
(integer): HEALPix order (0..29)lon
(floating point): longitude in degreeslat
(floating point): latitude in degreeshealpixRingIndex( k, lon, lat )
k
(integer): HEALPix order (0..29)lon
(floating point): longitude in degreeslat
(floating point): latitude in degreeshealpixNestLon( k, index )
Note: the index
parameter is 0-based,
unlike the table row index special token $index
(a.k.a. $0
), which is 1-based.
So if the HEALpix index is implicitly determined by the table row,
the value $index-1
should be used.
k
(integer): HEALPix order (0..29)index
(long integer): healpix indexhealpixNestLat( k, index )
Note: the index
parameter is 0-based,
unlike the table row index special token $index
(a.k.a. $0
), which is 1-based.
So if the HEALpix index is implicitly determined by the table row,
the value $index-1
should be used.
k
(integer): HEALPix order (0..29)index
(long integer): healpix indexhealpixRingLon( k, index )
Note: the index
parameter is 0-based,
unlike the table row index special token $index
(a.k.a. $0
), which is 1-based.
So if the HEALpix index is implicitly determined by the table row,
the value $index-1
should be used.
k
(integer): HEALPix order (0..29)index
(long integer): healpix indexhealpixRingLat( k, index )
Note: the index
parameter is 0-based,
unlike the table row index special token $index
(a.k.a. $0
), which is 1-based.
So if the HEALpix index is implicitly determined by the table row,
the value $index-1
should be used.
k
(integer): HEALPix order (0..29)index
(long integer): healpix indexhealpixNestToRing( k, nestIndex )
Note: the nestIndex
parameter is 0-based,
unlike the table row index special token $index
(a.k.a. $0
), which is 1-based.
So if the HEALpix index is implicitly determined by the table row,
the value $index-1
should be used.
k
(integer): HEALPix order (0..29)nestIndex
(long integer): pixel index in NEST schemehealpixRingToNest( k, ringIndex )
Note: the ringIndex
parameter is 0-based,
unlike the table row index special token $index
(a.k.a. $0
), which is 1-based.
So if the HEALpix index is implicitly determined by the table row,
the value $index-1
should be used.
k
(integer): HEALPix order (0..29)ringIndex
(long integer): pixel index in RING schemehealpixK( pixelsize )
k
value (also variously known as order, level, depth)
is the logarithm to base 2 of the
Nside parameter.
pixelsize
(floating point): pixel size in degreesk
healpixResolution( k )
k
This k
value is the logarithm to base 2 of the
Nside parameter.
k
(integer): HEALPix order (0..29)healpixSteradians( k )
k
(integer): HEALPix order (0..29)healpixSteradians(5) = 0.0010226538585904274
4*PI/healpixSteradians(0) = 12.0
healpixSqdeg( k )
k
(integer): HEALPix order (0..29)healpixSqdeg(5) = 3.357174580844667
round(12 * healpixSqdeg(0)) = 41253
steradiansToSqdeg( sr )
The unit sphere is 4*PI steradians = 360*360/PI square degrees.
sr
(floating point): quantity in steradiansround(steradiansToSqdeg(4*PI)) = 41253
sqdegToSteradians( sqdeg )
The unit sphere is 4*PI steradians = 360*360/PI square degrees.
sqdeg
(floating point): quantity in square degreesround(sqdegToSteradians(41253)/PI) = 4
htmLevel( pixelsize )
level
parameter suitable for a given
pixel size.
pixelsize
(floating point): required resolution in degreeshtmResolution( level )
level
(integer): HTM depthSQDEG