Changes to make the fast CTRE index builder work for OSM (do not merge) #404
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.
This PR should not be merged into the master as is because some of it is ad-hoc (items 1 and 4) and some of it is just congifuration (item 3). Here is what it does:
Assume that all triples are subject-predicate-object (no , or ; syntax to avoid repeating the subject and/or predicate) and that all triples are on a single line and end with a newline.
In the current master, all literals with ^^ after the last quote are considered as xsd values, which cannot be externalized. In particular, this prevents the externalization of literals of type ^^geo:wktLiteral . This could be considered a BUG in the current master, which is fixed by a change in this PR.
Externalize all literals of length > 128 (so far the threshold was 1024). This will externalize all larger geometries, but not POINTs and simple geometries like buildings. This should actually be configurable in the
settings.json
.Don't run the TurtleParserTest because it has several tests concerning the escaping of , and ; which now fail due to 1.