Skip to content

fix: added railway as an activityType, added cbsCode attribute to Roa…#13

Merged
Zandv320 merged 1 commit intomasterfrom
fix/railway-activity-type-and-cbs-code
Aug 18, 2025
Merged

fix: added railway as an activityType, added cbsCode attribute to Roa…#13
Zandv320 merged 1 commit intomasterfrom
fix/railway-activity-type-and-cbs-code

Conversation

@Zandv320
Copy link
Contributor

added railway as an activityType, added cbsCode attribute to RoadAuthority and updated the test schema according to the new fixture data

Description

The activity type now has a railway value, roadAuthority now has a cbs code attribute which can be null and the geometry of a situation now includes the crs data.

Motivation and context

The tests where failing in the pipeline due to changes made in their API, also the schema was not matching the updated fixtures

If it fixes an open issue, please link to the issue here (if you write fixes #num
or closes #num, the issue will be automatically closed when the pull is accepted.)

How has this been tested?

I made sure i had fully updated the fixtures so that i had the most recent testdata. After this i ran the situationsTest locally to verify my schema changes matches the testdata.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have read the CONTRIBUTING document.
  • My pull request addresses exactly one patch/feature.
  • I have created a branch for this patch/feature.
  • Each individual commit in the pull request is meaningful.
  • I have added tests to cover my changes.
  • If my change requires a change to the schema, I have updated it accordingly.
  • If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

…dAuthority and updated the test schema according to the new fixture data
@Zandv320 Zandv320 requested a review from StanH-Swis August 18, 2025 09:30
@Zandv320 Zandv320 self-assigned this Aug 18, 2025
@Zandv320 Zandv320 merged commit 7f5a358 into master Aug 18, 2025
14 of 15 checks passed
self::Event => 'Evenement',
self::Waterway => 'Vaarweg werk',
self::WaterwayEvent => 'Vaarweg evenement',
self::Railway => 'Spoorweg',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd call this "Spoorweg werk"

"type": "object",
"additionalProperties": false,
"properties": {
"recordId": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't allowed according to the GeoJSON spec. Is this correct? 🤔

"type": {
"$ref": "#/definitions/GeometryType"
},
"crs": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is incorrect, this is how it's present in the API (and the GeoJSON-spec):

"crs": {
    "type": "name",
    "properties": {
        "name": "EPSG:4326"
    }
},

According to this schema, it should be something like this:

"crs": {
    "name": "EPSG:4326"
},

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JaZo JaZo deleted the fix/railway-activity-type-and-cbs-code branch September 1, 2025 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants