On 28/09/10 17:06, [email protected] wrote: > 1) I have a set of Inspire schemas generated to conform to GML 3.1 (by > Andrew Woolf, who I think you know).
I have corresponded with Andrew. As long as your schemas have been ported to GML 3.1, they should work with the current version of app-schema. (Although we have not tested all data types.) > 2) Don't worry, I've not used the GUI to do my app-schema stuff. I just > happened to notice that the data stores I've set up that seem to be > working have a green tick and the ones that don't have a yellow > triangle. Hmm. This might mean the data accesses did not load because of errors. > 3) The tutorials are working. I've got the tutorial files parallel to > mine in the data directory. Good start. I thought I'd check to see where you were. I assumed you had worked through the tutorial, but I thought I should check. > I started by making copies of the tutorial workspaces and adapting them. > This has worked fine, but not in this case. I am prepared to believe > that there is some inconsistency in the schemas I'm using, but it's > tricky to pin down without any debugging information. In fact, this > morning I've chased up something in the schemas which refers to the > namespace gmd, and in the file gmd.xsd provided by GeoServer there is > the comment 'This is a stub schema because the ISO metadata schema does > not have a GML 3.1 binding.' So this may be where I'm currently held > up. Unless you've got any bright ideas, I can carry on trying to work > around this. A similar problem was encountered in a GeoSciML 2.0.0, which introduced a dependency on GMD and thus GML 3.2.1, which is not yet supported by GeoServer app-schema. The solution in this case was for the GeoSciML maintainers to change GMD use to by-reference (changed in GeoSciML 2.0.1). I will forward you information in a separate email. You might consider making a similar change to your ported schemas. > However, while I've got an expert on the line I'd like to ask about my > setup. I'm running GeoServer in an Ubuntu virtual machine which is > allocated 1GB of my 3.25GB on my desktop. Each time I make any change > to my mapping or setup, I have to restart tomcat6 and then refresh the > request to the WFS. This request (using firefox) takes more than 5 > minutes each time. This may again because I'm using complex schemas (if > I don't restart tomcat subsequent requests are much quicker) but if > there's some way I can save time in this cycle it would make progress > much quicker. Do you have any ideas? If you enable the tomcat manager, you should be able to reload just the GeoServer servlet without restarting tomcat. This will save you a some time. Feature chaining is inefficient because it does not make joins between source relations in the database. Configurations with many levels of nested features will be worst affected. > Sorry that these e-mails are a bit rambling. Not a problem. Your questions are clear and concise! Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
