-
Notifications
You must be signed in to change notification settings - Fork 3
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
Bridges #6
Comments
The image is from slide 4 on the attached PowerPoint pdf and identifies a particular scenario along with the supporting report on the converter from S-100WG1/S-101PT01 meeting. Unfortunately US5NJ14M no longer exists publicly due to NOAA's rescheming and the bridge construction since then has changed the underlaying conditions but this scenario still holds true for our conversion process. The data from our testing is also attached. S101PT01-5.1 S-57 to S-101 Converter Update.pdf |
Use multiple C_AGGR for each bridge? I guess the issue here is that S-101 bridges can share features (pylons) but each bridge aggregation should really relate to a single "bridge"? this is the kind of use case we need to look at. The other issue, I guess is also propagating attributes correctly - i.e ensuring the bridge aggregation has the correct attributes from the S-57 features. |
I add a presentation that Friedhelm will make during the meeting on Monday 21 Feb. |
A placeholder issue for discussion on the automation of Bridge conversion between S-57 and S-101. Bridges are a potentially complex case as they combine some complicated feature transformations, attribution and association features.
This issue could usefully be progressed by looking at the features involved in current S-57 bridges, the modelling in the existing S-101 feature catalogue and also differences in geometry and attribution for the S-101 case.
The text was updated successfully, but these errors were encountered: