Rasterlite2 - status?

[mj10777]

Since January I have noticed that many api-changes were made to distinguish between Raster/Vector functions (RL2_Create/SetRasterCoverage etc.)

- for which the sql-reference table has not yet been updated at:

https://www.gaia-gis.it/fossil/librasterlite2/wiki?name=reference_table

It would also be interesting to learn the intended use of the 'RL2_*VectorCoverage' functions and an expected time-frame for a release.

Mark

[a.fu...@lqt.it]

On Tue, 26 May 2015 05:23:54 -0700 (PDT), mj10777 wrote:
> Since January I have noticed that many api-changes were made to
> distinguish between Raster/Vector functions
> (RL2_Create/SetRasterCoverage etc.)
> - for which the sql-reference table has not yet been updated at:
>
>
> https://www.gaia-gis.it/fossil/librasterlite2/wiki?name=reference_table
>

Hi Mark,

unhappily the documentation of RL2 is currently frozen (with very few
exceptions) to the last public release: RC0

many relevant changes are currently completely undocumented, anyway
the overall situation is still very fluid an highly dynamic, so any
attempt to maintain a well ordered documentation has very little
sense during this cahotic transition phase.
we'll surely have a complete and up-to-date documentation at the
end of the process when we'll finally reach a stable configuration.

> It would also be interesting to learn the intended use of the
> 'RL2_*VectorCoverage' functions
>

a Vector Coverage simply is a further meta-structure allowing to
create a WMS source based on vector data.
it basically is a thin wrapper encapsulating an ordinary Geometry
table and adding few others informations such as Name, Title and
Abstract plus a list of available SLD/SE styles and a list of
alternative CRSes.

in other words: the next version of RL2 will include a complete
rendering engine indifferently covering both raster and vector
data and fully based on standard SLD/SE styling rules.
The Vector Coverage simply is an intermediate level allowing
to rasterize vector data in a very flexible and fully
configurable way accordingly to the WMS conceptual model.

> and an expected time-frame for a release.
>

as you probably already noticed any development activity
on rasterlite2 was frozen during the latest weeks.
this simply was because the current priority is releasing
ASAP spatialite 4.3.0 thus definitely stabilizing many
relevant facets on this critical side.

after this the development will restart on rasterlite2:
the hi-level methods supporting full vector rasterization
will get their final implementation, the capability to
reproject on-the-fly raster data will be implemented
and the library as a whole will reach its intended final
stable configuration.
(and obviously: the documentation will be accordingly
updated).

when all these steps will be completed we'll be ready
to publish a new self-consistent testing version.
since then we'll simply have an unfinished and unstable
transition phase.

my personal rough estimation is that we have currently
done about 4/5 of the required overall work.

bye Sandro