XtoCityDB improvement and alternative #51
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… transforming building data into CityDB schema, this runs custom SQL scripts to extract thematic surfaces and make available through Ontop via custom mapping. It can also work with TOID-UPRN data.
…relying on CityDB post-processing.
…unlogged for CityDB post-processing.
…iour for CityDB datasets.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of relying on CityDB post-process to generate building footprints, insert footprints directly into CityDB schema for XtoCityDB data upload. This should reduce upload time.
Added additional example to upload LoD1 building data. Instead of using XtoCityDB upload which convert the building data into CityDB schema, the new example upload the building data to PostGIS, and it is made SPARQL queryable by Ontop using a bespoke OBDA file. Local testing suggests that this can reduce upload time significantly with respect to XtoCityDB (~40%), without affecting the result of SPARQL queries. However, it should be noted that the generated IRI for buildings are not persistent with this method.