HY: new application schema not written properly by ETL

[antjacques]

Dear helpdesk,

We are facing an issue related to new application schemas 2024.1 and 2024.2 (thus XSD v5.0), I'm not sure where to post this.

We are working with FME in order to write an INSPIRE-conform GML based on the new XSD:

The dataset here is a PhysicalWaters - Watercourse one. Therefore, I indicate these URLs into the XSD and the xsi:schemaLocations
http://inspire.ec.europa.eu/schemas/hy-p/5.0 http://inspire.ec.europa.eu/schemas/hy-p/5.0/HydroPhysicalWaters.xsd http://www.opengis.net/gml/3.2 http://schemas.opengis.net/gml/3.2.1/gml.xsd http://inspire.ec.europa.eu/schemas/base/4.0 http://inspire.ec.europa.eu/schemas/base/4.0/BaseTypes.xsd http://inspire.ec.europa.eu/schemas/gn/4.0 http://inspire.ec.europa.eu/schemas/gn/4.0/GeographicalNames.xsd http://www.isotc211.org/2005/gmd http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd

However, the output is not written properly and application schema 4.0 still appears (tag hy-p4). We suspect an issue with the XSD but couldn't find anything.
HY.watercourse_v5.zip

The issue might be related directly to FME but we'd rather first check if you can reproduce this issue and provide a solution.

Kind regards

[fabiovinci]

Dear @antjacques,

it seems there is still an import of the hy-p schema version 4 by some other linked schema, but when opening the schema with Hale Studio the default feature types are those related to version 5 (see screenshot below).
So, these are used in the exported gml file.

It could be a FME issue or something that should be specified in the transformation project.

I would suggest opening an issue in the dedicated FME repository/helpdesk.

In the meantime, we will check if it is possible to avoid the import of the old version of the hy-p schema.

[antjacques]

Thanks for your feedback @fabiovinci

The reason why we were reluctant to open a ticket at FME is because we successfully implemented new application schemas for other themes such as AU, TN, PS, NZ or HH. I forgot to mention it earlier, sorry.
The only bugs we have so far are linked to HY and US (ticket 1089 in the validator), so we were suspecting a problem in INSPIRE documents.

If you don't find anything else, we'll sure ask FME support.

Best regards

[JohannaOtt]

I am also confused that the current HY-N schema which is still version 4.0 is importing HY-Base in version 4.0 even though HY-Base 5.0 is existing.
Shouldn't the latest schemas always import the latest versions of other schemas?

Same for TN-A and TN-C where the latest version existing (4.0) is not importing the latest version existing for TN (should be 5.0, is only 4.0).

[JohannaOtt]

@fabiovinci Do you have any input on if we can expect the current 4.0 HY-N and TN-A and TN-C schema to be updated so that they import the latest 5.0 version of their respective "base" schemas HY-Base and TN?
Or will they remain as they are and use the old 4.0 base schemas?

[JohannaOtt]

@fabiovinci It would be important to clarify the handling of the schema imports between the various versions so that data providers know with which namespaces to work. It would be great if you could provide some input on that soon.
Thank you and all the best, Johanna

[fabiovinci]

Dear all,

I'm sorry for not getting back to you sooner.

We decided to fix these import errors and release them as a hotfix schema release.
It will be done in the next few weeks.

[antjacques]

FYI regarding the writer issue in FME: I opened a ticket and apparently Safe Software forgot to edit a configuration file to implement entirely the new application schemas
https://community.safe.com/transformers-9/inspire-gml-writer-importing-wrong-xsd-35229