Mailing-List: contact commits-help@sis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: sis-dev@sis.apache.org
Date: Sun, 15 Oct 2017 12:20:02 +0000 (UTC)
From: "Martin Desruisseaux (JIRA)" <jira@apache.org>
To: commits@sis.apache.org
Message-ID: <JIRA.12705834.1396316692000.765.1508070002314@Atlassian.JIRA>
In-Reply-To: <JIRA.12705834.1396316692000@Atlassian.JIRA>
References: <JIRA.12705834.1396316692000@Atlassian.JIRA> <JIRA.12705834.1396316692826@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (SIS-171) Upgrade NetCDF to ISO-19115 mapping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 15 Oct 2017 12:20:12 -0000


     [ https://issues.apache.org/jira/browse/SIS-171?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Desruisseaux reassigned SIS-171:
---------------------------------------

    Assignee: Martin Desruisseaux

> Upgrade NetCDF to ISO-19115 mapping
> -----------------------------------
>
>                 Key: SIS-171
>                 URL: https://issues.apache.org/jira/browse/SIS-171
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Metadata, Storage
>    Affects Versions: 0.3, 0.4, 0.5, 0.6, 0.7
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Minor
>              Labels: NetCDF
>             Fix For: 0.8
>
>
> The mapping from NetCDF attributes to the ISO-19115 metadata is defined a=
t this page:
> * [NetCDF Attribute Convention for Dataset Discovery|http://wiki.esipfed.=
org/index.php/Attribute_Convention_for_Data_Discovery]
> * [NetCDF, HDF, and ISO Metadata|http://wiki.esipfed.org/index.php/NetCDF=
,_HDF,_and_ISO_Metadata]
> * [NcISO|https://geo-ide.noaa.gov/wiki/index.php?title=3DNcISO] (is XSLT =
files for the mapping from NetCDF metadata to ISO 19115-2)
> The mapping implemented since SIS 0.3 is the version 1.0 of above convent=
ion. Available versions as of May 2017 is 1.3. We will need to upgrade the =
mapping implemented by SIS to the latest version.
> h2. {color:green}UPDATE - June 1917{color}
> Rob Wallace did a review and [posted his result on the mailing list|https=
://lists.apache.org/thread.html/76c0ccf2e7e678a5525fc6ef633e06345c67286d077=
ab86e3c7f73f4@%3Cdev.sis.apache.org%3E]. Below is a copy of his result:
> h3. Report on work to check consistency of attributeNames between ISO 191=
15, ACDD 1-3 and  Metadata paths in Javadoc June 2017
> Resources used:
> * [ACDD 1-3|http://wiki.esipfed.org/index.php/Attribute_Convention_for_Da=
ta_Discovery] last modified version as of 24th January 2017
> * SIS source > Retrieved on 1st June 2017: {{storage/sis-netcdf/src/main/=
java/org/apache/sis/storage/netcdf/AttributeNames.java}}
> * [AttributeNames Javadoc|http://sis.apache.org/apidocs/org/apache/sis/st=
orage/netcdf/AttributeNames.html] > Retrieved 26th May 2017
> * [ISO 19115 xsl file|https://github.com/Unidata/threddsIso/blob/master/s=
rc/main/resources/xsl/nciso/UnidataDD2MI.xsl] > Retrieved on 6th June 2017
> In order to make the scanning of the XSL file easier, I (Rob): >
> * Read the XSL file with csVed v2.5.1 and filtered out xsl lines
> * Saved filtered version as CSV
> * Read CSV file with Notepad++ v7.4.1. This facilitated the metadata elem=
ent searches.
> ||ACDD 1-3 Attribute Names||In Javadoc Heading List?||In Javadoc Field De=
tail?||Metadata Path in ISO 19115 XSL file||Field and ISO 19115 path inAttr=
ibuteNames Class Source?
> |{{title}}|(/)|(/)|{{Metadata/citation/title}}|(/)
> |{{summary}}|(/)|(/)|{{Metadata/identificationInfo/abstract}}|(/)
> |{{keywords}}|(/)|(/)|{{Metadata/identificationInfo/descriptiveKeywords/k=
eyword}} with {{KeywordType.THEME}}|(/)
> |{{Conventions}}|(x)|(x)|{color:red}Needs to be implemented{color}|(x)
> |{{id}}|(/)|As {{IDENTIFIER}}|{{Metadata/fileIdentifier\\Metadata/identif=
icationInfo/citation/identifier/code}}|(/)
> |{{naming_authority}}|(/)|(/)|{{Metadata/identificationInfo/citation/iden=
tifier/authority/title}}|(x) title node missing in source
> |{{history}}|(/)|(/)|{{Metadata/dataQualityInfo/lineage/statement}}|(/)
> |{{source}}|(x)|(x)|Cannot find =E2=80=9Csource=E2=80=9D in file UnidataD=
D2MI.xsl|(x) No path for attribute in documents
> |{{processing_level}}|(/)|(/)|{{Metadata/contentInfo/processingLevelCode}=
}|(/)
> |{{comment}}|(/)|(/)|{{Metadata/identificationInfo/supplementalInformatio=
n}}|(x) No such path in ISO 19115
> |{{acknowledgement}}|(/)|(/)|{{Metadata/identificationInfo/credit}}|(/)
> |{{license}}|(/)|(/)|{{Metadata/identificationInfo/resourceConstraints/us=
eLimitation}}|(/)
> |{{standard_name_vocabulary}}|(/)|(/)|{{Metadata/identificationInfo/descr=
iptiveKeywords/thesaurusName/title}}|(/)
> |{{date_created}}|(/)|(/)|{{Metadata/identificationInfo/citation/date/dat=
e}} with {{DateType.CREATION}}|(/)
> |{{creator_name}}|(/)|(/)|{{Metadata/identificationInfo/citation}} with {=
{Role.ORIGINATOR}}|(/)
> |{{creator_email}}|(/)|(/)|{{Metadata/identificationInfo/citation}} with =
{{Role.ORIGINATOR}}|(/)
> |{{creator_url}}|(/)|(/)|{{Metadata/identificationInfo/citation}} with {{=
Role.ORIGINATOR}}|(/)
> |{{institution}}|(/)|(/)|{{Metadata/identificationInfo/citation}} with {{=
Role.ORIGINATOR}}|(/)
> |{{project}}|(/)|(/)|{{Metadata/identificationInfo/descriptiveKeywords}} =
with the =E2=80=9Cproject=E2=80=9D {{KeywordType}}|(/)
> |{{publisher_name}}|(/)|(/)|{{Metadata/distributionInfo/distributor/distr=
ibutorContact}} with {{Role.PUBLISHER}}|(x) AttributeNames class uses the b=
ranch name of =E2=80=9Cdistributors=E2=80=9D. It s/be =E2=80=9Cdistributor=
=E2=80=9D
> |{{publisher_name}}|(/)|(/)|{{Metadata/identificationInfo/descriptiveKeyw=
ords/keyword}} with the "dataCenter" {{KeywordType}}|(/)
> |{{publisher_email}}|(/)|(/)|As above|(x) and (/)
> |{{publisher_url}}|(/)|(/)|As above|(x) and (/)
> |{{geospatial_bounds}}|(x)|(x)|Not in ISO 19115 document|(x)
> |{{geospatial_bounds_crs}}|(x)|(x)|Not in ISO 19115 document|(x)
> |{{geospatial_bounds_vertical_crs}}|(x)|(x)|Not in ISO 19115 document|(x)
> |{{geospatial_lat_min}} and {{geospatial_lat_max}}|(/)|(/)|{{Metadata/ide=
ntificationInfo/extent/geographicElement/southBoundLatitude}} or {{northBou=
ndLatitude}}, {{Metadata/spatialRepresentationInfo/axisDimensionProperties/=
resolution}}\\The {{spatialRepresentationInfo}} element does not contain th=
e final two elements. They exist independently in Metadata XSL|(/) and (x) =
The 2nd and 3rd elements are not contained within the 1st
> |{{geospatial_lon_min}} and {{geospatial_lon_max}}|(/)|(/)|{{Metadata/ide=
ntificationInfo/extent/geographicElement/westBoundLongitude}} or {{eastBoun=
dLongitude}}, {{Metadata/spatialRepresentationInfo/axisDimensionProperties/=
resolution}}\\The {{spatialRepresentationInfo}} element does not contain th=
e final two elements. They exist independently in Metadata XSL|(/) and (x) =
The 2nd and 3rd elements are not contained within the 1st
> |{{geospatial_vertical_min}} and {{geospatial_vertical_max}}|(/)|(/)|{{Me=
tadata/identificationInfo/extent/verticalElement/minimumValue}} or {{maximu=
mValue}}, {{Metadata/spatialRepresentationInfo/axisDimensionProperties/reso=
lution}} The spatialRepresentationInfo element does not contain the final t=
wo elements. They exist independently in Metadata XSL|(/) and (x) The 2nd a=
nd 3rd elements are not contained within the 1st
> |{{geospatial_vertical_positive}}|(/)|(/)|(x) Seems to be missing in ISO =
19115 in XLS file|(/)
> |{{time_coverage_start}}|(/)|(/)|{{Metadata/identificationInfo/extent/tem=
poralElement/extent}}|(/)
> |{{time_coverage_end}}|(/)|(/)|{{Metadata/identificationInfo/extent/tempo=
ralElement/extent}}|(/)
> |{{time_coverage_duration}}|(/)| | |Unsure of the implementation of this =
in our source
> |{{time_coverage_resolution}}|(/)|(/)|{{Metadata/spatialRepresentation/ax=
isDimensionProperties/resolution}}|(/)
> |{{creator_type}}|(x)| | |Can be covered by =E2=80=9Ccreator=E2=80=9D
> |{{creator_institution}}|(x)| | |Can be covered by =E2=80=9Ccreator=E2=80=
=9D
> |{{publisher_type}}|(x)| | |Can be covered by =E2=80=9Cpublisher=E2=80=9D
> |{{publisher_institution}}|(x)| | |Can be covered by =E2=80=9Cpublisher=
=E2=80=9D
> |{{program}}|(x)|(x)|To be implemented in XSL file?|(x)
> |{{contributor_name}}|(/)|As {{CONTRIBUTOR}}|{{Metadata/identificationInf=
o/citation}} This path is stated in Javadoc, but I cannot see where the dat=
a will be defined in the XSL file|?
> |{{contributor_role}}|(/)|As {{CONTRIBUTOR}}|{{Metadata/identificationInf=
o/citation}} This path is stated in Javadoc, but I cannot see where the dat=
a will be defined in the XSL file|?
> |{{geospatial_lat_units}}|(/)|(/)|Unsure about how these data items will =
be read in|?
> |{{geospatial_lat_resolution}}|(/)|(/)|Unsure about how these data items =
will be read in|?
> |{{geospatial_lon_units}}|(/)|(/)|Unsure about how these data items will =
be read in|?
> |{{geospatial_lon_resolution}}|(/)|(/)|Unsure about how these data items =
will be read in|?
> |{{geospatial_vertical_units}}|(/)|(/)|Unsure about how these data items =
will be read in|?
> |{{geospatial_vertical_resolution}}|(/)|(/)|As above|?
> |{{date_modified}}|(/)|(/)|{{Metadata/identificationInfo/citation/date/da=
te}} with {{DateType.REVISION}}|(/)
> |{{date_issued}}|(/)|(/)|{{Metadata/identificationInfo/citation/date/date=
}} with {{DateType.PUBLICATION}}|(/)
> |{{date_metadata_modified}}|(x)| |Can=E2=80=99t find|?
> |{{product_version}}|(x)| |Can=E2=80=99t find|?
> |{{keywords_vocabulary}}|(/)|As {{VOCABULARY}}|{{Metadata/identificationI=
nfo/descriptiveKeywords/thesaurusName/title}}|(/)
> |{{platform}}|(x)|(x)|Can=E2=80=99t find|(x)
> |{{platform_vocabulary}}|(x)|(x)|Can=E2=80=99t find|(x)
> |{{instrument}}|(x)|(x)|Can=E2=80=99t find|(x)
> |{{instrument_vocabularay}}|(x)|(x)|Can=E2=80=99t find|(x)
> |{{cdm_data_type}}|(/)|As {{DATA_TYPE}}|{{Metadata/identificationInfo/spa=
tialRepresentationType}} in Javadoc|(x) No  spatialRepresentationType eleme=
nt in XSL file
> |{{metadata_link}}|(x)|(x)|Could be there under a different name|(x)
> |{{references}}|(/)|(/)|{{Metadata/identificationInfo/citation/otherCitat=
ionDetails}}|(/)
> |{{long_name}}|(x)|(x)|No yet in ISO 19115?|(x)
> |{{standard_name}}|(/)|(/)|{{Metadata/identificationInfo/descriptiveKeywo=
rds/keyword}} with {{KeywordType.THEME}}|(/)
> |{{units}}|(x)|(x)|Could be there in XSL file|(x)
> |{{coverage_content_type}}|(x)|(x)|Does appear in XSL file as =E2=80=9Cco=
ntentType=E2=80=9D|(x)
> |{{acces_constraint}}|(/)|As {{ACCESS_CONSTRAINT}}|{{Metadata/identificat=
ionInfo/resourceContraints/accessConstraints}} Not found in XSL file|(/)
> |{{contributor_email}}|(/)|As {{CONTRIBUTOR}}|Not specifically in XSL fil=
e|?
> |{{contributor_url}}|(/)|As {{CONTRIBUTOR}}|Not specifically in XSL file|=
?
> |{{flag_masks}}|(/)|(/)|{{Metadata/rangeElementDescription/rangeElement}}=
 Question: "rangeElement" referred to by two attributes?|(/) But includes "=
/contentInfo" in path
> |{{flag_meanings}}|(/)|(/)|{{Metadata/rangeElementDescription/definition}=
}|(/) As above
> |{{flag_names}}|(/)|(/)|{{Metadata/rangeElementDescription/name}}|(/) As =
above
> |{{flag_values}}|(/)|(/)|{{Metadata/rangeElementDescription/rangeElement}=
} Question: "rangeElement" referred to by two attributes?|(/) As above
> |{{full_name}}|(/)|(x)|Not sure of where this is implemented|(x)
> |{{geographic_identifier}}|(/)|(/)|{{Metadata/identificationInfo/extent/g=
eographicElement/geographicIdentifier}} Element "geographicIdentifier" Not =
found|(/)
> |{{metadata_creation}}|(/)|(/)|{{Metadata/dateStamp}}|(/)
> |{{name}}|(/)|(x)|Unsure of identity for this name|(x)
> |{{purpose}}|(/)|(/)|{{Metadata/identificationInfo/purpose}} Not found|(/=
)
> |{{time_coverage_units}}|(/)|(x)|Is mentioned at top of file as: //nc:att=
ribute\[\@name=3D'time_coverage_units']/\@value)"/>|Maybe covered somewhere
> |{{topic_category}}|(/)|(/)|{{Metadata/identificationInfo/topicCategory}}=
|(/)


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)