I have been working with the ANZMET tool from OSDM also. I have got it to work with ArcMap (version 9.3.1). The Sequence I used is this:
1. Write your metadata using the ANZmet tool.
2. Take the finished xml file from the ANZ process and import it into arc catalog.
3. The metadata tab in arccatalog willl have to be set to ISO 19139.
4. Metadata attached to your dataset is now visable in arc.
Problems / Issues: If you have attributes that require detailed field descriptions.. you cant see these.
The other Alternative is to use the ISO wizard in arc-catalog.
Hopefully this helps.
Thanks for the response.
Yeah that does seem to work. But, if you try exporting that xml file out again and opening it with the ANZMet tool, you'll find that it says "Non-compliant (ANZLIC) XML File: Not associated to a dataset", so not too sure what that means exactly.
Also, it would be good to have the ANZLIC XML file styled correctly. For example, In ANZLIC for distribution information it has the element name Address, which is listed like this:
Address 16 Nicolaus St
Upper Hutt 5018
But in ISO 19139 it is:
Delivery point�??16 Nicolaus St
City�?? Upper Hutt
Postal code�?? 5018
Country�?? New Zealand
So, it would be good to import an XML file in and have it styled this way and then export it out and for it to be accepted in the ANZMet tool.
Can I easily create an ANZLIC Metadata style?
Curious to know if any progress has been made on this?
I currently have to manage the same metadata twice, within ArcGIS and outside ArcGIS.
Also having same issues as documented above in 10 - can import and edit ANZLIC metadata, however "to ISO 19139" translator doesn't seem to export an ANZLIC compliant xml, i.e. am also receiving "non compliant ANZLIC metadata" message in ANZMET.
Would also like to see an ANZLIC Metadata style.
Any progress made on this?
The key is to know the difference in the metadata XML statement. ESRI-ISO is not ISO19139 compliant. A ISO19139 XML implementation of ISO19115 should have the following up the top of the XML statement.
The ANZLIC version of ISO19139 is just sitpulation on what elements of the ISO19139 standard are to be used ie whether the obligation to use an element is mandatory or optional in Australia / NZ. And therefore will be accepted when made available to the Australian Spatial Data Directory or Australian Ocean Data Network (Bluenet)
<gmd:MD_Metadata xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gml="http://www.opengis.net/gml" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gsr="http://www.isotc211.org/2005/gsr" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://www.isotc211.org/2005/gmd/gmd.xsd http://www.opengis.net/gml http://www.isotc211.org/2005/gml/gml.xsd http://www.w3.org/1999/xlink http://www.isotc211.org/2005/xlink/xlinks.xsd">
If it has anything like <esri> it will not work with ISO19139. There are converters available on line.
The attached stylesheet can be put in
Change the name before saving I suggest removing the ver<date> from the file name.
This will allow you to view the ANZLIC ISO19139 metadata in catalog.
The attached is a first cut I did last year and haven't revised since.
Please note if your organisation want to view additional elements of the ISO19139 standard you will need to edit the attached.
Any comment or improvements are more than welcome.
Many thanks for sharing that valuable information which looks from the pathname you specified (C:\programfiles\arcgis\metadata\stylesheets\) to be a 9.x solution.
I'm trying to come to grips with ANZLIC Metadata at ArcGIS 10 so am wondering if you've tried to adapt your solution for that?
I tried simply putting your *.xsl into C:\Program Files\ArcGIS\Desktop10.0\Metadata\Stylesheets but did not meet with instant success and ran out of time to try and experiment further.
:) I too would be interested in get a ANZLIC metadata tool working in ArcGIS 10.
as Graeme mentioned you can stick the XSL in the ...Desktop10.0\Metadata\Stylesheets directory. When you go into ArcCatalogue to select the ANZLIC stylesheet, it comes up with the option 'item description'. When you select the item description and begin to edit, some of the elements like bounding coordinates etc are missing.
Interested to see this work
Moreton Bay Regional Council
I just found this in Jack Dangermond's Q&A for Esri UC 2012:
Q: Does ArcGIS 10.1 support the ANZLIC standard?
No. However, Esri's distributors, Esri Australia and Eagle Technologies, are actively collaborating on a custom version of the ArcGIS metadata editor. They are creating this editor using the ArcGIS Metadata Toolkit. This will mean support for ANZLIC later this year.
Folks,1 of 1 people found this helpful
Just as a belated update to this thread - the tools mentioned above are available at the following link:
1 of 1 people found this helpful
Found this tool but unfortunately when I go to edit any metadata with the ANZLIC metadata style it crashes my session (closes ArcCatalog or Catalog window in ArcMap). Anyone else have this issue?
Currently submitted error with ESRI so will await their response.
I haven't used the recent ESRI Australia Metadata tool so I cannot comment about it however here are some more metadata ideas (just what you needed right?)
I haven't written any anzlic meta recently however I suggest trying the 19139 style sheet. You might find that works easier with ANZLIC domains better than say Inspire or FDGC. That's what I used when I couldn't use a custom version from ANZMET etc. Geonetwork (Open-source) and Blue-Net (an Australian flavour of version of Geo-network) can give you some more metadata controls and editing. If you get the XML's from these you can associate them via Arc-Catalog. Its a long work around but it might help. - Failing that - talk to the specialists at Redlands.
Hope this helps.
You might want to have a look at the esri blog about metadata as well.