From 0268576f90800af3c008700b69c23e8d9a1f3439 Mon Sep 17 00:00:00 2001 From: Gobe Hobona Date: Fri, 17 Nov 2023 17:55:01 +0000 Subject: [PATCH] Update os_muddi.adoc --- .../engineering-report/sections/results/os_muddi.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2023/Open-Standards-Code-Sprint/engineering-report/sections/results/os_muddi.adoc b/2023/Open-Standards-Code-Sprint/engineering-report/sections/results/os_muddi.adoc index f946a79..430b2d6 100644 --- a/2023/Open-Standards-Code-Sprint/engineering-report/sections/results/os_muddi.adoc +++ b/2023/Open-Standards-Code-Sprint/engineering-report/sections/results/os_muddi.adoc @@ -18,12 +18,12 @@ One thing that the sprint participants found unclear in the candidate standard w [[img_os_muddi_networks]] .Relationships between types of networks in MUDDI -image::images/muddi/os_muddi_networks.jpg[] +image::images/muddi/muddi_networks.png[] To demonstrate that sample data conforming to the logical schema could be displayed on a web application, the sprint participants uploaded the data into a pygeoapi instance. The pygeoapi instance was then linked into a web application. A screenshot of the web application is shown in <>. [[img_os_muddi_webapp]] .A screenshot of a web application displaying underground asset data -image::images/muddi/os_muddi_webapp.png[] +image::images/muddi/muddi_os_webapp.png[] Future work on the storage aspects of the MUDDI task could involve using the MUDDI logical schema as a template for MUDDI compliance. The logical schema does not currently have much attribution about the assets themselves. Therefore any implementation would be expected to introduce additional attributes. The code for the logical schema is available at: https://github.com/Geovation/muddi_compliance