You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ and the next targeted release of Mapnik.
20
20
21
21
## Meaning
22
22
23
-
The structure of the file is as such:
23
+
The structure of `reference.json` is:
24
24
25
25
*`version`: the version of Mapnik targeted. Same as the containing directory.
26
26
*`style`: properties of the `Style` XML element
@@ -38,6 +38,7 @@ then the `status` is `stable`. Possible values are:
38
38
-**deprecated:**`property` should not be used and will be removed in upcoming major version of Mapnik
39
39
-**experimental:**`property` should not be used and may change, be re-named, or disappear at any time
40
40
41
+
`datasources.json` separately details the properties of the possible data sources (since version 2.3.0).
41
42
42
43
## Using
43
44
@@ -82,5 +83,5 @@ Tests require python and node.js:
82
83
83
84
## Users
84
85
85
-
*[carto.js](https://github.com/mapbox/carto)
86
-
* Mapnik itself (the util/validate-mapnik-instance.py is used to check binding consistency like in [#1427](https://github.com/mapnik/mapnik/issues/1427))
86
+
*[carto.js](https://github.com/cartocss/carto)
87
+
* Mapnik itself (the utility [mapnik-reference-validate.py](https://gist.github.com/springmeyer/3410845) can be used to check binding consistency like in [#1427](https://github.com/mapnik/mapnik/issues/1427))
0 commit comments