New answers tagged metadata
1
Look at the NME project
With it, you can have all metadata supported by GDAL referenced in an XML (also an SQL output options) using the python script gdalogr_catalogue.py with a command like below
python gdalogr_catalogue.py -d /home/my_directory
After, it's up to you to adapt the retrieved XML from this utility to be able to compare it with anzlic ...
0
One way of doing it is to generate a really simple XML tree for each record in your spreadsheet, write an XSLT stylesheet to translate from your simple XML to ISO 19139, then use lxml.etree.XSLT to transform.
The major advantage of this is it keeps the complex iso19139 XML out of your python code which makes it much easier to debug. Some more ...
1
The INSPIRE Portal of the Grand-Duchy of Luxembourg is build on top Geoportal:
http://inspire.geoportail.lu/geoportal/catalog/main/home.page
2
Version 1.2.2 does use the REST API.
Geportal REST API:
http://sourceforge.net/apps/mediawiki/geoportal/index.php?title=REST_API_Syntax
Check out these sites. I'm not sure if any are running 1.2.2 but are probably not too far back:
http://geo.data.gov/geoportal/catalog/main/home.page
http://www.ga.gov.au/geoportal/catalog/main/home.page
...
3
Metadata is a dynamic thing. "Locking" it probably wouldn't be wise, even if you could. For example, what if they reproject your dataset? The metadata will be incorrect if it were "locked".
My suggestion: publish the metadata separately in a clearinghouse and distribute your dataset with links permanent URL to the to "authoritative" metadata. The link ...
Top 50 recent answers are included
