v2022.2- 21/06/2022

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

• #765 Validation against the latest INSPIRE official schemas - #748
• #770 INSPIRE data sets and data set series metadata for IACS multilanguage- #749

🐛 Bugfixes

• #569 tn-gml typo correction - #750
• #618 #703 invalidLegendFormat message updated - #751
• #710 am-as-a.2 missingElement and missingAttribute property fixed - #752
• #714 su-vector-as.b.1 and su-vector-as.b.2 updated - #753
• #729 Conformance class description typo fixed - #754
• #742 5621, 9389 and 9390 EPSG codes added - #755
• #747 pf-gml typo fixed - #756
• #749 outputSchema and elementSetName default parameters added in UI
• #780 #718 #771 Not required service metadata checks removed- #757

🚀 Validator UI

• #24 New cookie consent on Validator UI - #25
• #23 Quick links in the "Get support" menu need to be changed
• #22 Wrong CC for some US application schemas - #21
• #19 URL Metadata validation for non-ISO default responses - #20
• #14 Staging/production parametrization - #18
• #13 Typo for AD data theme - #15
• #10 Missing CC name for BU3D
• #9 Outdated instructions to be removed
• #8 Date display issue bug - #12
• #7 Link to be changed - #11

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2022.2
#Launches a container with the image, exposing the UI in port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file, you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, the UI and correct rendering of Test Reports, the validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property.
It is also necessary to configure the Validator UI properties in order to properly point to the ETF. Thus, it is necessary to modify the configuration values in the /validator/js/config.js file inside the ui.zip (to point to the corresponding host domain).
Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2022.2.zip and follow the instructions in the README.md file inside the .zip file.

v2022.1 17/03/2022

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

• #727 INSPIRE data sets and data set series metadata for IACS - #720

🐛 Bugfixes

• #327 Add 'nor' language to c.5 - #713
• #567 common-req C.5 and datasets-and-series 1.6 codelists updated - #714
• #625 ge-ia.b.2 and ge-ia.b.3 missing element and wrong multiplicity conditions removed - #715
• #659 Removed multiplicity check for so:soilDerivedObjectObservation - #712
• #686 New certificate added
• #688 C.18 otherConstraints Anchor condition updated - #716
• #704 lc-as.a.1 updated - #717
• #706 common req C.5 ice language code added - #718
• #712 bu-3d-as.a.3 and bu-3d-as.a.4 checks each buildingpart of bu-base:parts - #719

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2022.1
#Launches a container with the image, exposing the UI in port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file, you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, the validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2022.1.zip and follow the instructions in the README.md file inside the .zip file.

v2022.0 19/01/2022

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

OGC API-Features:

• OGC API-Features

🐛 Bugfixes

• #565 etf.dependency.ids value updated - #702
• #612 Accepted date and dateTime - #693
• #626 BU.Building.default option style added - #694
• #633 Update emptyName message - #695
• #638 Check operatesOn/xlink:href instead of operatesOn/uuidref - #700
• #643 Created loop to avoid defining messages - #696
• #646 Update StatisticalTesselation to StatisticalTessellation - #697
• #649 Update mr-as.b.1: specification test - #698
• #669 Add 5013, 5014 and 5015 EPSG codes - #699

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2022.0
#Launches a container with the image, exposing the UI in port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file, you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, the validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2022.0.zip and follow the instructions in the README.md file inside the .zip file.

v2021.3.1 04/10/2021

🐛 Bugfixes

This is an exceptional release of the Validator, which includes the latest version of the TEAM Engine. A hotfix was needed on the TEAM engine test driver due to a change in the OGC response and the validator was not able to proccess the new response. As a consequence, all the ETS releated with the OGC validator were not able to run and process the result page

Several issues arose from this problem, see #565, #553, #548, #538,
This release builds on the latest release (v.2021.3).

• TEAM Engine reference update to treat the new OGC validator response format

• TestDriver for TEAM Engine updated on validator.war inside INSPIRE validator

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training materal

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf ghcr.io/inspire-mif/helpdesk-validator/inspire-validator:2021.3.1
#Launches a container with the image, exposing it port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file, you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, the validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2021.3.1.zip and follow the instructions in the README.md file inside the .zip file.

v2021.3 16/09/2021

The version published at this time contains only non-breaking changes.

🚀 New Features

ATS:

• ATS for Data Specification on Mineral Resources
• ATS for Data Specification on Energy Resources
• ATS for Data Specification on Oceanographic geographical features
• ATS for Data Specification on Atmospheric Conditions and Meteorological Geographical Features
• ATS for Data Specification on Statistical Units
• ATS for Data Specification on Soil

