Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

noise: mapping of activities outside the grid #3548

Closed
tschlenther opened this issue Nov 7, 2024 · 0 comments
Closed

noise: mapping of activities outside the grid #3548

tschlenther opened this issue Nov 7, 2024 · 0 comments
Assignees

Comments

@tschlenther
Copy link
Contributor

We can reduce the noise analysis to a (small) subarea of the scenario. The SimWrapper contrib highly facilitates this (by simply setting ShpOptions). As the spatial extent of our scenarios is ususally quite large, these days, this is a convenient and frequent use case, I suppose.

When you do this, all activities that are configured by NoiseConfigGroup.consideredActivitiesForDamageCalculation are mapped to the Grid, which has the spatial extent as specified either in the NoiseConfigGroup or e.g. by the ShpOptions via the SimWrapper contrib.
The mapping is conducted in the way that each activity's coordinate is associated to the nearest Grid cell, in other words: all activities from the entire scenario (of the specified activity types) are included (in my understanding, and based on the screenshots below).
This is most probably not intended - why setting a sub-area/focus area for the noise analysis in the first place?
Results look libe below, where you can see the immisions being nicely distributed over the focus area, but for the damages, all (work and home) acitvities happening in Munich (and Ingolstadt etc.) are mapped to the edge of the Kelheim focus area - leading tp distortion in the viz.

grafik
grafik

The solution would be to filter the activity coords according the spatial extent of the Grid. I have an idea how to do this and will (hopefully) take a try in the MATSim hackathon in winter.

Related:
#3519

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant