Lorenzo Becchi wrote: >> If you want to be able to update your catalog, you should also implement >> transactionnal operators. >> All this to say it could be the ideal solution but this is a big game. >> >> >> > Hi Robert, > I absolutely don't want to re-implement a complete client for CAT or > CSW2. I would be scared about it. > I'm just trying to do a simple search field to query a/some Catalog/s > and retrieve a list of WMS/OWS services with title, description, > getCapabilities url, and a link to the complete metadata description. > In this way it would be easy to add a server to WMSManager (probably > soon OWSManager) having the Metadata available. > You put a search string: "forest occurrence" > You maybe have a checkbox to block the research to your map extent. > Submit the query and play with the parsed response. > > is this feasible from a Catalog point of view? > > >> In my mind, for the particular needs of retrieving some WMS servers URLS and >> their capabilites, we could rely on something much simpler. >> The example already given here : >> http://www.microimages.com/wmscatalog/request.cgi? sends XML output. I was >> wondering if this output was somewhere standardized ? >> >> > http://www.microimages.com/wmscatalog/request.cgi > has no Metadata and it's close to be useless, IMO. I'm scared about that > list. > hehehe dont be afraid...currently it is a free form implementation http://www.microimages.com/wmscatalog/specifications.htm but will graduate to an official catalog some day > Who wants to try all those servers to see what they have inside? > > What happens if the list goes over a thousand records? > - long time to download it > - hypnosis after 10 lines reeding > - :-) > maybe I'm kidding but Metadata are very important to me. > ask for new features... I will log the request we have one of our programmers doing it... and he is very speedy ;-)
_______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev
