File tree Expand file tree Collapse file tree 2 files changed +11
-1
lines changed
Expand file tree Collapse file tree 2 files changed +11
-1
lines changed Original file line number Diff line number Diff line change 3535
3636- File location can be given as a full path to the file, or (in MapServer >=
3737 4.10.1) as a path relative to the mapfile.
38+
39+ .. note::
40+
41+ Nested :ref:`INCLUDE` statements (such as an INCLUDE within an INCLUDE)
42+ must be relative to the top-level mapfile, not its parent mapfile.
3843
3944- Debugging can be problematic because:
4045
Original file line number Diff line number Diff line change 1111:Contact: steve.lime at dnr.state.mn.us
1212:Author: Jeff McKenna
1313:Contact: jmckenna at gatewaygeomatics.com
14- :Last Updated: 2022-08-29
14+ :Last Updated: 2025-06-04
1515
1616The Mapfile is the heart of MapServer. It defines the relationships
1717between objects, points MapServer to where data are located and
@@ -122,6 +122,11 @@ Notes
122122* File paths may be given as absolute paths, or as paths relative to
123123 the location of the mapfile. In addition, data files may be
124124 specified relative to the SHAPEPATH.
125+
126+ .. note::
127+
128+ Nested :ref:`INCLUDE` statements (such as an INCLUDE within an INCLUDE)
129+ must be relative to the top-level mapfile, not its parent mapfile.
125130
126131* The mapfile has a hierarchical structure, with the MAP object being
127132 the "root". All other objects fall under this one.
You can’t perform that action at this time.
0 commit comments