redmer / rdf-geopackage Goto Github PK

Output data enumerates from from rdf:_0, but rdf:_1 should be the first item in an ordered RDF collection.

According to http://www.geopackage.org/spec/#table_column_data_types, GeoPackage columns can be typed with i.a. Booleans and DateTimes. In the RDF output, they are just output as the underlying SQLite data types (integer and text).

1. Find out where this metadata is saved
2. See if there is a GeoPackage-js DAO to access this metadata and pass it along to valueToTerm()

http://www.opengis.net/def/crs/${organization.toUpperCase()}/0/${id} is now used. Is in all cases correct? Or could a correct GeoPackage provide incorrect organization and organization_coordsys_id?

There are few tests provided. Write more tests that check model output, etc.

Besides the console.log debugging comments coming from the package, it has a lot of dependencies too: 21 direct, 178 transitive.

Explore how to implement this in a tinier package:

• how to read the SQLite db
• how to read the geometry columns
• how to read the geometry SRS and definition

This is due to GeoJSON, that defaults to WGS84. The GeoJSON iterator used for feature tables is GeoPackage#iterateGeoJSONFeatures() in

Changes there would also require refactoring of

Features appear off by some 180 m. Investigate whether this is due to an issue in the rdf-geopackage code or if it's an issue upstream with GeoPackage or Proj4Jjs.

The current v1 parameter is a bit ideosyncratic, with its space separated values, not using abbreviated bbox.

Proposal:

1. rename to --bbox, rename --bounding-box-crs to --bbox-crs.
2. change valuespace in accordance with https://docs.ogc.org/is/17-069r4/17-069r4.html#_parameter_bbox to comma-separated values

This is expected to be a breaking change? Or allow both types of values.

When loading a 180 MB GeoPackage file, too many RDF.Quads are generated in a non-streaming fashion.

First priority, enable some limits on the Quad generation.

Secondly, work out how RDF.Stream works.

The output hasn't been formally checked yet. Issue #11 is an example of an issue that could have come forth from such a check.

• Facade-X
• GeoSPARQL Done in #19

1. CRS84 (WGS84) is the only valid serialization for GeoJSON req25
2. The tables original SRS is used for the WKT serialization.

Should the default geometry be specific for (1) and (2) separately or be combined into one, as they aren't materially different.
The "perhaps" in 6.4.2 implies that they should be two different geometries iff the table SRS is not WGS84.

When executing rdf-geopackage on Windows (Node v18.17.1), an error prohibits execution.

$ rdf-geopackage -i .\Selectie_Wallengebied_Small.gpkg
Unable to register SqliteAdapter. The better-sqlite3 module was not found. Falling back to SqljsAdapter.
C:\Users\...\AppData\Roaming\npm\node_modules\@rdmr-eu\rdf-geopackage\node_modules\@ngageoint\geopackage\dist\canvaskit\canvaskit.js:1513
                    throw a;
                    ^

TypeError: Failed to parse URL from sql-wasm.wasm
    at Object.fetch (node:internal/deps/undici/undici:11576:11) {
  [cause]: TypeError [ERR_INVALID_URL]: Invalid URL
      at new NodeError (node:internal/errors:405:5)
      at new URL (node:internal/url:611:13)
      at new Request (node:internal/deps/undici/undici:7132:25)
      at fetch2 (node:internal/deps/undici/undici:10715:25)
      at Object.fetch (node:internal/deps/undici/undici:11574:18)
      at fetch (node:internal/process/pre_execution:229:25)
      at C:\Users\...\AppData\Roaming\npm\node_modules\@rdmr-eu\rdf-geopackage\node_modules\rtree-sql.js\dist\sql-wasm.js:158:271
      at C:\Users\...\AppData\Roaming\npm\node_modules\@rdmr-eu\rdf-geopackage\node_modules\rtree-sql.js\dist\sql-wasm.js:158:492
      at C:\Users\...\AppData\Roaming\npm\node_modules\@rdmr-eu\rdf-geopackage\node_modules\rtree-sql.js\dist\sql-wasm.js:158:505
      at new Promise (<anonymous>) {
    input: 'sql-wasm.wasm',
    code: 'ERR_INVALID_URL'
  }
}

Node.js v18.17.1

When writing to e.g. Turtle, the CLI options parsers recognizes that it is text/turtle.

The N3 StreamWriter however still outputs graph information, whereas this should have been filtered.