[raster] Some functions are missing in the XML reference

[pracine]

These functions should added to the XML documentation:

-st_bandhasnodatavalue

-st_bandpath

-postgis_raster_lib_version

-postgis_raster_lib_build_date

It would also be good to separate functions accessing (or setting) RASTER metadata from functions accessing (or setting) BAND metadata from function accessing or setting PIXEL values. Somehow the same way they are organized in rtpostgis.sql

[robe]

Pierre,

Have these documented, but not sure how to break out the sections. Broke some out. Take a look and make suggestions.

​http://www.postgis.org/documentation/manual-svn/RT_reference.html

Not sure where to put the value ones. The only accessor we have is ST_Value and the others I would consider processing or output. But its a bit of a grey zone.

In the windows download - also have the wktraster_comments.sql (to install the help in PostgreSQL). ​http://www.postgis.org/download/windows/experimental.php

Haven't added it as a make target in postgis yet. Mostly cause not familar with that — though it would follow the same routine as the postgis_comments just uses a different xsl file to generate.

[pracine]

For me there should be two changes:

-ST_Value should go in a new "Raster Pixel Accessor" section to distinguish the function accessing the global raster, the functions accessing the band and the ones accessing the pixels. I understand that for now there is only one Pixel Accessor and I still have problem imagining any other, but that make more sence to me. At last it should go with the "Band Accessor" ones but certainly not with the "Raster Accessor" ones like it is now.

The second one, I'm not sure:

-It seems to me that ST_Envelope and ST_Box2D should go in the "Raster Processing Functions" like ST_ConvexHull. I understand that in a geometry you really only "access" the value stored in the geometry, but for a raster we have to compute it from the georeference like we compute the convex hull. There is no Box2D, envelope or convex hull already stored that you can access. It is derived information. That's my understanding of the "Accessors".

[robe]

Okay made these changes they should show up soon.

For the other pixel accessor. We needed one that worked against point geometry. I think we have that on the list todo. Gives the pixel value at an intersecting point.

We have it here http://trac.osgeo.org/postgis/wiki/UsersWikiwktrasterfunctions

Seems to give the right answers as far as we can tell.

[pracine]

Please list any function missing in the documentation here.