[Geonetwork-devel] Import XML

GeoNetwork GeoNetwork Developer
1

Hello Carl,

I’m sending attached both files which I tried to validate but it didn’t work.
What’s that MP tool? What does it makes?
The XML files are here, hope you may find the problem.
If you don’t can you send me the procedures you made to import the data?
Thanks,
Felipe Costa

Carl Anderson carl.anderson@anonymised.com wrote:

Felipe,

Can you be more specific on your path from Arc Catalog to Geonetwork

did you try to import the

Relax. Yahoo! Mail virus scanning helps detect nasty viruses!

(attachments)

landsat2.shp.xml (4.28 KB)
landsat.shp.xml (9 KB)

2

Hi Felipe,
ArcCatalog does not generate standard XML. As a matter of fact, it does not even generate XML compliant to ESRI’s own DTD.
—quote from http://www.esri.com/metadata/ —
NOTE: DTDs require the elements in an XML file to be in a specific order. ArcCatalog cannot guarantee that the elements in the metadata files that it maintains will be in the correct order. A separate operation must order the elements in the XML file before it can be validated by the DTD.
—end quote—
In any case, you have to pipe the XML through an XSLT to strip extra stuff off.
Personally, I use ISO since that’s what everything will migrate to - even FGDC.
You can use Jeroen’s tool at http://193.43.36.138/software/tools/releases to do this or the TemplateExporter which is part of the developer samples.
See: http://webhelp.esri.com/arcgisdesktop/9.1/body.cfm?tocVisable=1&ID=-1&TopicName=Customizing%20metadata
The second method will allow export directly from ArcCatalog. Of course, if you are validating the XMLs then you must ensure all the mandatory fields in the wizard are filled.

–paul

Paul Grzeszczak
GIS Analyst / Programmer		 Dept. of Earth Sciences
University of Windsor

Felipe Costa <fsc7@anonymised.com>
Sent by: geonetwork-devel-admin@lists.sourceforge.net

2006-02-07 07:31 AM

To

Carl Anderson <carl.anderson@anonymised.com>, Geonetwork Devel <geonetwork-devel@lists.sourceforge.net>

cc

Subject

Re: [Geonetwork-devel] Import XML

Hello Carl,

I’m sending attached both files which I tried to validate but it didn’t work.
What’s that MP tool? What does it makes?
The XML files are here, hope you may find the problem.
If you don’t can you send me the procedures you made to import the data?
Thanks,
Felipe Costa

Carl Anderson carl.anderson@anonymised.com wrote:
Felipe,

Can you be more specific on your path from Arc Catalog to Geonetwork

did you try to import the .shp.xml files?
did you export the metadata as < ?? > then import it?
are you using Latin Characters or UTF-8 characters in your metadata?
did you check the “validate” box on import?
did you set the template to fgdc-std?

I have imported several metadata sets that originated with Arc Catalog
into Geonetwork.
I have also passed them through the MP tool (from USGS) first.

Felipe Costa wrote:

Hello,

I’m having problems when importing the xml data. I’d like to know how
can I import automatically the xml files from Arc Catalog to
geonetwork database.
I just can’t using ISO or FGDC, batch import or normal insert.
THanks,
Felipe Costa

Yahoo! Mail

  • Helps protect you from nasty viruses.

