/
ms-rfc-51.txt
111 lines (94 loc) · 3.62 KB
/
ms-rfc-51.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
.. _rfc51:
======================================================================
MS RFC 51: XML Mapfile Format
======================================================================
:Date: 2009/01/16
:Authors: Alan Boudreault
:Contact: aboudreault at mapgears.com
:Last Edited: 2009/03/09
:Version: MapServer 6.0
Overview
------------------------------------------------------------------------------
Presently, MapServer supports only normal mapfiles that are parsed by Flex.
The current mapfiles are parsed very fast by MapServer but can not be
parsed by any other software due to the parser complexity. So, a client
interface to build mapfiles is difficult to make.
The need we are trying to address is the ability to build MapFile Editors
that would be facilitated by the existence of a XML mapfile format (since
the current mapfile format makes it impossible to write a
forward-compatible parser). XML is seen as a solution that can provide a
strict syntax to mapfiles to have a strong validation with XML Schema.
This RFC proposes the addition of XML Mapfile support.
Technical Solution
------------------------------------------------------------------------------
It was decided that for the time being we should develop a XML schema and a
XSLT to convert from XML to text mapfile. If the new XML format takes off
then we may consider implementing support for it directly in MapServer in a
future release.
Mapfiles
------------------------------------------------------------------------------
An example of XML mapfile layer definition (prototype):
::
<Layer>
<name>popplace</name>
<type>POINT</type>
<debug>5</debug>
<status>ON</status>
<Metadata>
<item name="DESCRIPTION">Cities</item>
<item name="TEST">TESTING</item>
<item name="RESULT_FIELDS">NAME</item>
</Metadata>
<data>popplace</data>
<labelItem>Name</labelItem>
<classItem>Capital</classItem>
<Class>
<name>Cities</name>
<expression>1</expression>
<template>ttt_query.html</template>
<symbol>2</symbol>
<size>8</size>
<Label type="TRUETYPE">
<colorAttribute>[COULEUR]</colorAttribute>
<font>sans</font>
<angle>0</angle>
<size>8</size>
<outlineColor red="255" green="255" blue="255"/>
</Label>
<color red="0" green="255" blue="0"/>
</Class>
<Class>
<name>Cities</name>
<expression>/2|3/</expression>
<template>ttt_query.html</template>
<tolerance>5</tolerance>
<Label type="TRUETYPE">
<colorAttribute>[COULEUR]</colorAttribute>
<font>[FONT]</font>
<angle>[ANGLE]</angle>
<size>8</size>
<outlineColor red="255" green="255" blue="255"/>
<position>AUTO</position>
<partials>FALSE</partials>
</Label>
<Style>
<symbol>7</symbol>
<size>6</size>
<colorAttribute>[COULEUR]</colorAttribute>
</Style>
</Class>
</Layer>
Future Enhancement
------------------------------------------------------------------------------
In the future, some enhancement could be good to added:
* Special tags for all WMS options (including styles)
* Reusable xml block with ID
Documentation
--------------------------------------------------------------------------------
TBD
Backwards Incompatibility
--------------------------------------------------------------------------------
No issues expected.
Bug ID
--------------------------------------------------------------------------------
https://github.com/mapserver/mapserver/issues/2872