Thanks for getting back to me so late. I changed the URL for the first catalogRef element, JPL054.xml, so at least that one can be looked at and tested. I will see about changing the rest of the urls tomorrow. I used the validator that was included in the version 2 to validate a type example of the original catalog and then built the others around the same example. It seemed to work well, the links worked and the html display was good so I felt it was working okay. But it seems that I should subject it to a more rigorous validation to flush out these bugs. Would it make any difference at this point, at least for the short term, to use version 3.2 instead or would the results be the same as what I am experiencing with v3.3? THanks again and I guess we will be in touch tomorrow.
ok, ive fixed a couple of bugs on my end:
1. should be able to show your catrefs as html now 2. fix bug not alowing validation messages
you will need the latest 3.3 war at:
there are various problems with your catalog, but it should no longer fail to show. you should check the validator, you can use motherlode:
and once you've installed the new war file, the same service will be on your machine
one problem i see you have is:
<metadata> <property name="Time units" value="seconds since 1970-1-1 0:0:0"/> </metadata>
<timeCoverage> <start>554774409</start> <end>554856152</end> </timeCoverage>
you should use:
<timeCoverage> <start>554774409 seconds since 1970-1-1 0:0:0</start> <end>554856152 seconds since 1970-1-1 0:0:0</end> </timeCoverage>
also its standard to start each xml with:
<?xml version="1.0" encoding="UTF-8"?>
though im not sure if it matters
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.