Relax. Yahoo! Mail virus scanning helps detect nasty viruses!<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd"><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>REQUIRED: The name of an organization or individual that developed the data set.</origin>
<pubdate>REQUIRED: The date when the data set is published or otherwise made available for release.</pubdate>
<title>landsat</title>
<geoform>vector digital data</geoform>
<onlink>\\RIONEGRO\Ibge\landsat.shp</onlink>
</citeinfo>
</citation>
<descript>
<abstract>REQUIRED: A brief narrative summary of the data set.</abstract>
<purpose>REQUIRED: A summary of the intentions with which the data set was developed.</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.</caldate>
</sngdate>
</timeinfo>
<current>REQUIRED: The basis on which the time period of content information is determined.</current>
</timeperd>
<status>
<progress>REQUIRED: The state of the data set.</progress>
<update>REQUIRED: The frequency with which changes and additions are made to the data set after the initial data set is completed.</update>
</status>
<spdom>
<bounding>
<westbc>
-76.749428</westbc>
<eastbc>
-32.265392</eastbc>
<northbc>
6.958051</northbc>
<southbc>
-35.490685</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>REQUIRED: Reference to a formally registered thesaurus or a similar authoritative source of theme keywords.</themekt>
<themekey>REQUIRED: Common-use word or phrase used to describe the subject of the data set.</themekey>
</theme>
</keywords>
<accconst>REQUIRED: Restrictions and legal prerequisites for accessing the data set.</accconst>
<useconst>REQUIRED: Restrictions and legal prerequisites for using the data set after access is granted.</useconst>
<native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.0.0.535</native>
</idinfo>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>String</sdtstype>
<ptvctcnt>444</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>0.000000</latres>
<longres>0.000000</longres>
<geogunit>Decimal degrees</geogunit>
</geograph>
<geodetic>
<horizdn>North American Datum of 1927</horizdn>
<ellips>Clarke 1866</ellips>
<semiaxis>6378206.400000</semiaxis>
<denflat>294.978698</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
landsat</enttypl>
</enttyp>
<attr>
<attrlabl>FID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>FNODE_</attrlabl>
</attr>
<attr>
<attrlabl>TNODE_</attrlabl>
</attr>
<attr>
<attrlabl>LPOLY_</attrlabl>
</attr>
<attr>
<attrlabl>RPOLY_</attrlabl>
</attr>
<attr>
<attrlabl>LENGTH</attrlabl>
</attr>
<attr>
<attrlabl>ORB_PTO_</attrlabl>
</attr>
<attr>
<attrlabl>ORB_PTO_ID</attrlabl>
</attr>
<attr>
<attrlabl>ORBPTO</attrlabl>
</attr>
</detailed>
</eainfo>
<distinfo>
<resdesc>Downloadable Data</resdesc>
<stdorder>
<digform>
<digtinfo>
<transize>0.058</transize>
</digtinfo>
</digform>
</stdorder>
</distinfo>
<metainfo>
<metd>20060201</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>REQUIRED: The organization responsible for the metadata information.</cntorg>
<cntper>REQUIRED: The person responsible for the metadata information.</cntper>
</cntorgp>
<cntaddr>
<addrtype>REQUIRED: The mailing and/or physical address for the organization or individual.</addrtype>
<city>REQUIRED: The city of the address.</city>
<state>REQUIRED: The state or province of the address.</state>
<postal>REQUIRED: The ZIP or other postal code of the address.</postal>
</cntaddr>
<cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</cntvoice>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
</metadata>
<?xml version="1.0"?>
<!--<!DOCTYPE metadata SYSTEM "http://www.esri.com/metadata/esriprof80.dtd">-->
<metadata xml:lang="en"><Esri><MetaID>{C6CE05AD-0D1B-4607-84DD-901592F985A0}</MetaID><CreaDate>20060201</CreaDate><CreaTime>16555700</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20060201</SyncDate><SyncTime>17102300</SyncTime><ModDate>20060201</ModDate><ModTime>17102300</ModTime></Esri><idinfo><native Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.0.0.535</native><descript><langdata Sync="TRUE">en</langdata><abstract>REQUIRED: A brief narrative summary of the data set.</abstract><purpose>REQUIRED: A summary of the intentions with which the data set was developed.</purpose></descript><citation><citeinfo><origin>REQUIRED: The name of an organization or individual that developed the data set.</origin><pubdate>REQUIRED: The date when the data set is published or otherwise made available for release.</pubdate><title Sync="TRUE">landsat</title><ftname Sync="TRUE">landsat</ftname><geoform Sync="TRUE">vector digital data</geoform><onlink
Sync="TRUE">\\RIONEGRO\Ibge\landsat.shp</onlink></citeinfo></citation><timeperd><current>REQUIRED: The basis on which the time period of content information is determined.</current><timeinfo><sngdate><caldate>REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.</caldate></sngdate></timeinfo></timeperd><status><progress>REQUIRED: The state of the data set.</progress><update>REQUIRED: The frequency with which changes and additions are made to the data set after the initial data set is completed.</update></status><spdom><bounding><westbc Sync="TRUE">-76.749428</westbc><eastbc Sync="TRUE">-32.265392</eastbc><northbc Sync="TRUE">6.958051</northbc><southbc Sync="TRUE">-35.490685</southbc></bounding><lboundng><leftbc Sync="TRUE">-76.749428</leftbc><rightbc Sync="TRUE">-32.265392</rightbc><bottombc Sync="TRUE">-35.490685</bottombc><topbc Sync="TRUE">6.958051</topbc></lboundng></spdom><keywords><theme><themekt>REQUIRED: Referen
ce to a formally registered thesaurus or a similar authoritative source of theme keywords.</themekt><themekey>REQUIRED: Common-use word or phrase used to describe the subject of the data set.</themekey></theme></keywords><accconst>REQUIRED: Restrictions and legal prerequisites for accessing the data set.</accconst><useconst>REQUIRED: Restrictions and legal prerequisites for using the data set after access is granted.</useconst><natvform Sync="TRUE">Shapefile</natvform></idinfo><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.0.0.535</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">landsat</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="001"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">-76.749428</wes
tBL><eastBL Sync="TRUE">-32.265392</eastBL><northBL Sync="TRUE">6.958051</northBL><southBL Sync="TRUE">-35.490685</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-76.749428</westBL><eastBL Sync="TRUE">-32.265392</eastBL><northBL Sync="TRUE">6.958051</northBL><southBL Sync="TRUE">-35.490685</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><metainfo><langmeta Sync="TRUE">en</langmeta><metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn><metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv><mettc Sync="TRUE">local time</mettc><metc><cntinfo><cntorgp><cntper>REQUIRED: The person responsible for the metadata information.</cntper><cntorg>REQUIRED: The organization responsible for the metadata information.</cntorg></cntorgp><cntaddr><addrtype>REQUIRED: The mailing and/or physical address for the organization or individual.</addrtype><city>REQUIRED: The
city of the address.</city><state>REQUIRED: The state or province of the address.</state><postal>REQUIRED: The ZIP or other postal code of the address.</postal></cntaddr><cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</cntvoice></cntinfo></metc><metd Sync="TRUE">20060201</metd><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><distinfo><resdesc Sync="TRUE">Downloadable Data</resdesc><stdorder><digform><digtinfo><transize Sync="TRUE">0.058</transize><dssiz
e Sync="TRUE">0.058</dssize></digtinfo></digform></stdorder></distinfo><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\RIONEGRO\Ibge\landsat.shp</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">0.058</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><spdoinfo><direct Sync="TRUE">Vector</direct><ptvctinf><esriterm Name="landsat"><efeatyp Sync="TRUE">Simple</efeatyp><efeageom Sync="TRUE">Polyline</efeageom><esritopo Sync="TRUE">FALSE</esritopo><efeacnt Sync="TRUE">444</efeacnt><spindex Sync="TRUE">TRUE</spindex><linrefer Sync="TRUE">FALSE</linrefer></esriterm><sdtsterm Name="landsat"><sdtstype Sync="TRUE">String</sdtstype><ptvctcnt Sync="TRUE">444</ptvctcnt></sdtsterm></ptvctinf></spdoinfo><spref><horizsys><cordsysn><geogcsn Sync="TRUE">GCS_Assumed_Geographic_1</geogcsn></cordsysn><geograph><geogunit
Sync="TRUE">Decimal degrees</geogunit><latres Sync="TRUE">0.000000</latres><longres Sync="TRUE">0.000000</longres></geograph><geodetic><horizdn Sync="TRUE">North American Datum of 1927</horizdn><ellips Sync="TRUE">Clarke 1866</ellips><semiaxis Sync="TRUE">6378206.400000</semiaxis><denflat Sync="TRUE">294.978698</denflat></geodetic></horizsys></spref><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">GCS_Assumed_Geographic_1</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="landsat"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">444</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><eainfo><detailed Name="landsat"><enttyp><enttypl Sync="TRUE">landsat</enttypl><enttypt Sync="TRUE">Feature Class</enttypt><enttypc Sync="TRUE">444</enttypc></enttyp><attr><attrlabl Sync="TRUE">FID</attrlabl><attalias Sync="TRUE">FID</att
alias><attrtype Sync="TRUE">OID</attrtype><attwidth Sync="TRUE">4</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Internal feature number.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">Shape</attrlabl><attalias Sync="TRUE">Shape</attalias><attrtype Sync="TRUE">Geometry</attrtype><attwidth Sync="TRUE">0</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Feature geometry.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Coordinates defining the features.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">FNODE_</attrlabl><attalias Sync="TRUE">FNODE_</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">TNODE_</attrlabl><attalias Sync="TRUE">TNODE_
</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">LPOLY_</attrlabl><attalias Sync="TRUE">LPOLY_</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">RPOLY_</attrlabl><attalias Sync="TRUE">RPOLY_</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">LENGTH</attrlabl><attalias Sync="TRUE">LENGTH</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">12</attwidth><atnumdec Sync="TRUE">3</atnumdec></attr><attr><attrlabl Sync="TRUE">ORB_PTO_</attrlabl><attalias Sync="TRUE">ORB_PTO_</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">ORB_PTO_ID</attrlabl><attalias Sync="TRUE">ORB_PTO_ID</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE
">ORBPTO</attrlabl><attalias Sync="TRUE">ORBPTO</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">10</attwidth></attr></detailed></eainfo><mdDateSt Sync="TRUE">20060201</mdDateSt></metadata>

