Bad Jody - wrong list! (see Andrea it is not just you). Jody > Hi Joachim: > > Let me answer your email inline. > [EMAIL PROTECTED] wrote: > >> Hy Jody >> >> thank you for your great work on Postgis and Geoserver that brings great >> ideas one more time to Europe from your nice country Canada. >> >> I am writing to you cause I am a bit stuck on my workflow to set up a land >> information system. Since one month I have been working on programming and >> configuring a geodatabase with PostgreSQL/ Postgis as backend and GeoServer >> and Mapbender 2.4 as frontend. I come more from the user side but I am >> getting more involved in developing GIS infrastructures. If I am bothering >> you to much please just ignore my request. >> >> > Questions are always good; asking them on the GeoServer user list is > better (because more people are around to answer). GeoServer is designed > to work with a PostGIS you already have set up; you should be able to > point it at your existing tables and fill in the blanks using the web ui > (blanks are for things like description, projection and so on). > >> Online documentation is a quite good resource for further information and >> most of my questions have been answered by studying it. Unfortunately, I >> have not found comments and detailed examples on some features of GeoServer >> 1.4 that are not explained in detail. Lacking of comprehensive understanding >> of GeoServer architecture and some language obstacles, please give a novice >> programmer a hint.:-) >> >> > Could you be more specific? I am leaning GeoServer 1.4 as well ... my > best advice is to stop by tomorrow at 1pm PST on the #geoserver channel > and ask questions. Seriously we need question in order to provide > documentation, and indeed having anyone available to review docs can be > a big help. > > For developer docs it is a bit hard to follow - when I first started > work on GeoServer I spent three months taking it apart, and then putting > it back together - the documentation I produced during this time is > available here: http://vwfs.refractions.net/ I am looking to work with > it again; and it will be an interesting contrast to see how things have > changed through use. > >> My point of stumbling block is how to tell Geoserver to interact (configure) >> with PostgreSQL except for defining feature types and configuring mapbender >> 2.4 to interact with geoserver. At the end I would like to give users access >> via mapbender to my geodatabase and doing some programming with php that >> allows direct feature selecting, updating ... on my database. >> >> > I am not up to speed on mapbender; your goal sounds reasonable however. > >> For short overview please find attached screen shots showing my points of >> stumbling. >> >> > 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. > > > Thanks for these great questions ... > > What to do next? In a perfect world we use this as an opportunity to get > you involved :-) > 1. Create a Jira bug report > 2. Attach your document to it > 3. Make sure developers know you are available to test the result (ie > review docs or changes to ui page) > 4. Developers can mark the bug resolved and cut you a release with the > changes > 5. And you can close the issue :-) > > All the best, and enjoy GeoServer. > Jody > > > > >> I am looking forwared from hearing from you. >> >> Yours sincerely, >> Joachim >> >> >> -- >> -------------------------------- >> Joachim Sommer >> Hermann-Löns-Str. 24 >> 07745 Jena >> Email: [EMAIL PROTECTED] >> >> >> >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel >
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
