Skip to content

Add identification configuration to sensors/processes - #359

Closed
earocorn wants to merge 6 commits into
opensensorhub:devfrom
earocorn:identification-info
Closed

earocorn wants to merge 6 commits into
opensensorhub:devfrom
earocorn:identification-info

Conversation

@earocorn

Copy link
Copy Markdown
Contributor

This also fixes a small existing UI bug that would not display protected List config fields from the ResponsibleParty class (and other classes with protected fields but public accessors).

The identification info is used to override the system UID, optional system kind UID, and contact information in the system description for both sensor drivers and processes.

}
}
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can we avoid this by making it an ArrayList in the config rather than a Collection?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The issue here is that the collection/list (these are already List<String>) fields in ResponsibleParty are protected, so those fields do not show up in the UI. This seems to be an existing bug as the list fields don't show up in the UI from OGCServiceConfig. For example, go to SOS Service -> Capabilities Info, and you will see that the list fields (voiceNumbers, faxNumbers, deliveryPoints, and emails) do not show up.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The unit test in TestResponsiblePartyProperties is for confirming this.

@alexrobin
alexrobin changed the base branch from master to dev November 4, 2026 22:31
@earocorn earocorn closed this Nov 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.

2 participants