A need to aggregate the network segments into a single object was briefly discussed yesterday. It was agreed to add an additional attribute to the tables representing networks (roads, pipelines, etc.) to capture a unique id for this aggregated feature. This requirements was already accounted for in the FSDF network model. A new table for the aggregated feature will be created. This table attributes are finalised at the moment and might slightly vary for different features. I'll update relevant excel spreadsheets on GitHub when available.
I am going to verify some of the data content to ensure that the attributes in the ontologies you created (thanks for that) match the data. These potential changers may or may not affect the current ontology versions, e.g. licence information store a link to the document itself or an URI to it. I hope to have this meeting today-tomorrow.
https://github.com/GeoscienceAustralia/FSDF/blob/master/core.md
@dr-shorthair
Hi Simon,
FYI
A need to aggregate the network segments into a single object was briefly discussed yesterday. It was agreed to add an additional attribute to the tables representing networks (roads, pipelines, etc.) to capture a unique id for this aggregated feature. This requirements was already accounted for in the FSDF network model. A new table for the aggregated feature will be created. This table attributes are finalised at the moment and might slightly vary for different features. I'll update relevant excel spreadsheets on GitHub when available.
I am going to verify some of the data content to ensure that the attributes in the ontologies you created (thanks for that) match the data. These potential changers may or may not affect the current ontology versions, e.g. licence information store a link to the document itself or an URI to it. I hope to have this meeting today-tomorrow.
Irina