Free Node of type "roadServiceArea"

[DLList]

Hello,

I have a problem with the ETF-Validator that I'd like to solve here.

I am currently busy developing a tool for transforming street data into INSPIRE Transport Network Structures. I have created several INSPIRE Features and tested them with the Validator. I have a problem with free RoadNodes of type "roadServiceArea".

My approach for creating INSPIRE-Data
Creating RoadNodes with the type "roadServiceArea". These objects are geometrically located in the middle of a RoadLink. This means not at the beginning and not at the end.

Testing the DataSet with the Validator
The Validator returns in case of such RoadNodes error message "No free transport nodes".

Question
My question is: Is the fact with the placement of RoadNodes in the middle of RoadLinks (not at their ends) INSPIRE compliant, or is this an error of the validator?

Best regards,
Dawid

[josemasensio]

Dear @DLList

We have been doing some checks with the metadata you provide us on issues #90 and #140 and we have seen that there are not RoadServiceAreas defined, for this reason, the validator interprets that there is a union with a roadServiceArea that does not exist.
As you can see on Transport Network TG there should be a Service Area defined close enough to RodeNode.

Are you using a different metadata file? Are the Services Areas defined somewhere else?
Regards

[josemasensio]

Dear @DLList,

Does the explanation provided was valid for you?

Best regards.

[DLList]

Dear @josemasensio,

I am using this data you checked. In this question i didn't ask for FeatureType: RoadServiceArea.
I asked for RoadNode with the formOfWay-value: 'roadServiceArea'.
There are two examples for such RoadNodes.

Best regards.

[josemasensio]

Dear @DLList,

Regarding your first question,

Is the fact with the placement of RoadNodes in the middle of RoadLinks (not at their ends) INSPIRE compliant, or is this an error of the validator

INSPIRE only allows RoadNodes in the middle of RoadLink when they are in a roadServiceArea. For this reason, we were mentioning that there was not a roadServiceArea define on your file.
Secondly, about your last question,

I asked for RoadNode with the formOfWay-value: 'roadServiceArea'.

There is not any reference on the TG DataSpecification 3.2 to the use of roadServiceArea as the value of formOfWayValue. Here is where the roadServiceArea value is supposed to be defined and which are the accepted values of formOfWayValue:

Please, let us know what is your opinion about this.

Best regards.

[DLList]

Dear @josemasensio,

As for your first statement,
"INSPIRE only allows RoadNodes in the middle of RoadLink when they are in a roadServiceArea."
Ok, thats new for me. Can I know where concretly it is defined this way?
For the second statement, I'm sorry, I mean't "formOfRoadNode", not "formOfWay".

Best regards.

[josemasensio]

Dear @DLList,

Thank you for your reply.

As you can see at the image below, there are multiple RoadNodes. If we focus on all of them, we can observe that nodes have a connection with other "Entity" i.e.: PortNode, WaterwayNode or another Road. So, on general aspects, we could say that all RoadNodes below are a connections with something.

Regarding Road Transport Network image posted on our previous comment, There are three different types of RoadNodes. Two of them, (roundabout and junction) are connecting different roads. Another example of RoadNode could be a Service Station (real object). The third RoadNode, is connecting the road with a RoadServiceArea which is a surface. 5.4 Application schema Road Transport Networks from Technical Guidance

Regarding your second question:

I asked for RoadNode with the formOfRoadNode: 'roadServiceArea'.

According to the TG a RoadNode is defined as
A point spatial object that is used to either represent connectivity between two road links or to represent a significant spatial object such as a services station or roundabout.

Therefore, the RoadNode defined, which is raising an error, is being identified as a connection point but is not connected to anything. In order to be compliant needs to be connected to a ServiceArea.
RoadNode have a property which is formOfRoadNode: 'roadServiceArea' which means that at this point is the union between the Road and the Service Area, but there is no RoadServiceArea.

In our opinion, the problem is that there is no roadServiceArea defined. Maybe you could try to define a roadServiceArea and run the test again? We will be waiting for your response.

Please, let us know how can we help you.

Best regards.

[DLList]

Dear @josemasensio,

thank you for answer. Ok, but which association allows to connect a RoadNode to a ServiceArea.

A RoadNode can only be connected with links:

• spokeStart
• spokeEnd

A ServiceArea also has not an association to RoadNode.

Best regards.

[josemasensio]

Dear @DLList.

You are right, there is no way to connect directly the RoadNode with the Service area, that is why we are going to use the property of formOfRoadNode attribute from RoadNode, which is a description of a RoadNode in the RoadTransportNetwork.

FormOfRoadNode attribute has some predefined values, which are the following ones:

• enclosed traffic area
• junction
• level crossing
• pseudo node
• road end
• road service area
• roundabout
• traffic square

As you can see, one of these values is roadServiceArea. This is used to define that there is a ServiceArea, which is what we mentioned on a previous comment:

The RoadNode defined, which is raising an error, is being identified as a connection point but is not connected to anything. In order to be compliant needs to be connected to a ServiceArea.
RoadNode have a property which is formOfRoadNode: 'roadServiceArea' which means that at this point is the union between the Road and the Service Area, but there is no RoadServiceArea.

What are referring here, is that you have a roadServiceArea attribute on your RoadNode defined in the middle a RoadLink but with no roadServiceArea defined. Maybe you could try to define a roadServiceArea and run the test again? Please let us know if that works.

Best regards.

[DLList]

Hello, all,

I would like to revisit the subject, because it is still not clear for me:

What are referring here, is that you have a roadServiceArea attribute on your RoadNode defined in the middle a RoadLink but with no roadServiceArea defined. Maybe you could try to define a roadServiceArea and run the test again? Please let us know if that works.

What should the fact that I create a RoadServiceArea bring about?

• where is it written, that it is allowed if you have RoadNode with the formOfRoadNode attribute value 'RoadServiceArea'?

How should the RoadServiceArea be connected to my RoadNode with the formOfRoadNode attribute value 'RoadServiceArea'?

• attributive? => there is no attribute that allows this
• geometrical? => I don't think so

The only connection I make is between my RoadNode and the RoadServiceType (networkRef).

So my question is still open:

• Is the fact that the ETF validator sends the error message "The node is not located at the start or end of any link feature in the data set" in this situation correct or not?
  If this is correct, it would mean that the RoadNode, even if it has the formOfRoadNode value "RoadServiceArea", should be connected to a RoadLink (spokeStart or spokeEnd). Is this true?

Best regards.