{"id":19556139,"url":"https://github.com/geovation/muddi_compliance","last_synced_at":"2025-06-21T15:06:52.847Z","repository":{"id":207190496,"uuid":"702476614","full_name":"Geovation/muddi_compliance","owner":"Geovation","description":"Project for the development of validation techniques to ensure ingress and egress of data is MUDDI compliant.","archived":false,"fork":false,"pushed_at":"2023-11-14T15:57:04.000Z","size":1638,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":3,"default_branch":"main","last_synced_at":"2025-06-21T15:06:46.104Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Geovation.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-10-09T11:47:11.000Z","updated_at":"2023-11-14T13:08:28.000Z","dependencies_parsed_at":"2023-11-14T15:28:55.334Z","dependency_job_id":"2a5608f6-ceed-4fb1-b9b9-d473a00d23c8","html_url":"https://github.com/Geovation/muddi_compliance","commit_stats":null,"previous_names":["geovation/muddi_compliance"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Geovation/muddi_compliance","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Geovation%2Fmuddi_compliance","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Geovation%2Fmuddi_compliance/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Geovation%2Fmuddi_compliance/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Geovation%2Fmuddi_compliance/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Geovation","download_url":"https://codeload.github.com/Geovation/muddi_compliance/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Geovation%2Fmuddi_compliance/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":261143149,"owners_count":23115674,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-11T04:36:56.432Z","updated_at":"2025-06-21T15:06:47.823Z","avatar_url":"https://github.com/Geovation.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# MUDDI Compliance\nProject for the development of validation techniques to ensure ingress and egress of data is MUDDI (Model for Underground Data Definition and Integration) compliant.\n\n## Database\nWe sought to examine how a schema that conformed to MUDDI could be created to support the ingestion of typical utility source data. We organised the OGC code sprint work into creation of a backend to store MUDDI-compliant data and a front end to display it. To facilitate the task, we had to transform open utility data into MUDDI-compliant data.\n\nThe datasets we chose to ingest in this example are referenced [here](https://github.com/opengeospatial/developer-events/wiki/muddi%E2%80%90overview#:~:text=A%20number%20of%20datasets%20a%20freely%20available%20on%20open%20data%20portals%2C%20operated%20by%20certain%20network%20utility%20operators%2C%20please%20download%20these%20directly).\n\nThe conceptual schema is a direct interpretation of the MUDDI conceptual model as a database entity relationship diagram. Each feature type in the model is represented by a table in the conceptual schema.\n\nHowever in the conceptual model there are both ‘real’ feature types and ‘abstract’ feature types.  Real feature types are represented as tables in the logical schema, and these tables inherit attribution from the abstract feature types above them in the conceptual model. The logical schema illustrates the minimum attribution required for MUDDI compliance, and it is expected that any implementation would introduce additional attribution as required for their individual use case.\n\n## JSON-FG\nThe aim of the JSON-FG work was to investigate creating a MUDDI compliant method for supporting the exchange of underground asset data between trusted parties. Using JSON-FG we could support a MUDDI schema while retaining the correct EPSG code.","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgeovation%2Fmuddi_compliance","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fgeovation%2Fmuddi_compliance","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgeovation%2Fmuddi_compliance/lists"}