1
|
|
2
|
<h2>Sources for maps</h2>
|
3
|
|
4
|
<p>
|
5
|
All maps used in mapbuilder are from OGC
|
6
|
<a href="?page=reference#ogc">Web Map Context documents.</a>
|
7
|
A context document provides an interoperable way of storing and sharing
|
8
|
maps created using the various OGC web service specfications
|
9
|
</p>
|
10
|
|
11
|
<p>
|
12
|
Sources for these maps:
|
13
|
<ul>
|
14
|
<li><span class="title">Create your own:</span>
|
15
|
Use a text or XML editor to add and delete layers to an existing or new
|
16
|
context document.
|
17
|
This method is tedious and difficutl but can be used for simple changes.
|
18
|
</li>
|
19
|
<li><span class="title">owsview:</span>
|
20
|
Currently, the best application for creating a context document is
|
21
|
<a href="http://cgdi-dev.geoconnections.org/prototypes/owsview/index.html" target="GetContext">owsview.</a>
|
22
|
Functions include adding layers by browsing WMS capabilities doc and loading
|
23
|
and saving context documents.
|
24
|
</li>
|
25
|
<li><span class="title">Search the GeoConnections Discovery Portal:</span>
|
26
|
The Discovery Portal offers a
|
27
|
<a href="http://geodiscover.cgdi.ca/ceonetWeb/doc?dispatchServlet=/biz&servletName=bizServlet&service=searchForWebServiceData" target="GetContext">
|
28
|
web service search</a> function which will
|
29
|
dynamically generate a context document based on search parameters.
|
30
|
The limitiations of this method are that it depends on the web service
|
31
|
providing good metadata in the capabilities document and a slow response of the
|
32
|
search engine.
|
33
|
Look for improvments to this service as new registry technology is implemented.
|
34
|
</li>
|
35
|
</ul>
|
36
|
</p>
|
37
|
|
38
|
<p>
|
39
|
If you know of any other map sources, please
|
40
|
<a href="mailto:mapbuilder-devel@lists.sourceforge.net">let us know.</a>
|
41
|
</p>
|
42
|
|