Character encoding problem for some ACADIS *.iso19139 files causes Rubric-Q validation to fail

XMLWordPrintable

    • Type: Feature
    • Resolution: Cannot Reproduce
    • Priority: Major
    • None
    • Affects Version/s: 2.0.48, 2.0.49
    • None
    • Hide
      <p>I just retried the url that Brian entered into the description today (9/18/2015) and the website came back with a full report on the iso file.</p>

      <p>&nbsp;</p>

      <p>So closing this ticket for now and un-reproducable.</p>
      Show
      <p>I just retried the url that Brian entered into the description today (9/18/2015) and the website came back with a full report on the iso file.</p> <p>&nbsp;</p> <p>So closing this ticket for now and un-reproducable.</p>


      The Rubric-Q validation tool (http://www.geoviqua.org/MetadataVisualization.htm) reports a parse error for the following ISO document:

      https://www.aoncadis.org/dataset/2010_niskin_bottle_data_chlorophyll_nutrients_picoplankton.iso19139

      The error says: XML Parsing Error: not well-formed
      Location: http://www.ogc.uab.cat/cgi-bin/geossback/GEOSSBack.cgi?accio=EstilXML&AfegirEstil=rubric&URL=https://www.aoncadis.org/dataset/2010_niskin_bottle_data_chlorophyll_nutrients_picoplankton.iso19139
      Line Number 79, Column 356

      The problem appears to be caused by a character in the project description field for this metadata, which includes the greek letter "mu", commonly used to denote "micro" units. It is also called the "micro sign".

      The cause could be caused by the HTTP header for this document, which reports that the character set for this document is ISO-8559-1. Nathan believes this is almost certainly not the actual character set encoding used for this document. It is not yet clear how we find out exactly what the actual character set encoding is for our ISO documents.


              Assignee:
              Unassigned
              Reporter:
              Brian Bonnlander
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: