[postgis-devel] Docbook ID's and <a name> links
Kevin Neufeld
kneufeld at refractions.net
Mon Jul 14 15:50:06 PDT 2008
Obe, Regina wrote:
> Okay that's good so we can have meaningful names. So what goes in
> Chapter 6? I can start moving my changes into chapter 7 and putting in
> the refentry replacement when you are ready.
>
> So would we just delete whatever we have in chapter 6 once we move it to
> chapter 7?
>
> Thanks,
> Regina
That would be great. Yes, I propose we delete the function entry(s)
from chapter 6 as we make a new refentry in chapter 7. Eventually ch6
would disappear entirely. I foresee this taking some time, but with
couple of people working on this, it's not too bad. Functions sometimes
occur several times in the docs in different sections.
IE. ST_Distance() is in:
OpenGIS Functions -> Geometry Relationship Functions
PostGIS Functions -> Measurement Functions
SQL-MM Functions
each time with a different definition, which I think could get cleaned
up. Other functions are in appropriate headings, like ST_LineMerge
which is in the Editors heading when its really a constructor like
ST_Polygonize.
I think first thing we would need to come up with though, is an outline
that will reduce the number of duplicate entries. As you may recall, it
was discussed that the "OpenGIS Functions" and "PostGIS Extensions"
could merge together
(http://postgis.refractions.net/pipermail/postgis-devel/2008-June/003134.html).
Should we include SQL-MM and ArcSDE functions as well?
What about something like...
6.1 Management Functions
6.2 Geometry Constructors
6.3 Geometry Accessors
6.4 Geometry Editors
6.5 Geometry Outputs
6.6 Operators
6.7 Spatial Predicates
6.8 Linear Referencing
6.9 Long Transactions Support
6.10 Misc
Alternatives?
-- Kevin
More information about the postgis-devel
mailing list