id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc
3967,Extract metadata of layer data automatically,armin11,mapserverbugs,"To fulfill the requirements of the european sdi ('''INSPIRE''') the ows must have filled the '''MetadataURL''' Tags with a link to an existing iso19139 file (maybe over http-get or csw getrecordbyid request). This file should describe the data which is used to serve the layer/featuretype thru the ows. 
Filling this tag by hand is a very bad idea. S.o. have to write the link or s.th. else into the mapfile.

If mapserver is able to read a metadata file which is in the some directory (for database there must be another solution like extent postgis geometry_columns with some more fields) as the datafile (tiff/shape/tab/gml) it maybe easy to fill the MetadataURL automatically and serve this metadata itself via http!
In such a case the needed service-data-metadata coupling (tight) as claimed by '''iso19119''' ([http://portal.opengeospatial.org/files/?artifact_id=122]) is realized and INSPIRE may have a little chance to work ;-) .

It will be an extension to the work which is done in google summer of code 2011 [http://trac.osgeo.org/mapserver/wiki/gsoc2011]. The work there is only the part which must be done to generate the service metadata records - but the coupling between data- and service-metadata is much more relevant for implementing the european sdi!
The european geoportal will '''not work''' if this is not realized - the concept is a little bit to difficult :-( .

The solution maybe simple for filebased geodata. It's the same as reading and interpreting a world file. The metadata-file should have the same name but another file extension or mimetype. I don't know if there is already a type for standardized geo-metadata. Maybe we can use '''*.iso19139'''.

Please feel free to comment this ticket!





",enhancement,closed,normal,6.2 release,WMS Server,unspecified,normal,wontfix,,