3

Hello Developers,

I’m using a lot geonetwork to discover it’s capabilities and thanks for you all helping me about my questions. I have one more today.
Is it possible to make a query inserting a pair of coordinates and recovering maps that match to this coordinate?
How’s that possible? I tried but I couldn’t make it. I saw in the advanced search a field which have some options like “is in”, “is not in”,“is completely out”, etc… But I don’t know how to use it. Can you explain it to me?
Thanks in advance,
Felipe Costa

Brings words and photos together (easily) with
PhotoMail - it’s free and works with Yahoo! Mail.

4

Hi,
I am also interested in this. As a matter of fact, picking coordinates on a map would also be a great feature. Let’s say you start with a map of the world, you could zoom in on an area and drag a box around the area of interest to submit coordinates. I’ve seen applets that perform a similar function.

With respect to your query Felipe, I think that you would have to edit the regions.xml file under web/xml/ directory, to add your region and coordinates.

I actually tried this just now, and the location name shows up in the pull down menu in advanced search, but the results are not quite what I expected. Perhaps there is some logical problem with the overlapping/enclosing coordinates. Take the following scenario: Out of 426 total metadata entries, the search returns 9 that overlap, 375 that enclose, 370 that are fully outside of and 342 that are a particular location (about 0.05 degrees x 0.05 degrees). It seems to me, that if a dataset encloses a location should also overlap it. Also, evidently, judging from the result numbers, some locations that are fully outside of the specified area also enclose it. How can that be?

