Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -26,13 +26,13 @@
26	26
27	27	= How do I query the KG Spatial Search? =
28	28
29		-Simply use the API endpoint at [[https:~~/~~/spatial.kg.ebrains.eu/api/>>https://spatial.kg.ebrains.eu/api/]] by running queries according to the following examples:
	29	+Simply use the API endpoint at [[https:~~/~~/spatial.kg.ebrains.eu/api/spatial_objects>>https://spatial.kg.ebrains.eu/spatial_objects]] by running queries according to the following examples:
30	30
31	31	== Get started: Query by a "bounding box" (hyperrectangle) ==
32	32
33	33	{{code language="bash" layout="LINENUMBERS"}}
34	34	curl -X 'POST' \
35		- 'https://spatial.kg.ebrains.eu/spatial-search/cores/ebrains/spatial_objects' \
	35	+ 'https://spatial.kg.ebrains.eu/api/spatial_objects' \
36	36	-H 'accept: application/json' \
37	37	-H 'Content-Type: application/json' \
38	38	-d '{
...	...	@@ -65,8 +65,17 @@
65	65	{{/code}}
66	66
67	67
	68	+= Technical details of the ingestion pipeline =
68	68
	70	+The current pipeline is regularly parsing locareJSON files registered in the KG.
69	69
	72	+* Points are translated to the data structure of spatial search without manipulation
	73	+* Polyhedrons are translated via the [[vtk>>https://pypi.org/project/vtk/]] library into a point cloud of (currently) a density of 1 coordinate unit (by ray-casting on an obb-tree)
	74	+* Other geometries are work-in-progress
	75	+
	76	+The resulting files (all representing point-clouds) as well as the space definitions are uploaded to the [[bucket of this collab>>https://data-proxy.ebrains.eu/kg-spatial-search]]. A cron job running on the spatial search server pulls the files from the repo and rebuilds the databases index in regular intervals.
	77	+
	78	+
70	70
71	71	)))
72	72