codefornl / inspire Goto Github PK

The request used so far does not retuen any features any more: https://geodata.nationaalgeoregister.nl/noordzeevaarwegmarkeringenrd/wfs?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&NAMESPACES=xmlns(noordzeevaarwegmarkeringenrd,http://noordzeevaarwegmarkeringenrd.geonovum.nl)&TYPENAMES=noordzeevaarwegmarkeringenrd:markdrijvendrd

@HerzovanderWal is there someone from PDOK in this repository I could assign that issue to?

@HerzovanderWal When do we actually hold the workshop

Data source added to TN-RO
WFS link: hhttps://geodata.nationaalgeoregister.nl/digitaaltopografischbestand/wfs?SERVICE=WFS&VERSION=2.0.0&REQUEST=Getcapabilities

The following INSPIRE feature type is derived from this WFS:
RoadArea

The RoadJunction data is currently delivered as FGDB. It is supposed to be delivered via WFS in the future.

Deliver an alignment that transforms dmlinks and dmnodes to the INSPIRE Hydrography Network theme.

@milovanderlinden - How can I deliver a dutch and an english readme file in the root of this subject?

In the scope of this task, the hale connect configuration for TN-RO (theme and dataset) as well as the hale studio transformation project is updated to ensure fully automated updates every month. This task includes:

• Use WFS data sources in the transformation project where possible
• Publish source data sets that are not available through WFS as haleconnect WFS
• Update theme configuration to automatically update everything every month

Is there a difference in the coördinates that describe the AHN1 data and provided by the AHN1 services? The data seems to be delivered in EPSG 28992 hor. and EPSG 5730 vert.. What are the coördinate systems expected by INSPIRE?

In the Nationaal GeoRegister (www.nationaalgeoregister.nl) are the hosted services available.

• INSPIRE - NL Waterwegen (Waterways)
• INSPIRE - NL Wegen (Roads)
• INSPIRE - NL Hydrografie (Hydrogaphy)

We would like to use the these services but they already give errors in the catalog. Has someone the explanation?

This task's objective is to generate INSPIRE GML for the Elevation 4.0 Schema from the following source data sets:

• AHN3 (Hoogte)
• AHN2 (Hoogte)
• AHN1 25 meter (Hoogte)

We will not republish the existing elevation data sets, but instead create GML objects that references the original data sets at the existing granularity.

The results of this task are…:

• a detailed conceptual mapping documentation
• One or more hale studio transformation projects
• the transformed data sets, published as a download services

Create an initial TN-RO network alignment based on the mapping table and the source data.

The GML files generated during Phase I of this project represented complete data sets and included features form more than one namespace, e.g. from http://inspire.ec.europa.eu/schemas/tn/4.0 and from http://inspire.ec.europa.eu/schemas/tn-ro/4.0. This led to problems with downstream processing of data e.g. at PDOK. As a consequence, we add the option to write output by feature type to hale studio:

halestudio/hale#564

If necessary, we will make additional changes to the alignments to accomodate processing by downstream applications.

to be added according to offer

Data source added to TN-W
WFS link: https://geodata.nationaalgeoregister.nl/nwbvaarwegen/wfs?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetCapabilities

The following INSPIRE feature types are derived from this WFS:

• InlandWaterway

• MarineWaterway

• WaterwayLink

• MarkerPost

When users download the data (GML) from Hale-connect the filename is always Inspire.zip. Is it possible to name the file more unique like: [namespace+date].zip?

If you look at what the server returns for the GetCapabilities request you can see that it returns the URL like this, with a colon:

<ows:Operation name="DescribeFeatureType">
  <ows:DCP>
    <ows:HTTP>
      <ows:Get xlink:type="simple" xlink:href="http://geodata.nationaalgeoregister.nl:/kaderrichtlijnwater/wfs?language=dut&"/>
      <ows:Post xlink:type="simple" xlink:href="http://geodata.nationaalgeoregister.nl:/kaderrichtlijnwater/wfs?language=dut&"/>
    </ows:HTTP>
  </ows:DCP>
...
</ows:Operation>

The service returns invalid URLs. There should not be a colon after http://geodata.nationaalgeoregister.nl:.

In the scope of this task, the configuration for the HY-N dataset and theme are updated to ensure fully automated publishing and updating every month. This task includes:

