Additional NLD VHF points

[marcelrv]

Hallo @htool

I maintain a github page where I publish OpenCPN waypoints like VHF points by daily parsing the RWS data.

https://github.com/marcelrv/OpenCPN-Waypoints/tree/main
https://github.com/marcelrv/OpenCPN-Waypoints/blob/main/NL-MarifoonPunten-VHFinName.gpx

Doing few random checks, I see many points in the data set that are not in the NLD.json file.

You think it would make sense to extend the NLD.json with the published VHF points in the RWS data?

[htool]

Hey Marcel,

It depends on how, but potentially yes. The idea of vhfinfo is to give the user/ststem the area which the vhf frequency covers.

I did notice that for Denmark the official map uses circles (which technically makes sense).

And we'd want to avoid duplicates of course, so maybe you could check to see if a RWS point falls within an existing area?

[marcelrv]

Avoidance of the duplicates will be the key challenge. But I think that should be doable...
e.g. we can check the overlap in geozone, show the overlapping entries and than some manual check if they match.

Is the id you used created yourself or coming from some other source?

Anyway need to dig bit into the naming of the points
e.g in your file

      "type": "Feature",
      "properties": {
        "id": "0753a155-043d-4f3e-982e-05dcf69d4d17",
        "name": "Wemeldinge",
        "callname": "Post Wemeldinge",
        "type": "vts",
        "channel": "68",

is in RWS vtssector called "Sector Wemelding"

    "Id": 16499894,
    "GeoType": "vtssector",
    "GeoGeneration": 3709,
    "Name": "Sector Wemeldinge",
    "Geometry": "POLYGON ((3.693585502191057 51.616585270454344, 3.693792224 51.61632562, 3.690877404 51.61598988, 3.686262028 51.61617228, 3.685845311 51.61588142, 3.685476692 51.61514769, 3.684300762 51.61480809, 3.68246155 51.60173446, 3.682416669 51.60128427, 3.683281389 51.6008546, 3.68352085 51.60038753, 3.683572013 51.59945324, 

and has several 'Meldpunt Post Wemeldinge' in the RWS radiocallinpoint file

  {
    "Id": 28102356,
    "GeoType": "radiocallinpoint",
    "GeoGeneration": 1708,
    "Name": "Meldpunt Post Wemeldinge Tholen",
    "Geometry": "POINT (4.165341 51.512537)",
    "VinCode": "65115637",
    "RouteId": 30985571,
    "RouteKmBegin": 0.5,
    "RouteKmEnd": 0.5421969119534308,
    "FairwayId": 30985718,
    "FairwaySectionId": 39409,
    "IsrsId": 28102487,
    "ParentId": 16499894,
    "ParentGeoType": "vtssector",
    "RadioTraffic": "OUTBOUND",
    "VhfChannels": [
      "68"
    ],
    "RadioOrientation": 302.6,
    "RadioStatus": "PUBLIC",
    "Condition": "CONSTRUCTED"
  },

[marcelrv]

Did small test... showing both RWS and existing in the same map. The RWS ones in purple.
There are few extra ones in the rws set, like Moerdijk

and many where the lines are drawn slightly different (RWS seems to follow the water contours bit more closely, but excludes droogvalllende areas it seems)

[marcelrv]

Was relative easy to find the matching sectors and only add new ones.
Created #21
Note: skipped sector moerdijk as I did not find other references to it

Also I did not update the contours of the existing ones to match the RWS details.
I can easily do that, but wanted to confirm first if that is desired.

[htool]

Sorry for the late response. I improved the workflow on the site so that it uses an sql db as the backend.
Updating contours is ok, but now with the DB backend, I have to think about what would be a good way to do this.
The contours are made a bit simple, so avoid overloading the browser. Maybe have some sort of filter that keeps the number of points low.

Happy to have an online chat on how to approach on getting the data in and keep it updated.