ETS:

• ETS for Data Specification on Mineral Resources
• ETS for Data Specification on Energy Resources
• ETS for Data Specification on Oceanographic geographical features
• ETS for Data Specification on Atmospheric Conditions and Meteorological Geographical Features
• ETS for Data Specification on Statistical Units
• ETS for Data Specification on Soil

🐛 Bugfixes

• #440 Fixed prefixes on lu-gml - #647
• #458 Polygon, PolyhedralSurface and TriangulatedSurface added to bu-as b.5 and lc-v-as a.1 - #633
• #473 Added certificates in validation process - #648
• #526 hb-as.a.4 paths fixed - #649
• #532 Parsed 'lang' to String to avoid type error - #650
• #555 ef-as a.1 conditions fixed for empty observations - #651
• #566 Fixed "An error has occurred" error on new UI.
• #571 Fixed SwaggerUI documentation.
• #572 Added missing ';' to media-type test & Update URL to point against atom URL - #653
• #576 Added missing semicolons to WFS - #652
• #582 Added missing '.Default' layers - #654
• #587 Updated wrong variable - #655
• #601 noDateTypeForSpecification message typo fixed - #657

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training materal

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf ghcr.io/inspire-mif/helpdesk-validator/inspire-validator:2021.3
#Launches a container with the image, exposing it port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file, you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, the validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2021.3.zip and follow the instructions in the README.md file inside the .zip file.

v2021.2 15/06/2021

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

ATS:

• ATS for Data Specification on Orthoimagery
• ATS for Data Specification on Agricultural and Aquaculture Facilities

ETS:

• ETS for Data Specification on Orthoimagery
• ETS for Data Specification on Agricultural and Aquaculture Facilities

UI:

• Integration of new INSPIRE validator UI

🐛 Bugfixes

• #265 Added tiff format support to ATOM tests - #619
• #432 Updated from QualityOfCriteriaCode to QualityOfCriteria - #622
• #453 Updated temp schema validation - #616
• #472 Updated noDateTypeForSpecification message - #623
• #530 Added specification option to Geology - #618
• #531 GMLAS C.1 *:uom exception added - #617
• #535 Added new certificates to the ETF Validator
• #543 Added new certificates to the ETF Validator
• Updated outdated "community" repository links - #624

Deployment instructions

Section containing deployment process using Docker image and troubleshooting section. You can also find these in the training materal

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2021.2
#Launches a container with the image, exposing it port 8080 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2021.2.zip and follow the instructions in the README.md file inside the .zip file.

v2021.1 18/03/2021

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

ATS:

• ATS for Data Specification on Bio-geographical Regions
• ATS for Data Specification on Elevation
• ATS for Data Specification on Geology
• ATS for Data Specification on Population Distribution
• ATS for Data Specification on Sea Regions

ETS:

• ETS for Data Specification on Bio-geographical Regions
• ETS for Data Specification on Elevation
• ETS for Data Specification on Geology
• ETS for Data Specification on Population Distribution
• ETS for Data Specification on Sea Regions

🐛 Bugfixes

• #419 Updated CharacterString validation dor MD 2.0 3.4 - #581
• #461 Updated TeamEngine dependency
• #471 Added SSL certificates to the validator deployment
• #474 Updated HTTPS access to the TEAM engine
• #479 Relaxed MD C.21 - C.22 - 1.10 - 5.3 - 5.4 - 5.5 - #597
• #480 Relaxed error C.14 to allow before and after - #583
• #482 Added SSL certificates to the validator deployment
• #488 Added certificates in validation process
• #512 Added BuildingPart Default layer and set 'default' to upper case - #588
• #518 Species distribution paths and wrongMultiplicity messages fixed - #582
• #529 Modified el-gml path - #587

Deployment instructions

Section containing deployment process using Docker image and troubleshooting section. You can also find these in the training materal

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2021.1
#Launches a container with the image, exposing it port 8080 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2021.1.zip and follow the instructions in the README.md file inside the .zip file.

v2021.0 18/01/2021

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

ATS:

• ATS for Data Specification on Area Management
• ATS for Data Specification on Land Use
• ATS for Data Specification on Species Distribution
• ATS for Data Specification on Natural Risk Zones
• ATS for Data Specification on Buildings
• ATS for Data Specification on Environmental Monitoring Facilities
• ATS for Data Specification on Human Health and Safety
• ATS for Data Specification on Habitats and Biotopes
• ATS for Data Specification on Land Cover
• ATS for Data Specification on Production and Industrial Facilities
• ATS for Data Specification on Utility and Government Services

