[Geoserver-devel] [jira] Created: (GEOS-981) Request for Hints

Request for Hints
-----------------

                 Key: GEOS-981
                 URL: http://jira.codehaus.org/browse/GEOS-981
             Project: GeoServer
          Issue Type: Bug
          Components: Struts
    Affects Versions: 1.5.0-RC2
            Reporter: Jody Garnett
         Assigned To: Andrea Aime
            Priority: Minor
         Attachments: Request-Geoserver.doc

From private email (Joachim Sommer); attached document provides a list of specific questions. The tooltips for the user interface elements mentioned should be modified to answer the questions raised.

Questions (from attached doc)

Q: Proxy base URL

When you are using GeoServer behind a proxy/firewall the users on the
outside will see a different URL from anything geoserver had in mind.
Since some of the documents we return need to link to each other
geoserver needs to know how to construct the url that users will see.
So the GetFeature response document links to the DescribeFeatureType
response document.

Q: Online Resource

This is a good example - if you read the WFS 1.0 specification these
kinds of questions would be answered. If I recall correctly the
"OnlineResource" is link to more information about the server - oh wait
that was metadata url. Sigh. Can you check the WFS specification and get
back to me?

Q: AccessConstraints

I am not sure what access constraints you have - I would hope for read
only et... but one again this is from the specification. The words here
are only used to describe the access constraints (maybe data license?).

Q: Data Maintenance

Same deal - we need to read the specification

Q: OnlineResource

This is the one I mentioned earlier - it is the link to a metadata
document describig your data using a ISO19115 document - nobody in the
real world has ever done this.

Q: WMS Access Constraints

NONE is good; you could do a click through license or username/password
(if you configure your Tomcat correctly)

Q: WMS Data Maintenance

We need to read the specification again - my guess is the information
gives a user of your server an idea of how good your data is.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira