Replies: 8 comments
-
Dear @DLList, Thank you for your comment. We are going to begin with a research to provide you with the best solution as soon as possible. Please be patient, this might take some time. Best regards. |
Beta Was this translation helpful? Give feedback.
-
Dear @DLList, Please, could you use our contribution guidelines to help us more quickly locate what is causing this issue? We will like to have the file you are using, the problem you have and if is possible, a screenshot of the issue. Thanks in advice, this information will be useful for us. Best regards. |
Beta Was this translation helpful? Give feedback.
-
Dear @DLList, Please, we will appreciate if you can help us using the contribution guidelines. Otherwise, we could not help you. Best regards. |
Beta Was this translation helpful? Give feedback.
-
Dear @DLList, @josemasensio, the limitation seems due to the fact that:
Could you verify if the connectivityTolerance parameter can be used in case of the geometries are already in a meter-based CRS? |
Beta Was this translation helpful? Give feedback.
-
Dear @josemasensio, the problem for me now is more theoretical. Specifically: how to use/set the connectivityTolerance parameter in INSPIRE-XML-File? Best regards |
Beta Was this translation helpful? Give feedback.
-
Dear @josemasensio, In addition to the previous message, I send an example of test data where I would have liked to use the ConnectivityTolerance parameter. Best regards |
Beta Was this translation helpful? Give feedback.
-
Dear @DLList, there is no way to indicate the ConnectivityTolerance parameter inside the gml dataset. Please have a look at section 10.2 Ensuring Network Connectivity of the Data Specification (page 169), which indicates that:
In section 7.1.6 it is indicated how to document connectivity tolerance in the metadata. |
Beta Was this translation helpful? Give feedback.
-
Dear @fabiovin, thank you for the answer firstly. I will analyze now this topic. |
Beta Was this translation helpful? Give feedback.
-
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.
My approach for creating INSPIRE-Data
Transfer the source data to INSPIRE as it is. This means I get sometimes small geometric differences between RoadNodes and the corresponding RoadLinks in INSPIRE data. These discrepancies sometimes amount to only a few millimetres.
Testing the DataSet with the Validator
The Validator throws in situations of discrepancies the error "no free transport nodes".
Question
My question is: How can I solve this problem with free RoadNodes. Maybe should I use for the data the "ConnectivityTolerance"? If so, how to do it?
Best regards,
Dawid
Beta Was this translation helpful? Give feedback.
All reactions