ETS:

• ETS for Data Specification on Area Management
• ETS for Data Specification on Land Use
• ETS for Data Specification on Species Distribution
• ETS for Data Specification on Natural Risk Zones
• ETS for Data Specification on Buildings
• ETS for Data Specification on Environmental Monitoring Facilities
• ETS for Data Specification on Human Health and Safety
• ETS for Data Specification on Habitats and Biotopes
• ETS for Data Specification on Land Cover
• ETS for Data Specification on Production and Industrial Facilities
• ETS for Data Specification on Utility and Government Services

🐛 Bugfixes

• #324 Added a validation when parent Authority url is not defined - #549
• #338 Temporal filter errors in Conformance Class: Download Service - Direct WFS Team Engine
• #346 Improved information on docker deployment
• #389 Updated features in PLU - #512
• #397 Added manual check on nz-as - #529
• #422 WMS executed tests are not found in the list of tests executed by the validator
• #424 Added date validation for data consistency - #532

Deployment instructions

Section containing deployment process using Docker image and troubleshooting section. You can also find these in the training materal

As a prerrequisite to use the Docker packages from GitHub, you would need to create an access token as a way to authenticate on the registry. You can get more information here

• https://docs.github.com/en/packages/guides/configuring-docker-for-use-with-github-packages#authenticating-with-a-personal-access-token
• https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2021.0
#Launches a container with the image, exposing it port 8080 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2021.0.zip and follow the instructions in the README.md file inside the .zip file.

v2020.3.1 30/11/2020

🐛 Bugfixes
This is an exceptional release of the Validator, which includes the latest version of the TEAM Engine. A hotfix was needed on the TEAM engine test driver due to a change in the OGC endpoint the validator uses as an API (see #461). As a consequence, the ETS for Conformance Class "WFS Direct" needed to be updated to reference the change in the dependency to the TEAM engine test. This release builds on the latest release (v.2020.3).

• TEAM Engine reference update on Direct WFS ETS #461

• TestDriver for TEAM Engine updated on validator.war inside INSPIRE validator #461

Deployment instructions

Section containing deployment process using Docker image and troubleshooting section. You can also find these in the training materal

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf docker.pkg.github.com/inspire-eu-validation/community/inspire-validator:2020.3.1
#Launches a container with the image, exposing it port 8080 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2020.3.1.zip and follow the instructions in the README.md file inside the .zip file.

v2020.3 16/09/2020

This version only includes non-breaking changes, so that any INSPIRE resource passing the test in the previous release automatically passes the same test in this release. This release is the one used for the end-of-year Monitoring process.

🐛 Bugfixes

• #207 Tooltip updated for datasets services
• #214 Pre-defined WFS - check on optional element wfs:boundedBy - #503
• #295 Test "Request and check externalServiceMetadata" in Conformance Class: Download Service - Pre-defined WFS - #511
• #307 EPSG codes in Azores - #504
• #322 Increase Upload size limit to 200MB (Staging instance) and 50MB (Production instance)
• #343 Test C.18 - New corner case - #505
• #348 Priority Datasets Keyword: error for Citation Title - #506
• #350 Updated RegEx for ISO:8601 on MD 2.0 - #507
• #367 Possible invalid test in MD 2.0 CC 7: 'INSPIRE Harmonised Spatial Data Services metadata - #508
• #373 Fixed different system errors on MD 2.0 - #509
• #385 Updated error message for MD 2.0 - SDS 3.4 - #510

Deployment instructions

Section containing deployment process using Docker image and troubleshooting section. You can also find these in the trainig materal

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf docker.pkg.github.com/inspire-eu-validation/community/inspire-validator:2020.3
#Launches a container with the image, exposing it port 8080 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf

Modifying the Docker image

In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.

If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at WEB-INF/classes/etf-config.properties, and modify the etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.

Exposing the validator through a proxy

Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.

For the build process, you need to add the following arguments to the command

--build-arg http_proxy=[HTTP_PROXY_URL:PORT]  --build-arg https_proxy=[HTTPS_PROXY_URL:PORT]  --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>

For the run command, you need to add the environment variables to it

--env http_proxy=[HTTP_PROXY_URL:PORT]  --env https_proxy=[HTTPS_PROXY_URL:PORT]  --env no_proxy=127.0.0.1,localhost,*.<mydomain>

These can also be set up in the Dockerfile, using the keyword ENV

For more information please check out https://docs.docker.com/network/proxy

For further configuration, please download the file inspire-validator-2020.3.zip and follow the instructions in the README.md file inside the .zip file.