Changes for page kg-spatial-search

Last modified by oschmid on 2023/08/22 11:23
From version 14.1
edited by oschmid
on 2023/08/22 09:35
Change comment: There is no comment for this version
To version 16.1
edited by oschmid
on 2023/08/22 11:23
Change comment: There is no comment for this version

Summary

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/cores/ebrains/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/cores/ebrains/spatial_objects' \
36 36   -H 'accept: application/json' \
37 37   -H 'Content-Type: application/json' \
38 38   -d '{
... ... @@ -64,7 +64,28 @@
64 64  }
65 65  {{/code}}
66 66  
67 +== How to get the available spaces? ==
67 67  
69 +To get a list of available spaces (to know which coordinate systems are available), please run
70 +
71 +{{code language="bash" layout="LINENUMBERS"}}
72 +curl -X 'POST' \
73 + 'https://spatial.kg.ebrains.eu/spaces' \
74 + -H 'accept: application/json' \
75 + -H 'Content-Type: application/json' \
76 + -d '{}'
77 +{{/code}}
78 +
79 +to retrieve a list of spaces. To get more information about the space, you can then ask for a specific one with
80 +
81 +{{code language="bash" layout="LINENUMBERS"}}
82 +curl -X 'GET' \
83 + 'https://spatial.kg.ebrains.eu/spaces/AMB-CCF_v3-RAS' \
84 + -H 'accept: application/json' \
85 + -H 'Content-Type: application/json'
86 +{{/code}}
87 +
88 +
68 68  = Technical details of the ingestion pipeline =
69 69  
70 70  The current pipeline is regularly parsing locareJSON files registered in the KG.