New post
0

[Bug] LiveSky.com | DeepSkyLog Rejects OAL Format/Invalid XML File

And gives the following:

Invalid XML file!

Any solution would be most appreciated.

10 comments

  • 0
    Avatar
    Keiron Smith

    Hi Nicos, 

    We are working on it.

    Thanks!

  • 0
    Avatar
    Nicos Kountouris

    Hi Keiron, 

    I exchanged emails with Wim at DeepSkyLog and provided him with the OAL file available from my device, so it's been looked into from DSL side as well.

    More info:

    There was mention by another member on the CN thread I started, that DSL does NOT support camera equipment and I removed my camera. Still no go.

    I exported my observations in CSV and tried to import them to DSL. No go again.

  • 0
    Avatar
    Wim De Meester

    Hi Nicos and Keiron,

    I am looking into the problem. The first thing I always check is if I can import the file in ObservationManager: See

    http://observation.sourceforge.net/en/

    This is not the case... There is indeed a problem with the camera equipment... The XML-file Nicos gets, contains

    <imagers>
    <imagers>
    <ccdCameraType id="id_WbrUlR5t1k">
    <model>
    <![CDATA[D5500]]>
    </model>
    <vendor>
    <![CDATA[Nikon]]>
    </vendor>
    <pixelsX>6045</pixelsX>
    <pixelXSize>3.89</pixelXSize>
    <pixelsY>4003</pixelsY>
    <pixelYSize>3.89</pixelYSize>
    </ccdCameraType>
    </imagers>

    However, it should be:

     <imagers>
    <imager id="id_WbrUlR5t1k" xsi:type="oal:ccdCameraType">
    <model>
    <![CDATA[D5500]]>
    </model>
    <vendor>
    <![CDATA[Nikon]]>
    </vendor>
    <pixelsX>6045</pixelsX>
    <pixelsY>4003</pixelsY>
    <pixelXSize>3.89</pixelXSize>
    <pixelYSize>3.89</pixelYSize>
    <binning>1</binning>
    </imager>
    </imagers>

    This seems like a small fix to make on the SkySafari export. However, as DeepskyLog does not use camera equipment, this should be skipped, so I think there is still another problem somewhere...

  • 0
    Avatar
    Wim De Meester

    I did some more investigations and I found that all the targets are of type oal:observationTargetType. DeepskyLog (and I guess all other <OAL> compatible applications) expect more detailed types, such as oal:deepSkyGX, oal:deepSkyPN, ... I also saw that some of the targets don't even have a name.

  • 0
    Avatar
    Nicos Kountouris

    Wim,

    Thanks for joining in as this will really help with the process :)

  • 0
    Avatar
    Wim De Meester

    The first line of the exported file should also be

    <?xml version="1.0" encoding="ISO-8859-1"?>

    in stead of 

    <?xml version="1.0"?>
  • 0
    Avatar
    Keiron Smith

    Thank you, Wim, for joining us here!  We can figure it out together, for sure!

  • 0
    Avatar
    Wim De Meester

    You're welcome! I'm sure we will be able to figure it out. I'm also in contact with Phyllis about this problem.

    For the targets, I think oal:observationTargetType should be ok. DeepskyLog is not yet able to import these files, but I will make sure they will soon! In the example file, there were some targets without a name, and that is certainly a problem.

  • 0
    Avatar
    Wim De Meester

    Hi all,

    some of the people who helped to define the OpenAstronomyLog format (Thomas Pfleger) found a solution to the problems. DeepskyLog will not yet be able to import the file, but I'm working on a solution for this. This is what he says:

     

    Hi,

    after some investigation I was able to spot the problems and finally could import a slightly modified file. So, what is it?

    1. The namespace of the document and the schema do not match. Yes, it's true that we moved from the Google group to github, but the spec does not require a namespace URL to be resovable. It just has to be unique.
    2. There is an encoding problem and a character that breaks my import, at least into Eye&Telescope.
    3. The <imager> element for the CCD camera is not valid.
    Fixes:
    1. In the observations document, the namespace declaration to be used in element <oal:observations>  is
      http://groups.google.com/group/openastronomylog not https://github.com/openastronomylog/openastronomylog
    2. I removed the character after "Observing with Agapios Elia and his Celestron C9.25" in line 110 and saved the file as UTF-8 without byte order marker (BOM)
    3. An <imager> element gives its concrete type, but the concrete type is not the element name.
      Note the order of the pixelsX, pixelsY, pixelsXSize und pixelsYSize. They do not group by X and Y.  
      The <binning> element is mandatory, albeit it has a default value of 1. So it must be present but may be empty.
  • 0
    Avatar
    Wim De Meester

    Is this problem already fixed or do you need more information or help to fix this?

     

Please sign in to leave a comment.