Contents
1. General Questions
1.1. What is deegree?
There are many answers to this question! The most precise of them is, deegree is an Java API (Application Programming Interface) for Geographic Informations Systems (GIS). That is, a large set of Java classes (or components, if you like) for you to use to create a GIS. Having said that, there's already a main application we have built, which are the deegree OGC-conform Web Services. That is, deegree already includes the - at present - most comprehensive set of OGC Web services, ranging from a transactional Web Feature Service to the more pleasing to the eye Web Terrain Service. Please consult the related answers to this question, for more detailed information
1.2. Where can I get deegree?
You can download the demo applications. Note that the source code is also available as a jar and so is the latest binary release, with compiled classes. Building and deploying deegree is described in the article Deployment. You can also access our SVN and download the latest source code.
1.3. Why should I use deegree?
Well, there are many answers to this question, too. The most convenient of them is: deegree is free. But also, deegree is the most comprehensive set of OGC Web Services in free and open source software out there. deegree also includes a powerful and flexible Web mapping tool for you to build your Spatial Data Infrastructure, the iGeoPortal and a rich-client platform, deeJUMP in case you want to do even more.
1.4. Is there a tutorial available? Or can I get more information?
Yes, there is plenty of documentation available on how to set up a deegree service. You can download the documentation or perhaps subscribe to a mailing list. There are three mailing lists, one for users, interested in setting up and using deegree services and related products; a second list, for developers to exchange code and ideas; and a third list, with deegree-related news, for people who don't want the traffic of the main mailing lists, but want to be informed what the deegree team is up to. Feel free to subscribe, but before posting a question, make sure it hasn't been answered in this FAQ and that your question is actually not covered in the documentation.
2. Organisational Questions
2.1. Is deegree part of OSGeo?
deegree has successfully graduated from the incubation process and is now a full OSGeo project. For more information read about deegree's OSGeoIncubation.
2.2. What about the PSC?
The project steering committee (PSC) will have its own page in this wiki soon. Stay tuned.
3. Technical Questions
3.1. Do you have a CVS ?
We used to have a CVS. But the code has been moved to an SVN.
3.2. Do you have an SVN ?
Yes, indeed. We use the SVN at http://deegree.wald.intevation.org
There is a description on how to use it in this wiki on the Eclipse page.
3.3. Is there an issue tracker ?
Yes. They are at http://deegree.wald.intevation.org
We've got a bug tracker (http://wald.intevation.org/tracker/?atid=212&group_id=27)
and a feature request tracker (http://wald.intevation.org/tracker/?atid=215&group_id=27)
Since the deegree project is in incubation to become an OSGeo member, we even have a PSC tracker (http://wald.intevation.org/tracker/?atid=281&group_id=27)
3.4. Do you offer support by mailing list?
There are 3 mailing lists relevant for deegree. They are hosted by sourcforge. If you want to be informed about the evolution of deegree, join the deegree announce mailing list (very low traffic).
In cases of problems like installing and deploying deegree, join the deegree user's mailing list (medium traffic).
If you want to add code, apply patches etc. join the deegree developer's mailing list (medium traffic).
3.5. What libraries are needed by deegree?
many. see ExternalLibraries for more on this.
3.6. Do you have any technical documentation, such as UML diagrams?
[PENDING]
4. questions on deegree products
4.1. WMS Questions
4.1.1. What is a WMS?
WMS stands for Web Map Service. WMS is a standard defined by the Open Geospatial Consortium. A web service that implements the WMS standard is called a WMS. deegree WMS implementation is compliant to OGC WMS specification 1.1.1 and 1.3.
4.1.2. How can I set deegree WMS to show my data?
For most people this is a three-step process. (We are assuming you have a deegree demo up and running. If not, please consult the WMS documentation on how to do that.)
- Add a new layer to the WMS capabilities
- Configure the LOCAL_WFS or the LOCAL_WCS to include this new layer
- Configure the data store [PENDING: is this still called data store???] with your data parameters (position of your shapefile, DB parameters, etc...
This is all described in detail in the WMS documentation.
4.1.3. Why can't I see my data?
There are two main reasons for this: Your configuration is wrong. Please have a look at the log files (deegree_log.txt in your home directory and the Tomcat logs in TOMCAT_HOME/logs). The second reason is, you have defined a wrong LatLonBoundingBox.
The LatLonBoundingBox is always valid inside the ranges (-180,180) for longitude and (-90,90) for latitude. If you choose a value that doesn't match that of your data, the WMS doesn't even bother to look your data up, and thus shows none.
Conversely, you might be looking for data where you have none. This means you might be entering the wrong bounding box or the wrong coordinate reference system, or both!, in your request.
In doubt, enter a large bounding box, such as
<LatLonBoundingBox minx="-180" miny="-90" maxx="180" maxy="90">
(Note that the LatLonBoundingBox assumes a geographic coordinate system, which is, by definition EPSG:4326, that is WGS84.) Also, make sure in which coordinate system your data are in, and that in the WMS request you are entering a valid combination of bounding box and coordinate reference system.
4.1.4. OK, I've got an image. How do I pan, zoom, ask for feature info?
get a client like iGeoPortal or OpenJUMP to do that...
4.1.5. How do I change the data I'm seeing? Is there a service to do that?
(Question suggested by MarkusLupp. Will be answered.)
4.2. WFS Questions
4.2.1. What is a WFS?
WFS stands for Web Feature Service. WFS is a standard defined by the Open Geospatial Consortium. A web service that implements the WFS standard is called a WFS. deegree WFS implementation supports OGC WFS specifications 1.0 and 1.1.
4.2.2. How can I set deegree WFS to serve my data?
[PENDING]
4.2.3. OK, my WFS is up and running...What do I do now?
[PENDING]
4.2.4. How do I change my data with the WFS?
The magic word reads WFS-T (T for transactional). deegree WFS is a transactional WFS, thus it is also a WFS-T.
Read more about the WFS-T and its configuration right here: TransactionalWebFeatureServiceConfiguration
4.3. WCS Questions
4.3.1. What is a WCS?
WCS stands for Web Coverage Service. WCS is a standard defined by the Open Geospatial Consortium. A web service that implements the WCS standard is called a WCS. deegree WCS implementation is compliant to OGC WCS specification 1.0.
4.3.2. How can I tile my image?
[PENDING]
4.4. iGeoPortal Questions
[PENDING] for now, please see iGeoPortal
4.5. Questions about other services
4.5.1. Where can I get an overview over all WebServices supported by deegree?
Please visit our page on WebServices.
4.5.2. What is a CSW?
CSW stands for Catalaogue Service for the Web. CSW is a standard defined by the Open Geospatial Consortium. A web service that implements the CSW standard is called a CSW. deegree CSW implementation supports OGC CSW specifications 2.0.0 and 2.0.2.
4.5.3. What is a WPVS?
WPVS stands for Web Perspective View Service. WPVS is a standard defined by the Open Geospatial Consortium. A web service that implements the WPVS standard is called a WPVS.
4.5.4. What is a WPS?
WPS stands for Web Processing Service. WPS is a standard defined by the Open Geospatial Consortium. A web service that implements the WPS standard is called a WPS. deegree2 WPS implementation supports OGC CSW specification 0.4.0. deegree3 WPS implementation supports OGC specification 1.0.
5. Miscellaneous Questions
5.1. My Tomcat stops with an OutOfMemoryError. How can I avoid that?
You have to increase the maximal memory available to Tomcat. Read HowToDealWithOutOfMemoryError for a detailed description.