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.

Sign up for GitHub

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

Jump to bottom

[PilotageDistrict.geometry] Why GM_Surface 0..* instead of GM_MultiSurface 0..1 ? #229

Open
rik opened this issue May 3, 2023 · 0 comments
Open

[PilotageDistrict.geometry] Why GM_Surface 0..* instead of GM_MultiSurface 0..1 ? #229

rik opened this issue May 3, 2023 · 0 comments
Labels
Specification question

Comments

@rik
Copy link
Contributor

rik commented May 3, 2023 •
edited
Loading

There is a multisurface concept. Why represent this as a list of Surfaces?

This is the case not only for PilotageDistrict.geometry but most geometries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Specification question
Projects
SPPNaut - S127 questions
Status: To send
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rik