You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have a question regarding the updated INSPIRE schemas and the updated version of HALE Studio.
When we were updating data transformation models using the updated (v.5.0) INSPIRE schemas, we had noticed differences in how the GML file is exported by HALE Studio 3.5.0 and HALE Studio 5.1.
These differencies are also visible in reports of INSPIRE ETF validator.
If we import the schemas (v.5.0) to Hale Studio 3.5.0 and export GML file, when ETF validator does not show errors.
We attached INSPIRE ETF validator report (name: ValidationResults_HaleStudio_3_5_Road_sample.html) and gml file (name: HaleStudio_3_5_Road_sample.gml).
If we import schemas (v.5.0) to Hale Studio 5.1.0 and export GML file, when ETF validator shows errors which probably are related with some .xsd elements and their referencies to xml schemas (except error which are related with geometry. This error is because we are testing sample of data).
We attached INSPIRE ETF validator report (name: ValidationResults_HaleStudio_5_1_Road_sample.html) and gml file (name: HaleStudio_5_1_Road_sample.gml).
hale studio includes offline versions of the schemas, but there seems to be a discrepancy between what is included in hale studio and what is served on the INSPIRE website.
The schemas used in hale studio use the current version of the schemas from the GitHub repository at the time of release. There the schemas look correct, e.g. RoadTransportNetwork.xsd, so we will need to check why that is not properly reflected (and provide a new version with the update).
As workaround you can delete the file eu.esdihumboldt.util.resource.schemas.inspire_2024.2.21.bnd-8IYMsg.jar in the plugins folder of your hale studio installation.
Dear Wetransform team,
we have a question regarding the updated INSPIRE schemas and the updated version of HALE Studio.
When we were updating data transformation models using the updated (v.5.0) INSPIRE schemas, we had noticed differences in how the GML file is exported by HALE Studio 3.5.0 and HALE Studio 5.1.
For example,
When we import scheme https://inspire.ec.europa.eu/schemas/tn-ro/5.0/RoadTransportNetwork.xsd to Hale Studio 5.1, the properties of attribute „beginlifespanVersion“ is specified this way:
When we import the same scheme to Hale Studio 3.5, the properties of attribute „beginlifespanVersion“ is specified as expected:
The differencies (which are related with referencies to xml schemas) are noticeable when we are using the schemas listed below:
These differencies are also visible in reports of INSPIRE ETF validator.
If we import the schemas (v.5.0) to Hale Studio 3.5.0 and export GML file, when ETF validator does not show errors.
We attached INSPIRE ETF validator report (name: ValidationResults_HaleStudio_3_5_Road_sample.html) and gml file (name: HaleStudio_3_5_Road_sample.gml).
If we import schemas (v.5.0) to Hale Studio 5.1.0 and export GML file, when ETF validator shows errors which probably are related with some .xsd elements and their referencies to xml schemas (except error which are related with geometry. This error is because we are testing sample of data).
We attached INSPIRE ETF validator report (name: ValidationResults_HaleStudio_5_1_Road_sample.html) and gml file (name: HaleStudio_5_1_Road_sample.gml).
files.zip
Could you please have a look if these issues are related to the HALE Studio update, or it could be an another reason of this?
The text was updated successfully, but these errors were encountered: