[OSGeodata] geodata stylesheets

[Allan Doyle]

I agree this is a great idea. I've often wondered about doing  
something similar, basically just using stylesheets to create HTML  
renditions of capabilities documents with some bits that make them  
show up in google searches in a useful way.

On Aug 3, 2006, at 11:04, Norman Barker wrote:

> Thanks for the list, and the version numbers, if I get the WCS  
> retrieval
> fully working this way then the others will be very similar.
>
>
> The Sensor Observation Service would be interesting in terms of
> generating GeoRSS, and there are a couple flying around at the moment
> (MapServer has support).
>
> I have concerns about how much useful metadata you can retrieve from a
> getcapabilities call, the time period is important, and also since  
> most
> getcapabilites are dynamic should you just fetch every time - or say
> file size (as determined by an http head request) is an indicator of
> whether to fetch?

I would say try going with file size as a trigger. Maybe this whole  
thing will stir up a little interest in decent caching parameters.

Maybe once you've got something going, a message to wms-dev would be  
in order.

A second-order issue might be figuring out how to deal with cascading  
WMS's. There are some that simply cascade, others that cascade and  
add value (e.g. offering projections not available in the primary WMS).

	Allan

>
> I have copied the concerning bits from the stylesheet here but they
> relate to populating the database schema
>
>     <!-- boolean ok for classifying type? -->
>     <entry key="raster">1</entry>
>     <entry key="vector">0</entry>
>     <entry key="point">0</entry>
>     <!-- evaluate bbox, so not just to get -180,-90,180,90 from lazy
> admins-->
>     <xsl:call-template name="bbox">
>         <xsl:with-param name="list" select="//wcs:lonLatEnvelope"/>
>     </xsl:call-template>
>
>     <!-- what value should we put in here? -->
>     <entry name="date"><xsl:value-of select="date:date-time()"/></ 
> entry>
>     <!-- need to a describeCoverage here, but this could be different
> for every coverage offering brief and we are only storing
> capabilities-->
>     <entry name="timePeriod"></entry>
>     <!-- CRS ref is forced to epsg:4326 -->
>     <entry name="projRef">EPSG:4326</entry>
>     <entry name="dataSource">WCS</entry>
>
> Thanks,
>
> Norman
>
> -----Original Message-----
> From: Kralidis,Tom [Burlington] [mailto:Tom.Kralidis at ec.gc.ca]
> Sent: Thursday, August 03, 2006 3:54 PM
> To: geodata at geodata.osgeo.org
> Subject: RE: [OSGeodata] geodata stylesheets
>
>
> This is quite nice!
>
> If we assume all of metadata will be encoded in XML, we should  
> probably
> list what XSLT's we need, a few off the top of my head:
>
> OGC:WMS 1.1.1
> OGC:WFS 1.0.0
> OGC:WCS 1.0.0
> FGDC:CSDGM-1998
> ISO19115
> ISO19119
> OGC:OWSCommon
> GeoRSS
>
>
> Any others?
>
> ..Tom
>
>
>> -----Original Message-----
>> From: Norman Barker [mailto:nbarker at ittvis.com]
>> Sent: 03 August, 2006 10:44 AM
>> To: geodata at geodata.osgeo.org
>> Subject: [OSGeodata] geodata stylesheets
>>
>> Hi,
>>
>> Following on from our earlier discussions I wrote a
>> stylesheet targeted towards extracting information from a
>> getcapabilities response;
>>
>> I have attached the test capabilities response (just a crude
>> manufactured example), the stylesheet (you will need the
>> exslt extensions for your language (java has them already,
>> firefox will need the pure text versions), and the output (I
>> have made this Java serializable specific - doesn't have to be).
>>
>> I have put comments inline in <xsl:template
>> match="wcs:Service"> in metadata_wcs_1.0.0.xsl, where I think
>> we are missing info, or have questions.  From the
>> capabilities we can't get time periods, and we struggle to
>> get some meaningful data.
>>
>> Please let me have your comments, I think I am going to go
>> down the stylesheet route for extracting the data and then
>> pulling it into Java and hence in the persistence model - if
>> this isn't recommended please let me know.
>>
>> Thanks,
>>
>> Norman
>>

-- 
Allan Doyle
+1.781.433.2695
adoyle at eogeo.org