[Thread Prev][Thread Next][Index]
Re: Fwd: Re: Includes in LAS xml files
Ben,
I believe there are some errors in your XML:
you cannot insert any <variables> inside a <category> </category> pair, can you ?
In my belief, <category> tag only can include other <category> tag or <filter> tag....
<variables> should be declares inside a <datasets> item.
Jean-Marie
Ben Burford wrote:
> Hi Jon,
>
> I'm not sure if I understood what you had in mind, but the following is my
> explanation of what I tried (which didn't work). Basically, I tried to move
> variables, grids and axes from the lowest level (
> "CEOP_Insitu_Surface_Mongolia_DGS.xml") up into the "Insitu_Datasets.xml" fi
> le.
>
> (My las.xml file looks like this:)
> <?xml version='1.0' ?>
> <!DOCTYPE spec SYSTEM "spec.dtd" [
>
> <!-- Declaration of operations files to be included -->
> <!ENTITY StdOperations SYSTEM "operations.xml">
> <!ENTITY insitu_operations SYSTEM "insitu_operations.xml">
>
> <!-- Declaration of dataset files to be included -->
> <!ENTITY InsituDatasets SYSTEM "Insitu_Datasets.xml">
>
> <!-- Declaration of variables files to be included -->
> <!ENTITY CEOP_Insitu_Surface_Mongolia_DGS SYSTEM
> "CEOP_Insitu_Surface_Mongolia_DGS.xml">
> ]>
>
> <lasdata>
>
> <las_categories>
> &InsituDatasets;
> </las_categories>
>
> <institution name="Pacific Marine Environmental Lab"
> url="http://www.pmel.noaa.gov"/>
> <!-- Define properties -->
> <properties>
> (deleted for space)
> </properties>
>
> <!-- Operations supported by this server -->
> <operations url="http://172.16.7.82/las-bin/LASserver.pl";>
> &StdOperations;
> &insitu_operations;
> </operations>
>
> <!-- Datasets provided by this server -->
> &CEOP_Insitu_Surface_Mongolia_DGS;
>
> </lasdata>
>
> (My Insitu_Datasets.xml file looks like this:)
> <category name="Insitu">
> <category name="Surface">
> <category name="CAMP_Mongolia">
>
> <variables>
> <Station_Pressure name="Station Pressure" units="hPa (mb)">
> <link match="/lasdata/grids/DGS_XYZT_grid"/>
> </Station_Pressure>
> </variables>
> (etc. total of 19 variables)
>
> <grids>
> <DGS_XYZT_grid>
> <link match="/lasdata/axes/DGS_X"/>
> <link match="/lasdata/axes/DGS_Y"/>
> <link match="/lasdata/axes/DGS_T"/>
> </DGS_XYZT_grid>
> </grids>
> <axes>
> <DGS_X units="degree_east" type="x">
> <arange start="106.369" step="1" size="1"/>
> </DGS_X>
> <DGS_Y units="degree_north" type="y">
> <arange start="46.1273" step="1" size="1"/>
> </DGS_Y>
> <DGS_T units="hours" type="t">
> <arange start="2002-Oct-01 01:00:00" step="1" size="48"/>
> </DGS_T>
> </axes>
>
> <category name="DGS">
> <filter action="apply-dataset" equals="CEOP Surface Mongolia DGS"/>
> </category>
> (DGS is the name of a station at the "CAMP_Mongolia" Reference site. There
> are
> up to 25 stations at a single reference site.)
>
> </category>
> ("CAMP_Mongolia" is one of a list of 36 reference sites under "Surface")
> </category>
> ("Surface" is one of four types of data under "Insitu")
> </category>
>
> (My CEOP_Insitu_Surface_Mongolia_DGS.xml file looks like this:)
> <datasets>
> <Insitu_Surface_Mongolia_DGS name="CEOP Surface Mongolia DGS"
> url="Insitu/CAMP_Mongolia_20021001_20030331sfc.data"
> doc="">
> <properties>
> <database_access name="Dapper">
> <db_name>dods-3.4/nph-dods/CEOP</db_name>
> <db_host>http://dodsdev.gso.uri.edu</db_host>
> (most of properties deleted)
> </database_access>
> </properties>
>
> </Insitu_Surface_Mongolia_DGS>
> </datasets>
>
> I don't see how I could move <filter action="apply-dataset"
> equals="CEOP Surface Mongolia DGS"/>
> down, because the next level down is the file that it refers to, which is at
> the lowest level. The error that I got from make was:
>
> Resolving links...
> Match attribute for link href '/lasdata/grids/DGS_XYZT_grid' doesn't point to
> valid element at ../xml/perl/LASDB.pm line 436.
> make: *** [../ui/config.js] Error 255
>
> Ideally I would move the variables up one level to being under:
> <category name="Insitu">
> <category name="Surface">
> since all of the "Surface" variables are the same.
>
> I put grids and axes at this level:
> <category name="Insitu">
> <category name="Surface">
> <category name="CAMP_Mongolia">
> because, at least for now, I want the same time and location for all of the
> stations under "CAMP_Mongolia" and this will save me time building xml files.
>
> Any ideas on how I can move variables, grids and axes from the lowest level?
> I
> attached my 3 files in case you want to experiment with them.
>
> Thank you,
>
> Ben
>
> >
> > Delivered-To: benb@restec.or.jp
> > Date: Thu, 07 Oct 2004 10:05:42 -0700
> > From: Jonathan Callahan
> > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4)
> > Gecko/20030624 Netscape/7.1 (ax)
> > X-Accept-Language: en-us, en
> > To: Ben Burford
> > Cc: las_users@noaa.gov,J-M Epitalon ,Roland Schweitzer
> > Subject: Re: Includes in LAS xml files
> >
> > Ben,
> >
> > With the current XML specification you can define a single grid that can be
> > referenced by multiple variables. For folks running models on the same grid
> > this can be useful. In your case, each grid is unique to a specific
> > longitude and latitude so you must create and reference a separate grid for
> > each dataset.
> >
> > For Ferret (the LAS back end) to work, each variable must be identified with
> > a grid. What you really want to do is associate the <grid> at the <dataset>
> > level rather than at the <variable> level. Then all your <variables> XML
> > code would look the same in each file because they would inherit the unique
> > grid specified at the <dataset> level. This kind of inheritance works
> > automatically for things like <properties> but we've never tried it out with
> > the <link match=...)..
> >
> > I doubt this will work in the current incarnation of our XML parsing but you
> > can try the following: move <link match= ...> line up to make it a an
> > element of the <insitu_Surface_Mongolia_DGS ...> (at the same level as the
> > <properties> defined there). Then remove the <link match=...> lines from
> all
> > the <variables>. In the best of all possible worlds your variables will
> > inherit this information and your problem will be solved.
> >
> > Otherwise you'll have to write some scripts to automatically generate the
> > unique XML files you need (a straightforward, if unwelcome task).
> >
> >
> > -- Jon
> >
> >
> > Ben Burford wrote:
> >>
> >>
> >> Hello Jean-Marie,>> >> I tried you idea and it works! However, it n
> egates what I'm trying to accom>> plish!!>> >> I don't want to include the s
> econd line ( <link match="/lasdata/grids/DGS_XY>> ZT_grid"/>
> ) in the xml include file, because it has to be unique for each >> fi
> le. I have about 200 sets of automated weather station time series dat
> a f>> rom different locations. This will result in my creating 200 fil
> es like CEO>> P_Insitu_Surface_Mongolia_DGS.xml all of which have the
> same set of 19 vari>> ables (e.g. Air_Temperature), but all of which have a
> different station name>> (i.e. the "DGS" part, and all have a dif
> ferent lat/lon location). The stru>> cture of my CEOP_Insitu_Surface_M
> ongolia_DGS.xml file looks like this:>> >> <datasets>>> <Ins
> itu_Surface_Mongolia_DGS name="CEOP Surface Mongolia DGS">>
> &nbs
> p; url="Insitu/CAMP_Mongolia_20021001_20030331s
> fc.data">>
> doc="">>> &nbs
> p; <properties>>> (stuff deleted)>> </properties>>> >> &n
> bsp; <variables>>> >> <Air_Temperature name="Air
> Temperature" units="Celsius">>> <lin
> k match="/lasdata/grids/DGS_XYZT_grid"/>>> </Ai
> r_Temperature>>> >> <Dew_Point_Temperature name="Dew
> Point Temperature" units="Celsius">>>
> <link match="/lasdata/grids/DGS_XYZT_grid"/>>>
> </Dew_Point_Temperature>>> >> (etc., continues for a total of 19 varia
> bles)>> >> </variables>>> >> </Insitu_Surface_Mongolia_DGS&
> gt;>> </datasets>>> <grids>>> <DGS_XYZT_grid>>> &l
> t;link match="/lasdata/axes/DGS_X"/>>> <link match=&q
> uot;/lasdata/axes/DGS_Y"/>>> <link match="/lasdata/ax
> es/DGS_T"/>>> </DGS_XYZT_grid>>> </grids>>> <axes>
> ;>> <DGS_X units="degree_east" type="x">>>
> <arange start="106.369" step="1" size="1"/
> >>> </DGS_X>>> <DGS_Y units="degree_north" type=&quo
> t;y">>> <arange start="46.1273" step="1&quo
> t; size="1"/>>> </DGS_Y>>> <DGS_T units="hours&
> quot; type="t">>> <arange start="2002-Oct-01 01:
> 00:00" step="1" size="48"/>>> </DGS_T>>>
> </axes>>> >> >> The structure "DGS_ . . ." (shown in these n
> ext lines):>> >> <link match="/lasdata/grids/DGS_
> XYZT_grid"/>>> >> <DGS_XYZT_grid>>> <link match=&qu
> ot;/lasdata/axes/DGS_X"/>>> <link match="/lasdata/axe
> s/DGS_Y"/>>> <link match="/lasdata/axes/DGS_T"/&
> gt;>> </DGS_XYZT_grid>>> >> <DGS_X units="degree_east"
> type="x">>> </DGS_X>>> <DGS_Y units="degree_nor
> th" type="y">>> </DGS_Y>>> <DGS_T units="h
> ours" type="t">>> </DGS_T>>> >> The structure "
> ;DGS_ . . ." has to be unique in each of the 200 files. So if>>
> my include includes all three lines, i.e. if &InsituAirTemperature
> ; includ>> es:>> <Air_Temperature name="Air Temperature
> " units="Celsius">>> <link match=&qu
> ot;/lasdata/grids/DGS_XYZT_grid"/>>> </Air_Temperatu
> re>>> >> then the "DGS_XYZT" part is repeated, and xml doesn't
> allow repeats of this >> in the 200 files. >> >> I want a single copy
> of the following line identical/repeated in 200 files:>> <Ai
> r_Temperature name="Air Temperature" units="Celsius">
> >> >> but I can't have the second line repeated at all:>>
> <link match="/lasdata/grids/DGS_XYZT_grid"/>>> >> I may be
> stuck with an unfriendly structure. Does anybody see any solutions?>>
> >> Thank you,>> >> Ben>> >> >> >> At 09:11 2004/10/07 +0200, you wrote:>> &n
> bsp; </pre>>> <blockquote type=cite cite>>> Ben,>> >> yes, I believe I can s
> ee what is wrong...>> >> I guess that the entity you include should contain
> a valid start tag match>> >> </blockquote>>> ed with>> &n
> bsp; >> <blockquote type=cite cite>>> a valid end tag.>> >> In your example,
> file Insitu_Air_Temperature.xml should contain all the th>> &nb
> sp; >> </blockquote>>> ree>> >> <blockquote type=cite cite>>> lines:>
> > <Station_Pressure name="Station Pressure" units="
> hPa (mb)">>> <link match="/lasdata/grids/
> DGS_XYZT_grid"/>>> </Station_Pressure>>> >> match
> ing <Station_Pressure ...> start tag with </Station_Pre
> ssure>>> >> Did you try that ?>> >> Jean-Marie Epitalon>> >> >> >> Ben Bu
> rford wrote:>> >> >> <blockquote type=cite cite>>> Hi Joe
> ,>> >> Thanks, but it didn't work. I hope someone can spot a problem (
> like may>> >> </blockquote></blockquote>>> be
> a>> >> <blockquote type=cite cite><blockquote type=cite cite>>> mis
> sing semicolon). Here are the details:>> >> I modified my las.xml file
> as follows:>> <?xml version='1.0' ?>>> <!DOCTYPE spec SYSTEM "
> ;spec.dtd" [>> >> <!-- Declaration of operations files to be include
> d -->>> <!ENTITY StdOperations SYSTEM "operations.xml">>>
> <!ENTITY insitu_operations SYSTEM "insitu_operations.xml">>
> > >> <!-- Declaration of dataset files to be included -->>> <!ENTIT
> Y InsituDatasets SYSTEM "Insitu_Datasets.xml">>> >> (note: this
> next item was already in the las.xml file)>> <!-- Declaration of variabl
> es files to be included -->>> <!ENTITY CEOP_Insitu_Surface_Mongolia_DG
> S SYSTEM "CEOP_Insitu_Surface_Mo>> >> </
> blockquote></blockquote>>> ngol>> >> <blockquote type=cite cite><bloc
> kquote type=cite cite>>> ia_DGS.xml">>> >> (note: I added this next
> item to the xml.file)>> <!-- Declaration of variable names files to be in
> cluded -->>> <!ENTITY InsituAirTemperature SYSTEM "Insitu_Air_Tem
> perature.xml">>> ]>>> >> <lasdata>>> <las_categor
> ies>>> &InsituDatasets;>> </las_categories>>> (no
> te: other stuff deleted)>> >> (note: this next line was already in las.xml)>
> > <!-- Datasets provided by this server -->>> &CEOP_Insitu_Surface
> _Mongolia_DGS;>> </lasdata>>> >> Next, I created a new xml file Insitu
> _Air_Temperature.xml containing thi>> >> </bl
> ockquote></blockquote>>> s on>> >> <blockquote type=cite cite><blockq
> uote type=cite cite>>> e line:>> <Station_Pressure name=&quo
> t;Station Pressure" units="hPa (mb)">>> >> Next, I modifie
> d the file CEOP_Insitu_Surface_Mongolia_DGS.xml as follows.>> First, the ori
> ginal version:>> <datasets>>> <Insitu_Surface_Mongolia_DGS name=&q
> uot;CEOP Surface Mongolia DGS">> &n
> bsp; url=&
> quot;Insitu/CAMP_Mongolia_20021001_20030331sfc.data">> &nbs
> p; &n
> bsp; doc="">>> (note: other stuff deleted)>>
> <variables>>> <Station_Pressure name="Station Pr
> essure" units="hPa (mb)">>> <link ma
> tch="/lasdata/grids/DGS_XYZT_grid"/>>> </Statio
> n_Pressure>>> >> I modified this file by replacing one line in the variab
> les section as f>> >> </blockquote></blockquo
> te>>> ollo>> >> <blockquote type=cite cite><blockquote type=cite cite
> >>> ws:>> <variables>>> &InsituAirTemperature;
> >> <link match="/lasdata/grids/DGS_XYZT_grid"
> ;/>>> </Station_Pressure>>> >> The error message that
> I got from the make was:>> >> asynchronous entity at line 2, column 0, byte
> 63:>> <Station_Pressure name="Station Pressure" un
> its="hPa (mb)">>> >> ^>> >> error in processing external entity
> reference at line 32, column 3, byte>> >> </
> blockquote></blockquote>>> 901:>> >> <blockquote type=cite cite><blo
> ckquote type=cite cite>>> <variables>>> >> &In
> situAirTemperature;>> ==^>> <link match="/lasdata
> /grids/DGS_XYZT_grid"/>>> </Station_Pressure>>> >
> > error in processing external entity reference at line 53, column 0, byte>>
> >> </blockquote></blockquote>>> 1649:>> &nb
> sp; >> <blockquote type=cite cite><blockquote type=cite cite>>> <!-- Data
> sets provided by this server -->>> ^>> &CEOP_Insitu_Surface_Mongolia_
> DRS;>> at /usr/lib/perl5/site_perl/5.6.0/i386-linux/XML/Parser.pm line 185>
> > make: *** [../ui/config.js] Error 255>> >> What does "asynchronous en
> tity" mean in this case?>> >> After this I tried one more thing.
> I added &InsituAirTemperature; t>> &
> nbsp; >> </blockquote></blockquote>>> o la>> >> <blockquo
> te type=cite cite><blockquote type=cite cite>>> s.xml as follows:>> <!--
> Datasets provided by this server -->>> &CEOP_Insitu_Surface_Mongolia_
> DGS;>> &InsituAirTemperature;>> </lasdata>>> >> But I got exactly
> the same error message.>> >> Does anyone see anything wrong?>> >> Thanks,>>
> >> Ben>> >> At 15:13 2004/10/06 -0700, you wrote:>>
> >> <blockquote type=cite cite>>> Hi Ben,>> I have no example for you
> at the moment, but I have an explanation which>> I think will help.>> XML EN
> TITIES are declared in the DOCTYPE definition which must be>> declared befor
> e the first element in the XML document.>> Therefore all ENTITIES must be de
> clared in your root document which by>> default is las.xml (the first xml el
> ement in the las.xml file is <lasd>>
> >> </blockquote></blockquote></blockquote>>> ata>)>> >> <bl
> ockquote type=cite cite><blockquote type=cite cite><blockquote type=cite cit
> e>>> Once it is declared there, then you can use the reference anywhere>> wi
> thin the document>> i.e.>> these two Entities are declared in the las.xml DO
> CTYPE definition>> ----------------------------->> <?xml version='1.0' ?&
> gt;>> <!DOCTYPE spec SYSTEM "spec.dtd" [>> >> <!-- Declarati
> on of dataset files to be included -->>> <!ENTITY ceop_surf_mong_dgs S
> YSTEM "CEOP_Insitu_Surface_Mongolia_DGS.x>> &nb
> sp; >> </blockquote></blockquote></blockquote>>> ml">>>
> >> <blockquote type=cite cite><blockquote type=cite cite><blockquote
> type=cite cite>>> <!-- Other Entities -->>> <!ENTITY VarNameStation
> Pressure SYSTEM "Var_Name_Station_Pressure.xml">>> >> ]>>> &
> lt;lasdata>>> [...]>> ------------------------------>> now you can use &q
> uot;&ceop_surf_mong_dgs;" as a reference in the las.xml>> document
> and you can use "&VarNameStationPressure;" in the las.xml>> do
> cument or in CEOP_Insitu_Surface_Mongolia_DGS.xml.>> >> Hope this helps.>> >
> > Joe>> ------------------------------------->> >> Ben Burford wrote:>> >> &
> nbsp; >> <blockquote type=cite cite>>> H
> ello All,>> >> I'm a beginner at XML and I'm building LAS menus. I hav
> e a category >> >> </
> blockquote></blockquote></blockquote></blockquote>>> file>> >> <block
> quote type=cite cite><blockquote type=cite cite>>> th>> &
> nbsp; >> <blockquote type=cite cite><blockquote type=cite cite>>> at (
> partially) looks like:>> >> (file is Insitu_Datasets.xml)>> <category nam
> e="Insitu">>> >> <category name="Surface">>> >
> > <category name="CAMP_Mongolia">>>
> <category name="BTS">>>  
> ; <filter action="apply-dataset" equals="CEOP Surface Mong
> olia >> >> </blockquo
> te></blockquote></blockquote></blockquote>>> BTS"/>>> >> <blo
> ckquote type=cite cite><blockquote type=cite cite><blockquote type=cite cite
> ><blockquote type=cite cite>>> </category>>>
> >> (this leads to the file CEOP_Insitu_Surface_Mongolia_DGS.xml which co>> &
> nbsp; >> </blockquote></bloc
> kquote></blockquote></blockquote>>> ntai>> >> <blockquote type=cite c
> ite><blockquote type=cite cite>>> ns)>> >> <b
> lockquote type=cite cite><blockquote type=cite cite>>> <datasets>>> &l
> t;Insitu_Surface_Mongolia_DGS name="CEOP Surface Mongolia DGS">> &
> nbsp;  
> ; url="Insitu/CAMP_Mongolia_20021001_20030331sf
> c.data">> &
> nbsp; doc="">>> <proper
> ties>>> (properties stuff not important)>> </properties>>> >> &l
> t;variables>>> >> <Station_Pressure name="Station Pressure
> " units="hPa (mb)">>> <link match="/l
> asdata/grids/DGS_XYZT_grid"/>>> </Station_Pressure>>> >
> > (etc. for more variables, then grids then axes).>> In this line:>>
> <Station_Pressure name="Station Pressure" units="hPa (mb)&
> quot;>>> >> Station Pressure will appear as a menu entry. Thi
> s list of variable>>
> >> </blockquote></blockquote></blockquote></blockquote>>> s wi>> >> <
> blockquote type=cite cite><blockquote type=cite cite>>> ll>> &nb
> sp; >> <blockquote type=cite cite><blockquote type=cite cite>>>
> appear in about 100 different menu pages (and therefore in about 100 >> &nbs
> p; >> </blockquote></blockqu
> ote></blockquote></blockquote>>> diff>> >> <blockquote type=cite cite
> ><blockquote type=cite cite>>> ere>> >> <bloc
> kquote type=cite cite><blockquote type=cite cite>>> nt xml files, one for ea
> ch location) for several locations and statio>> &nbs
> p; >> </blockquote></blockquote></blockquote></block
> quote>>> ns w>> >> <blockquote type=cite cite><blockquote type=cite c
> ite>>> ith>> >> <blockquote type=cite cite><b
> lockquote type=cite cite>>> in locations. I want to make this line an
> xml file/xml include so th>>  
> ; >> </blockquote></blockquote></blockquote></blockquote>>> at,>> &nbs
> p; >> <blockquote type=cite cite><blockquote type=cite cite>>> if>> &n
> bsp; >> <blockquote type=cite cite><blockquote type=cite c
> ite>>> I want to change the text of the menu item, I only change it in the o
> >> >> </blockquote></
> blockquote></blockquote></blockquote>>> ne x>> >> <blockquote type=ci
> te cite><blockquote type=cite cite>>> ml>> >>
> <blockquote type=cite cite><blockquote type=cite cite>>> file, and not 100
> xml files. In other words, I want to create the xm>>  
> ; >> </blockquote></blockquote></blockqu
> ote></blockquote>>> l fi>> >> <blockquote type=cite cite><blockquote
> type=cite cite>>> le>> >> <blockquote type=ci
> te cite><blockquote type=cite cite>>> Var_Name_Station_Pressure.xml which wo
> uld contain one line:>> >> <Station_Pressure name="Station Pr
> essure" units="hPa (mb)">>> >> and then in CEOP_Insitu_Sur
> face_Mongolia_DGS.xml put &VarNameStationP>> &nb
> sp; >> </blockquote></blockquote></blockquote></bloc
> kquote>>> ress>> >> <blockquote type=cite cite><blockquote type=cite
> cite>>> ure>> >> <blockquote type=cite cite><
> blockquote type=cite cite>>> ; as in:>> >> <variables>>> >> &am
> p;VarNameStationPressure;>> <link match="/lasdata/grids
> /DGS_XYZT_grid"/>>> </Station_Pressure>>> >> so the 1 l
> ine would be substituted. I created the xml file Var_Name_>> &nb
> sp; >> </blockquote></blockquote><
> /blockquote></blockquote>>> Stat>> >> <blockquote type=cite cite><blo
> ckquote type=cite cite>>> ion>> >> <blockquot
> e type=cite cite><blockquote type=cite cite>>> _Pressure.xml and chang
> ed my original xml file by changing the one l>> &nbs
> p; >> </blockquote></blockquote></blockquote></block
> quote>>> ine>> >> <blockquote type=cite cite><blockquote type=cite ci
> te>>> to>> >> <blockquote type=cite cite><blo
> ckquote type=cite cite>>> &VarNameStationPressure; as I show just
> above. I also tried putti>>  
> ; >> </blockquote></blockquote></blockquote></blockquote>>> ng t
> >> >> <blockquote type=cite cite><blockquote type=cite cite>>> he>> &
> nbsp; >> <blockquote type=cite cite><blockquote type
> =cite cite>>> following at the beginning of the CEOP_Insitu_Surface_Mongolia
> _DGS.xm>> >> </blockq
> uote></blockquote></blockquote></blockquote>>> l fi>> >> <blockquote
> type=cite cite><blockquote type=cite cite>>> le:>> &
> nbsp; >> <blockquote type=cite cite><blockquote type=cite cite>>> <?xml v
> ersion='1.0' ?>>> <!DOCTYPE spec SYSTEM "spec.dtd" [>> >> &l
> t;!ENTITY VarNameStationPressure SYSTEM "Var_Name_Station_Pressure.xml&
> quot;>>> >> ]>>> >> So, is it possible to put this one line ( &nb
> sp; <Station_Pressure name="S>>
> >> </blockquote></blockquote></blockquote></blockquote>>>
> tati>> >> <blockquote type=cite cite><blockquote type=cite cite>>> o
> n>> >> <blockquote type=cite cite><blockquote
> type=cite cite>>> Pressure" units="hPa (mb)"> ) in a sepa
> rate xml file and then put it >> &
> nbsp; >> </blockquote></blockquote></blockquote></blockquote>>> into>>
> >> <blockquote type=cite cite><blockquote type=cite cite>>> CE>> &n
> bsp; >> <blockquote type=cite cite><blockquote type=
> cite cite>>> OP_Insitu_Surface_Mongolia_DGS.xml as an xml include?>> >
> > If anyone has an existing xml file(s) as an example that you can send>> &n
> bsp; >> </blockquote></block
> quote></blockquote></blockquote>>> me>> >> <blockquote type=cite cit
> e><blockquote type=cite cite>>> as>> >> <bloc
> kquote type=cite cite><blockquote type=cite cite>>> attached files, that wou
> ld be the ideal and easy way to explain.>> >> Thanks very much,>> >> Ben>> >
> > >> >> >> >> </block
> quote></blockquote></blockquote>>> >> >> </blockquote>>>
> >> >> </blockquote>>> </blockquote>>> </html>>>
> >>>
> >>> Ben, yes, I believe I can see what is wrong... I guess that the entity you
> >>> include should contain a valid start tag match
> >>
> >> ed with
> >>>
> >>> a valid end tag. In your example, file Insitu_Air_Temperature.xml should
> >>> contain all the th
> >>
> >> ree
> >>>
> >>> lines: <Station_Pressure name="Station Pressure" units="hPa (mb)">
> >>> <link match="/lasdata/grids/DGS_XYZT_grid"/> </Station_Pressure>
> >>> matching <Station_Pressure ...> start tag with </Station_Pressure> Did
> >>> you try that ? Jean-Marie Epitalon Ben Burford wrote:
> >>>>
> >>>> Hi Joe, Thanks, but it didn't work. I hope someone can spot a problem
> >>>> (like may
> >>>
> >>
> >> be a
> >>>
> >>>>
> >>>> missing semicolon). Here are the details: I modified my las.xml file as
> >>>> follows: <?xml version='1.0' ?> <!DOCTYPE spec SYSTEM "spec.dtd" [ <!--
> >>>> Declaration of operations files to be included --> <!ENTITY StdOperations
> >>>> SYSTEM "operations.xml"> <!ENTITY insitu_operations SYSTEM
> >>>> "insitu_operations.xml"> <!-- Declaration of dataset files to be included
> >>>> --> <!ENTITY InsituDatasets SYSTEM "Insitu_Datasets.xml"> (note: this n
> ext
> >>>> item was already in the las.xml file) <!-- Declaration of variables files
> >>>> to be included --> <!ENTITY CEOP_Insitu_Surface_Mongolia_DGS SYSTEM
> >>>> "CEOP_Insitu_Surface_Mo
> >>>
> >>
> >> ngol
> >>>
> >>>>
> >>>> ia_DGS.xml"> (note: I added this next item to the xml.file) <!--
> >>>> Declaration of variable names files to be included --> <!ENTITY
> >>>> InsituAirTemperature SYSTEM "Insitu_Air_Temperature.xml"> ]> <lasdata>
> >>>> <las_categories> &InsituDatasets; </las_categories> (note: other st
> uff
> >>>> deleted) (note: this next line was already in las.xml) <!-- Datasets
> >>>> provided by this server --> &CEOP_Insitu_Surface_Mongolia_DGS; </lasdata>
> >>>> Next, I created a new xml file Insitu_Air_Temperature.xml containing thi
> >>>>
> >>>
> >>
> >> s on
> >>>
> >>>>
> >>>> e line: <Station_Pressure name="Station Pressure" units="hPa (mb)">
> >>>> Next, I modified the file CEOP_Insitu_Surface_Mongolia_DGS.xml as follo
> ws.
> >>>> First, the original version: <datasets> <Insitu_Surface_Mongolia_DGS
> >>>> name="CEOP Surface Mongolia DGS"
> >>>> url="Insitu/CAMP_Mongolia_20021001_20030331sfc.data"
> >>>> doc=""> (note: other stuff deleted) <variables> <Station_Pressure
> >>>> name="Station Pressure" units="hPa (mb)"> <link
> >>>> match="/lasdata/grids/DGS_XYZT_grid"/> </Station_Pressure> I modified
> >>>> this file by replacing one line in the variables section as f
> >>>
> >>
> >> ollo
> >>>
> >>>>
> >>>> ws: <variables> &InsituAirTemperature; <link
> >>>> match="/lasdata/grids/DGS_XYZT_grid"/> </Station_Pressure> The error
> >>>> message that I got from the make was: asynchronous entity at line 2,
> >>>> column 0, byte 63: <Station_Pressure name="Station Pressure" units="
> hPa
> >>>> (mb)"> ^ error in processing external entity reference at line 32, column
> >>>> 3, byte
> >>>
> >>
> >> 901:
> >>>
> >>>>
> >>>> <variables> &InsituAirTemperature; ==^ <link
> >>>> match="/lasdata/grids/DGS_XYZT_grid"/> </Station_Pressure> error in
> >>>> processing external entity reference at line 53, column 0, byte
> >>>
> >>
> >> 1649:
> >>>
> >>>>
> >>>> <!-- Datasets provided by this server --> ^
> >>>> &CEOP_Insitu_Surface_Mongolia_DRS; at
> >>>> /usr/lib/perl5/site_perl/5.6.0/i386-linux/XML/Parser.pm line 185 make:
> ***
> >>>> [../ui/config.js] Error 255 What does "asynchronous entity" mean in this
> >>>> case? After this I tried one more thing. I added
> >>>> &InsituAirTemperature; t
> >>>
> >>
> >> o la
> >>>
> >>>>
> >>>> s.xml as follows: <!-- Datasets provided by this server -->
> >>>> &CEOP_Insitu_Surface_Mongolia_DGS; &InsituAirTemperature; </lasdata> Bu
> t I
> >>>> got exactly the same error message. Does anyone see anything wrong?
> >>>> Thanks, Ben At 15:13 2004/10/06 -0700, you wrote:
> >>>>>
> >>>>> Hi Ben, I have no example for you at the moment, but I have an
> >>>>> explanation which I think will help. XML ENTITIES are declared in the
> >>>>> DOCTYPE definition which must be declared before the first element in
> the
> >>>>> XML document. Therefore all ENTITIES must be declared in your root
> >>>>> document which by default is las.xml (the first xml element in the
> >>>>> las.xml file is <lasd
> >>>>
> >>>
> >>
> >> ata>)
> >>>
> >>>>
> >>>>>
> >>>>> Once it is declared there, then you can use the reference anywhere wit
> hin
> >>>>> the document i.e. these two Entities are declared in the las.xml DOCTYPE
> >>>>> definition ----------------------------- <?xml version='1.0' ?> <!DOCT
> YPE
> >>>>> spec SYSTEM "spec.dtd" [ <!-- Declaration of dataset files to be inclu
> ded
> >>>>> --> <!ENTITY ceop_surf_mong_dgs SYSTEM
> >>>>> "CEOP_Insitu_Surface_Mongolia_DGS.x
> >>>>
> >>>
> >>
> >> ml">
> >>>
> >>>>
> >>>>>
> >>>>> <!-- Other Entities --> <!ENTITY VarNameStationPressure SYSTEM
> >>>>> "Var_Name_Station_Pressure.xml"> ]> <lasdata> [...]
> >>>>> ------------------------------ now you can use "&ceop_surf_mong_dgs;" as
> >>>>> a reference in the las.xml document and you can use
> >>>>> "&VarNameStationPressure;" in the las.xml document or in
> >>>>> CEOP_Insitu_Surface_Mongolia_DGS.xml. Hope this helps. Joe
> >>>>> ------------------------------------- Ben Burford wrote:
> >>>>>>
> >>>>>> Hello All, I'm a beginner at XML and I'm building LAS menus. I have a
> >>>>>> category
> >>>>>
> >>>>
> >>>
> >>
> >> file
> >>>
> >>>>
> >>>> th
> >>>>>
> >>>>>>
> >>>>>> at (partially) looks like: (file is Insitu_Datasets.xml) <category
> >>>>>> name="Insitu"> <category name="Surface"> <category name="CAMP_Mongoli
> a">
> >>>>>> <category name="BTS"> <filter action="apply-dataset"
> >>>>>> equals="CEOP Surface Mongolia
> >>>>>
> >>>>
> >>>
> >>
> >> BTS"/>
> >>>
> >>>>
> >>>>>
> >>>>>>
> >>>>>> </category> (this leads to the file
> >>>>>> CEOP_Insitu_Surface_Mongolia_DGS.xml which co
> >>>>>
> >>>>
> >>>
> >>
> >> ntai
> >>>
> >>>>
> >>>> ns)
> >>>>>
> >>>>>>
> >>>>>> <datasets> <Insitu_Surface_Mongolia_DGS name="CEOP Surface Mongolia D
> GS"
> >>>>>> url="Insitu/CAMP_Mongolia_20021001_20030331sfc.data"
> >>>>>> doc=""> <properties> (properties stuff not important)
> >>>>>> </properties> <variables> <Station_Pressure name="Station Pressure"
> >>>>>> units="hPa (mb)"> <link match="/lasdata/grids/DGS_XYZT_grid"/>
> >>>>>> </Station_Pressure> (etc. for more variables, then grids then axes). In
> >>>>>> this line: <Station_Pressure name="Station Pressure" units="hPa (mb
> )">
> >>>>>> Station Pressure will appear as a menu entry. This list of variable
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> s wi
> >>>
> >>>>
> >>>> ll
> >>>>>
> >>>>>>
> >>>>>> appear in about 100 different menu pages (and therefore in about 100
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> diff
> >>>
> >>>>
> >>>> ere
> >>>>>
> >>>>>>
> >>>>>> nt xml files, one for each location) for several locations and statio
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> ns w
> >>>
> >>>>
> >>>> ith
> >>>>>
> >>>>>>
> >>>>>> in locations. I want to make this line an xml file/xml include so th
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> at,
> >>>
> >>>>
> >>>> if
> >>>>>
> >>>>>>
> >>>>>> I want to change the text of the menu item, I only change it in the o
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> ne x
> >>>
> >>>>
> >>>> ml
> >>>>>
> >>>>>>
> >>>>>> file, and not 100 xml files. In other words, I want to create the xm
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> l fi
> >>>
> >>>>
> >>>> le
> >>>>>
> >>>>>>
> >>>>>> Var_Name_Station_Pressure.xml which would contain one line:
> >>>>>> <Station_Pressure name="Station Pressure" units="hPa (mb)"> and then in
> >>>>>> CEOP_Insitu_Surface_Mongolia_DGS.xml put &VarNameStationP
> >>>>>
> >>>>
> >>>
> >>
> >> ress
> >>>
> >>>>
> >>>> ure
> >>>>>
> >>>>>>
> >>>>>> ; as in: <variables> &VarNameStationPressure; <link
> >>>>>> match="/lasdata/grids/DGS_XYZT_grid"/> </Station_Pressure> so the 1
> >>>>>> line would be substituted. I created the xml file Var_Name_
> >>>>>
> >>>>
> >>>
> >>
> >> Stat
> >>>
> >>>>
> >>>> ion
> >>>>>
> >>>>>>
> >>>>>> _Pressure.xml and changed my original xml file by changing the one l
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> ine
> >>>
> >>>>
> >>>> to
> >>>>>
> >>>>>>
> >>>>>> &VarNameStationPressure; as I show just above. I also tried putti
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> ng t
> >>>
> >>>>
> >>>> he
> >>>>>
> >>>>>>
> >>>>>> following at the beginning of the CEOP_Insitu_Surface_Mongolia_DGS.xm
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> l fi
> >>>
> >>>>
> >>>> le:
> >>>>>
> >>>>>>
> >>>>>> <?xml version='1.0' ?> <!DOCTYPE spec SYSTEM "spec.dtd" [ <!ENTITY
> >>>>>> VarNameStationPressure SYSTEM "Var_Name_Station_Pressure.xml"> ]> So,
> is
> >>>>>> it possible to put this one line ( <Station_Pressure name="S
>
> >>>>>
> >>>>
> >>>
> >>
> >> tati
> >>>
> >>>>
> >>>> on
> >>>>>
> >>>>>>
> >>>>>> Pressure" units="hPa (mb)"> ) in a separate xml file and then put it
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >> into
> >>>
> >>>>
> >>>> CE
> >>>>>
> >>>>>>
> >>>>>> OP_Insitu_Surface_Mongolia_DGS.xml as an xml include? If anyone has an
> >>>>>> existing xml file(s) as an example that you can send
> >>>>>
> >>>>
> >>>
> >>
> >> me
> >>>
> >>>>
> >>>> as
> >>>>>
> >>>>>>
> >>>>>> attached files, that would be the ideal and easy way to explain. Thanks
> >>>>>> very much, Ben
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
>
> ------------------------------------------------------------------------
> Name: las.xml
> las.xml Type: unspecified type (application/octet-stream)
> Encoding: base64
> Download Status: Not downloaded with message
>
> Name: Insitu_Datasets.xml
> Insitu_Datasets.xml Type: unspecified type (application/octet-stream)
> Encoding: base64
> Download Status: Not downloaded with message
>
> Name: CEOP_Insitu_Surface_Mongolia_DGS.xml
> CEOP_Insitu_Surface_Mongolia_DGS.xml Type: unspecified type (application/octet-stream)
> Encoding: base64
> Download Status: Not downloaded with message
begin:vcard
n:Epitalon;Jean-Marie
tel;fax:(+33) 05 61 19 30 00
tel;work:(+33) 05 61 19 31 32
x-mozilla-html:FALSE
org:C.E.R.F.A.C.S;Global change
version:2.1
email;internet:epitalon@cerfacs.fr
title:Computer engineer
adr;quoted-printable:;;42, Av G. Coriolis=0D=0A;TOULOUSE Cedex;;F-31057;France
x-mozilla-cpt:;0
fn:Jean-Marie Epitalon
end:vcard
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement