[mapserver-commits] r7982 - trunk/mapserver/rfc
svn at osgeo.org
svn at osgeo.org
Tue Oct 14 16:04:12 EDT 2008
Author: tbonfort
Date: 2008-10-14 16:04:12 -0400 (Tue, 14 Oct 2008)
New Revision: 7982
Modified:
trunk/mapserver/rfc/ms-rfc-45.txt
Log:
add file references
Modified: trunk/mapserver/rfc/ms-rfc-45.txt
===================================================================
--- trunk/mapserver/rfc/ms-rfc-45.txt 2008-10-14 15:43:48 UTC (rev 7981)
+++ trunk/mapserver/rfc/ms-rfc-45.txt 2008-10-14 20:04:12 UTC (rev 7982)
@@ -1,6 +1,3 @@
-.. sectnum::
-
-
:Date: 2008/08/26
:Authors: Stephen Lime, Håvard Tveite, Thomas Bonfort
:Contact: Steve.Lime at DNR.State.MN.US
@@ -10,12 +7,13 @@
(*partiallly derived in part from a document prepared by Håvard and discussions with other developers working on cartographic output*)
-Proposed Changes
-################
+1. Proposed Changes
+###################
-Scale Dependant Rendering
-*************************
+.. _1:
+1.1. Scale Dependant Rendering
+******************************
- All symbols can be scaled. When SYMBOLSCALEDENOM is given for a layer, the
layer and all of its symbols (height, width, line widths, line patterns, line
dashes, ...) are scaled.
@@ -28,14 +26,16 @@
CLASS->STYLE->MAXSIZE. By using these MINSIZE/MAXSIZE, one can ensure that a
symbol will never be rendered smaller/larger than the given sizes.
-Precise Symbol Placement
-************************
+1.2. Precise Symbol Placement
+*****************************
Harmonize the placement of symbols relative to the feature (point or line)
being drawn.
-Fractional values for sizes
-===========================
+.. _2:
+
+1.2.1. Fractional values for sizes
+==================================
All symbols sizes and symbol geometries should be specified and
represented as double - AGG supports fractional line widths so users
should be able to set them explicitly. GD could either round or
@@ -50,8 +50,10 @@
- LABEL->SIZE/MINSIZE/MAXSIZE - labelObj.size/minsize/maxsize
- LABEL->OFFSET - labelObj.offsetx and labelObj.offsety
-CENTER/ORIGIN [x y]
-===================
+.. _3:
+
+1.2.2. CENTER/ORIGIN [x y]
+==========================
Defines the centre of the symbol using decimal pixels (x axis increasing to
the right, y axis increasing downwards).
@@ -60,9 +62,11 @@
- Default value is the centre of the symbol's bounding box.
- Applies to TYPE ellipse, vector, pixmap, truetype.
-ANGLE [double|attribute] [DEFAULT|CLOCKWISE|COMPASS]
-====================================================
+.. _4:
+1.2.3. ANGLE [double|attribute] [DEFAULT|CLOCKWISE|COMPASS]
+===========================================================
+
- STYLE-> ANGLE [double|attribute] [DEFAULT|CLOCKWISE|COMPASS]
- LABEL-> ANGLE [double|auto|follow|attribute] [DEFAULT|CLOCKWISE|COMPASS]
@@ -79,8 +83,8 @@
The default would be reference direction east and counter-clockwise rotation.
If possible, something like:
-Modes of operation
-------------------
+a. Modes of operation
+---------------------
- DEFAULT reference direction to the right (east), counter-clockwise direction
of rotation.
- CLOCKWISE reference direction to the right (east), clockwise direction of
@@ -88,8 +92,8 @@
- COMPASS reference direction to the north, clockwise direction of rotation
(compass directions).
-Behavior
---------
+b. Behavior
+-----------
- For symbols of Type HATCH, this is the angle of the hatched lines.
- For points, this specifies the rotation of a symbol around its defined
CENTER.
@@ -101,24 +105,30 @@
defining symbol. For its use with hatched lines, see Example#8 in the SYMBOL
examples.
-Stable rendering for tile generation
-====================================
+1.2.4. Stable rendering for tile generation
+===========================================
*how and with what keywords?*
-polygon fill symbols
---------------------
+.. _5:
+
+a. polygon fill symbols
+-----------------------
give hatches and vector fills a stable geographical coordinate origin (0,0) to
better support tiling and continuous rendering of neighbouring polygons
-labelling
----------
+.. _6:
+
+b. labelling
+------------
TODO
-Keywords moved from SYMBOL to STYLE
-***********************************
+1.3. Keywords moved from SYMBOL to STYLE
+****************************************
-FIXME GAP [double]+ END
-=======================
+.. _7:
+
+1.3.1. FIXME GAP [double]+ END
+==============================
Gap between point symbols when rendered on a linear geometry (used eg. for
shields)
@@ -141,26 +151,36 @@
the line. When placing the symbol on the line, the symbol is oriented in such
a way that the symbol's x-axis is directed along the line.
+.. _8:
-DASHPATTERN ([double on] [double off])+ END
-===========================================
+1.3.2. DASHPATTERN ([double on] [double off])+ END
+==================================================
- renamed from STYLE
- the distances are scaled
-more to come?
-=============
+1.3.3. more to come?
+====================
-New Functionnality
-##################
+2. New Functionnality
+#####################
-add MINSCALEDENOM/MAXSCALEDENOM parameters to styleObj
-******************************************************
+.. _14:
+
+2.1. add attribute binding for WIDTH in styleObj
+************************************************
+
+.. _9:
+
+2.2. add MINSCALEDENOM/MAXSCALEDENOM parameters to styleObj
+***********************************************************
this would allow doing things like removing outlines or the hollow portions of
"tube" line work based on scale.
-add LABELMETHOD to layerObj
-***************************
+.. _10:
+
+2.3. add LABELMETHOD to layerObj
+********************************
(or perhaps just method to labelObj?)
- this would allow users to choose label placement algorithms that meet their
@@ -170,13 +190,17 @@
- The default would be the improved placement in D2.
-add LABEL to layersObj
-*************************
+.. _11:
+
+2.4. add LABEL to layersObj
+***************************
so that a default can be defined for all classes (sort of like templates). A
class label would take precedent.
-add OUTLINEWIDTH to styleObj
-****************************
+.. _12:
+
+2.5. add OUTLINEWIDTH to styleObj for line types
+************************************************
eg for drawing road lines with a cached outline
- It is currently impossible to have scale dependant road networks with a fixed
@@ -185,9 +209,10 @@
- This would also be a shorthand to be able to specify an outline for linear
networks, without having to specify two style blocks.
+.. _2.6:
-add TYPE to styleObj for line and polygon types
-***********************************************
+2.6. add TYPE to styleObj for line and polygon types
+****************************************************
modifies how the current shape is interpreted. Applies to line and polygon
layers (for now: any ideas for applying this to point layers?)
@@ -205,21 +230,21 @@
- default angle is direction of first/last segment
-Files Affected
-##############
+3. Files Affected
+#################
-* maplexer.l: C4, C5
-* mapgd.c: B1, C2, C3, C4
-* mapagg.cpp: B1, C2, C3, C4
-* mapfile.c: B1, C1, C2, C3, C4, C5, C6, D1
-* mapdraw.c: C1, C5, C6, D1
+* maplexer.l: 2.6_, 10_
+* mapgd.c: B1, C2, C3, C4, 1_, 2_?, 3_ 7_, 8_, 5_, 4_?
+* mapagg.cpp: B1, C2, C3, C4, 1_, 2_, 3_, 7_, 8_, 5_, 4_
+* mapfile.c: 2.6_, 12_, 11_, 10_, 9_, 6_, 5_, 4_, 3_, 2_, 1_
+* mapdraw.c: 2.6_, 12_, 11_, 10_, 9_, 4_ C1, C5, C6, D1
* mapprimitive.c: C5, D2
-Bug IDs
-#######
+4. Bug IDs
+##########
Individual modifications will be tracked with their own tickets which will
be listed here.
- - B1: http://trac.osgeo.org/mapserver/ticket/2766
+ - 2_: http://trac.osgeo.org/mapserver/ticket/2766
More information about the mapserver-commits
mailing list