Let’s say that some of the datasets have the wrong coordinates specified, so that could contribute to the problem - I didn’t fully examine all of them. However, I can’t figure out why a particular dataset, whose coordinates I verified, would show up in both the ‘encloses’ results as well as the ‘fully outside of’ results.

Is anyone else having this problem?

–paul

Paul Grzeszczak
GIS Analyst / Programmer		 Dept. of Earth Sciences
University of Windsor

Felipe Costa <fsc7@anonymised.com>
Sent by: geonetwork-devel-admin@lists.sourceforge.net

2006-02-09 10:26 AM

To

Geonetwork Devel <geonetwork-devel@lists.sourceforge.net>

cc

Subject

[Geonetwork-devel] Query Maps inserting coordinates

Hello Developers,

I’m using a lot geonetwork to discover it’s capabilities and thanks for you all helping me about my questions. I have one more today.
Is it possible to make a query inserting a pair of coordinates and recovering maps that match to this coordinate?
How’s that possible? I tried but I couldn’t make it. I saw in the advanced search a field which have some options like “is in”, “is not in”,“is completely out”, etc… But I don’t know how to use it. Can you explain it to me?
Thanks in advance,
Felipe Costa

Brings words and photos together (easily) with
PhotoMail - it’s free and works with Yahoo! Mail.