Skip to content

AER-4271 Added support for using max speed for NON_URBAN ROADS#379

Merged
Hilbrand merged 4 commits intoaerius:mainfrom
Hilbrand:AER-4271-non-urban-road
Apr 10, 2026
Merged

AER-4271 Added support for using max speed for NON_URBAN ROADS#379
Hilbrand merged 4 commits intoaerius:mainfrom
Hilbrand:AER-4271-non-urban-road

Conversation

@Hilbrand
Copy link
Copy Markdown
Member

@Hilbrand Hilbrand commented Apr 2, 2026

With new road emissions for NON_URBAN_ROAD speed will be relevant. Therefore speed will be read. Because with new data speed determines the emission and not only the road type code a default speed will be set if the speed is null or 0. The speed set is representative for the road type. For NON_URBAN_ROAD_NATIONAL it will be 80, for NON_URBAN_ROAD_GENERAL it will be 60. Calculator 2025 doesn't use these speed values yet, but having set them has no impact, but it also isn't effecting anything.

Simplified GML2SRMRoad v4 implementation by merging specific variables with convertRoadType because specificVariables was only used for road type, and since both methods have a SRM specific implementation the SRM1 case can be moved to the convertRoadTypeCode.

With new road emissions for NON_URBAN_ROAD speed will be relevant. Therefore speed will be read.
Because with new data speed determines the emission and not only the road type code, the road type code has been generalized to NON_URBAN_ROAD in the GML.
The road type code NON_URBAN_ROAD_NATIONAL and NON_URBAN_ROAD_GENERAL could be used on both SRM1 and SRM2 soruces. But these with the new data they become explicitly for use with a specific SRM version.
NON_URBAN_ROAD_NATIONAL is for SRM2 roads, and NON_URBAN_ROAD_GENERAL for SRM1 roads. This was somewhat implicit, as in Calculator UI only NON_URBAN_ROAD_NATIONAL was used,
and only SRM2 can be modified in Calculator. But it would be possible to manually use NON_URBAN_ROAD_GENERAL in an SRM2 source.
Both NON_URBAN_ROAD_NATIONAL and NON_URBAN_ROAD_GENERAL are still supported to be used in GML, also for backward compatibility.
@Hilbrand Hilbrand requested review from BertScholten and willvoo April 2, 2026 15:02
Copy link
Copy Markdown
Contributor

@willvoo willvoo left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Member

@BertScholten BertScholten left a comment

Choose a reason for hiding this comment

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

Not a fan of the temporary bit, but otherwise LGTM

- Simplified GML2SRMRoad v4 implementation by merging specific variables with convertRoadType because specificVariables was only used for road type, and since both methods have a SRM specific implementation the SRM1 case can be moved to the convertRoadTypeCode.
- In Road2GML non urban road type conversion inversed check on if 0 speed present from any to all such that no negative check has to be done
@Hilbrand Hilbrand requested a review from BertScholten April 3, 2026 09:57
…AL/GENERAL) only.

When importing always set a road speed for NON_URBAN_ROAD when road is 0 (or not set) to representative speeds.
Copy link
Copy Markdown
Member

@BertScholten BertScholten left a comment

Choose a reason for hiding this comment

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

LGTM

@Hilbrand Hilbrand merged commit f8c5303 into aerius:main Apr 10, 2026
1 check passed
@Hilbrand Hilbrand deleted the AER-4271-non-urban-road branch April 10, 2026 09:24
@Hilbrand Hilbrand changed the title AER-4271 Added support for using max speed with NON_URBAN ROADS AER-4271 Added support for using max speed for NON_URBAN ROADS Apr 10, 2026
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