• Use WFS data sources in the transformation project where possible
• Publish source data sets that are not available through WFS as haleconnect WFS
• Update theme configuration to automatically update everything every month

Daarom alle mapping tabellen converteren naar xls.

We would like to update our INSPIRE-services. Are the aligned data-services available? Where can we find them?

Data source added to TN-W
WFS link: https://geoservices.rijkswaterstaat.nl/apps/geoserver/verkeersscheidingsstelsel_nz/ows?service=WFS&request=getcapabilities

The following INSPIRE feature types are derived from this WFS:

• TrafficSeparationSchemeSeparator

• TrafficSeparationSchemeCrossing

kmmarkeringen has a vwk_id attribute that probably refers to objects in the vaarwegvakken table, with the key there probably also being vwk_id. However, when establishing a relationship, there are 456 MarkerPost objects derived from vaarwegvakken objects that do not have a valid reference. Is there any more info/confirmation that the relationship is like that?

@thorsten-reitz, @ - Can you and youre team change this readme.file.

Dear reader,“For the featuretype RegulatedFairwayAtSeaOrLargeInlandWater the 'Watervlakken' of DTB (Digitaal Topografisch Bestand) where dedicated.” But what dataset was used to get the featuretype?

In the scope of this task, the hale connect configuration (dataset and theme) and the hale studio transformation project for the TN-W are updated to ensure fully automated publishing and updating every month. This task includes:

• Use WFS data sources in the transformation project where possible
• Publish source data sets that are not available through WFS as haleconnect WFS
• Update theme configuration to automatically update everything every month

Based on the resources made available by RWS through WFS and other sources, we will develop a hale studio 3.4.0+ transformation project, to generate INSPIRE Human Health and Safety data from the following source data sets:

• Geluidbelasting rijkswegen in Nederland 2016 (nacht gemiddelde)
• Geluidbelasting rijkswegen in Nederland 2016 (24-uurs gemiddelde)
• Geluidbelasting rijkswegen in Nederland 2011 (nacht gemiddelde)
• Geluidbelasting rijkswegen in Nederland 2011 (24-uurs gemiddelde)
• Geluidbelasting rijkswegen in Nederland 2006 (nacht gemiddelde)
• Geluidbelasting rijkswegen in Nederland 2006 (24-uurs gemiddelde)

• Interpret all vaarwegvakken as InlandWaterways, as there is no attribute to distinguish them
• Interpret all kmmarkeringen as WaterwayNodes

Data source added to TN-W
WFS link: https://geodata.nationaalgeoregister.nl/noordzeevaarwegmarkeringenrd/wfs?&request=GetCapabilities&service=WFS

The following INSPIRE feature types are derived from this WFS:

• Beacon

• Buoy

The tree of INSPIRE definitions is complex for creating data-services. So the question is how we generalise the data and how do we we add the required definitions in the data and or metadata?

Het AHN dient gemapped te worden op het elevation thema https://inspire.ec.europa.eu/Themes/118/2892

What are the issues that come with stored query? Are the delivered services and there metadata compliant at this subject?

Omdat de rijkswaterstaat WFS services DEFAULT in RD (EPSG:28992) uitleveren moet transformatie van de geometrie plaatsvinden voor alle geometrie.

Het namespace register is nog niet gevuld. Dit maakt het registreren lastig en vereist dus afstemming met de betrokken autoriteiten.

The namespaces are declared. The source is becoming part of the INSPIRE-ID firtspart in Local-ID. The sources are for RWS:
hy-n -> NHI-
hy-p -> DTB-
hy-pc -> DTB-
hy-pmo -> DTB-
hy-poi -> DTB-
hy-pw => DTB-
tn-cte -> NWB-
tn-ro -> DTB- or NWB-W- (depends on mapping)
tn-rtn -> NWB-W-
tn-w -> NWB-V-
tn-wtn -> NWB-V-

Hale studio kan zaken niet laten zien (zoals de source data) wanneer een project is geinitieerd met meerdere source schema's (b.v. dmnodes en dmlinks in een project). De projecten moeten daarom worden uitgesplitst in projecten met een enkel source schema.

Volgens de specificatie in https://inspire.ec.europa.eu/file/1537/download?token=Uk33dqjm dienen geluidszoneringen ook te worden getransformeerd in het kader van het thema Human Health and Safety

https://inspire.ec.europa.eu/Themes/119/2892