Mapping - Revision history

Jillhinchliffe: /* Viewing maps */

2018-06-22T11:27:01Z

‎Viewing maps

Jillhinchliffe: /* Mapfile code */

2018-06-22T11:25:22Z

‎Mapfile code

Angus: /* Field names */

2015-04-04T07:27:22Z

‎Field names

Angus: /* Required fields */

2015-04-04T07:23:50Z

‎Required fields

Angus: /* Viewing maps */

2015-04-04T07:22:59Z

‎Viewing maps

Angus: /* CLASSITEM (optoinal) */

2015-04-04T07:22:13Z

‎CLASSITEM (optoinal)

Angus: /* Viewing maps */

2015-04-01T07:40:20Z

‎Viewing maps

Angus: /* Mapfile code */

2015-04-01T07:33:32Z

‎Mapfile code

Angus: /* Mapfile code */

2015-04-01T07:28:00Z

‎Mapfile code

Angus: /* Mapfile code */

2015-04-01T07:27:01Z

‎Mapfile code

@@ Baris 137: / Baris 137: @@
   /root/index/216
-* If there are parameters to produced a pre-configured report (different from the default) you need to use remove the first '/' and add the parameters. For example:
+* If there are parameters to produce a pre-configured report (different from the default) you need to remove the first '/' and add the parameters. For example:
   root/index/216&param[diagnosis]=13

@@ Baris 37: / Baris 37: @@
 Most of the mapfile is automatically generated using fixed standards and the SQL previously defined, but you have to specify here how the map should appear.
-The contents of the R code box, are inserted into the mapfile in a LAYER block. Full documentation of what is permitted can be found in the [http://mapserver.org/mapfile/layer.html Mapserver documentation]
+The contents of the R code box is inserted into the mapfile in a LAYER block. Full documentation of what is permitted can be found in the [http://mapserver.org/mapfile/layer.html Mapserver documentation]
 Two sections are required (TYPE and CLASS) and there are some optional sections
@@ Baris 43: / Baris 43: @@
 This can be POINT, LINE or POLYGON, depending on the map to be produced. For example, for a point map:
   TYPE POINT
-Other types can be used including CHART, CIRCLE, RASTER, but these are uncommon advanced features.
+Other types can be used including CHART, CIRCLE, RASTER but these are uncommon advanced features.
 =====CLASS (required) =====
@@ Baris 106: / Baris 106: @@
 In this case, the query must have a field called "laporan" which has an integer (the number of reports submitted).
-The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org/index.html   ColorBrewer] web site is an excellent tool for picking good map colours and finding their RBG code.
+The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org/index.html   ColorBrewer] web site is an excellent tool for picking good map colours and finding their RGB code.
 =====CLASSITEM (optional) =====

@@ Baris 21: / Baris 21: @@
   SELECT
     sum(total) as "Julah hewan"
 ===Mapfile code===

@@ Baris 10: / Baris 10: @@
 ====Required fields====
 Every query must return two required fields:
-* gid - this is a 'geographic ID' and is a unique integer for each spatial unit returned. Often, this can just be the id from the locations table, but if there can be multiple reports per location, you need to choose another unique ID value. It doesn't matter which. If nothing else is available, you can also use the row number window function:
+* '''gid''' - this is a 'geographic ID' and is a unique integer for each spatial unit returned. Often, this can just be the id from the locations table, but if there can be multiple reports per location, you need to choose another unique ID value. It doesn't matter which. If nothing else is available, you can also use the row number window function:
   select row_number() over () as gid,
-* the_geom: this is the spatial data and must be included in every report. It should always come from the projected version of the locations table spatial data. That is:
+* '''the_geom''': this is the spatial data and must be included in every report. It should always come from the projected version of the locations table spatial data. That is:
 ** For polygon data (administrative units) this should be geom_proj (e.g. select geom_proj as the_geom, )
 ** For point data (village locations etc) this should be centroid_proj (e.g. select centroid_proj as the_geom, )

@@ Baris 127: / Baris 127: @@
   /root/index/216
-* If there are parameters to produced a pre-configured report (different from the default, you need to use remove the first '/' and add the parameters. For example:
+* If there are parameters to produced a pre-configured report (different from the default) you need to use remove the first '/' and add the parameters. For example:
   root/index/216&param[diagnosis]=13

@@ Baris 98: / Baris 98: @@
 The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org/index.html   ColorBrewer] web site is an excellent tool for picking good map colours and finding their RBG code.
-=====CLASSITEM (optoinal) =====
+=====CLASSITEM (optional) =====
 This specifies that one field in the query will be used to determine the style of different features. For example:
@@ Baris 109: / Baris 109: @@
        END
    END
-−
    CLASS
        NAME "Negatif"

← Revisi sebelumnya		Revisi per 1 April 2015 07.40
Baris 121:		Baris 121:

	==Viewing maps==		==Viewing maps==
−	~~Menu~~ root	+	Maps must be viewed using the 'root' interface.
		+
		+	* If there are no special parameters (the normal situation)
		+	** Set up a menu entry as usual, and set the URL to: root/index/''reportid''. For example
		+	/root/index/216
		+
		+	* If there are parameters to produced a pre-configured report (different from the default, you need to use remove the first '/' and add the parameters. For example:
		+
		+	root/index/216&param[diagnosis]=13

@@ Baris 27: / Baris 27: @@
 Most of the mapfile is automatically generated using fixed standards and the SQL previously defined, but you have to specify here how the map should appear.
-The contents of the R code box, are inserted into the mapfile in a LAYER block. Full documentation of what is permitted can be found in the [[http://mapserver.org/mapfile/layer.html|Mapserver documentation]]
+The contents of the R code box, are inserted into the mapfile in a LAYER block. Full documentation of what is permitted can be found in the [http://mapserver.org/mapfile/layer.html Mapserver documentation]
 Two sections are required (TYPE and CLASS) and there are some optional sections
@@ Baris 56: / Baris 56: @@
    END
-The style options are very powerful. See the [http://mapserver.org/mapfile/class.html#class|Mapserver CLASS documentation] for more information.
+The style options are very powerful. See the [http://mapserver.org/mapfile/class.html#class Mapserver CLASS documentation] for more information.
 Standard SYMBOLs are pre-defined in a symbol file. For more symbols, this file will have to be manually edited.
@@ Baris 96: / Baris 96: @@
 In this case, the query must have a field called "laporan" which has an integer (the number of reports submitted).
-The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org/index.html | ColorBrewer] web site is an excellent tool for picking good map colours and finding their RBG code.
+The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org/index.html   ColorBrewer] web site is an excellent tool for picking good map colours and finding their RBG code.
 =====CLASSITEM=====

@@ Baris 69: / Baris 69: @@
        END # STYLE
    END # CLASS
    CLASS
        NAME "1 - 5 laporan"
@@ Baris 95: / Baris 96: @@
 In this case, the query must have a field called "laporan" which has an integer (the number of reports submitted).
-The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org|ColorBrewer] web site is an excellent tool for picking good map colours and finding their RBG code.
+The COLOR and OUTLINECOLOR lines require a RGB (red green blue) colour code. The [http://colorbrewer2.org/index.html | ColorBrewer] web site is an excellent tool for picking good map colours and finding their RBG code.
 =====CLASSITEM=====