You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/client-proxy.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,9 +49,9 @@ then response will change to
49
49
```
50
50
51
51
Currently, value of X-Forwarded headers affects following URLs:
52
-
*[GET Publications](rest.md#get-publications), [GET Layers](rest.md#get-layers), [GET Maps](rest.md#get-maps), and [GET Workspace Maps](rest.md#get-workspace-maps)
52
+
*[GET Publications](rest.md#get-publications), [GET Layers](rest.md#get-layers), and [GET Maps](rest.md#get-maps)
53
53
*`url` key
54
-
*[POST Layers](rest.md#post-layers) and [POST Workspace Maps](rest.md#post-workspace-maps)
54
+
*[POST Layers](rest.md#post-layers) and [POST Maps](rest.md#post-maps)
55
55
*`url` key
56
56
*[GET Layer](rest.md#get-layer) and [PATCH Layer](rest.md#patch-layer)
57
57
*`url` key
@@ -72,7 +72,7 @@ Currently, value of X-Forwarded headers affects following URLs:
72
72
* each `legends` key if its HTTP protocol and netloc corresponds with `url` or `protocol`.`url`
73
73
*`style` key if its HTTP protocol and netloc corresponds with `url` or `protocol`.`url`
74
74
* NOTE: If client proxy protocol, host, or URL path prefix was used in URLs in uploaded file, then such values are also replaced with values according to X-Forwarded header values. Default values are used for requests without X-Forwarded headers (protocol is the one from [LAYMAN_CLIENT_PUBLIC_URL](env-settings.md#layman_client_public_url), host is [LAYMAN_PROXY_SERVER_NAME](env-settings.md#layman_proxy_server_name), and path prefix is empty string).
75
-
*[DELETE Layers](rest.md#delete-layers), [DELETE Workspace Maps](rest.md#delete-workspace-maps), [DELETE Layer](rest.md#delete-layer) and [DELETE Map](rest.md#delete-map)
75
+
*[DELETE Layers](rest.md#delete-layers), [DELETE Maps](rest.md#delete-maps), [DELETE Layer](rest.md#delete-layer) and [DELETE Map](rest.md#delete-map)
76
76
*`url` key
77
77
*[OGC endpoints](endpoints.md)
78
78
* Headers `X-Forwarded-For`, `X-Forwarded-Path`, `Forwarded` and `Host` are ignored
Copy file name to clipboardExpand all lines: doc/publish-map.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,12 @@ In QGIS, you need to implement following steps.
12
12
13
13
First, compose JSON valid against [map-composition schema](https://github.com/hslayers/map-compositions). For Layman, especially `describedBy`, `name`, `title`, `abstract`, `layers`, `projection`, and `extent attributes are important. Each layer must have `className` attribute equal to `HSLayers.Layer.WMS` or `WMS`.
14
14
15
-
Then save the file to Layman using [POST Workspace Maps](rest.md#post-workspace-maps) endpoint. Well-known [requests](https://requests.readthedocs.io/en/latest/) module can be used for sending HTTP requests. See especially
15
+
Then save the file to Layman using [POST Maps](rest.md#post-maps) endpoint. Well-known [requests](https://requests.readthedocs.io/en/latest/) module can be used for sending HTTP requests. See especially
16
16
-[More complicated POST requests](https://requests.readthedocs.io/en/latest/user/quickstart/#more-complicated-post-requests)
17
17
-[POST a Multipart-Encoded File](https://requests.readthedocs.io/en/latest/user/quickstart/#post-a-multipart-encoded-file)
Copy file name to clipboardExpand all lines: doc/rest.md
+18-19Lines changed: 18 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,11 @@
10
10
|Layer Style|`/rest/layers/<uuid>/style`|[GET](#get-layer-style)| x | x | x |
11
11
|Layer Chunk|`/rest/layers/<uuid>/chunk`|[GET](#get-layer-chunk)|[POST](#post-layer-chunk)| x | x |
12
12
|Workspace Layer Metadata Comparison|`/rest/workspaces/<workspace_name>/layers/<layername>/metadata-comparison`|[GET](#get-workspace-layer-metadata-comparison)| x | x | x |
13
-
|Maps|`/rest/maps`|[GET](#get-maps)|x| x |x|
13
+
|Maps|`/rest/maps`|[GET](#get-maps)|[POST](#post-maps)| x |[DELETE](#delete-maps)|
14
14
|[Map](models.md#map)|`/rest/maps/<uuid>`|[GET](#get-map)| x |[PATCH](#patch-map)|[DELETE](#delete-map)|
15
15
|Map Thumbnail|`/rest/maps/<uuid>/thumbnail`|[GET](#get-map-thumbnail)| x | x | x |
16
16
|Map File|`/rest/maps/<uuid>/file`|[GET](#get-map-file)| x | x | x |
17
-
|Workspace Maps|`/rest/workspaces/<workspace_name>/maps`|[GET](#get-workspace-maps)|[POST](#post-workspace-maps)| x |[DELETE](#delete-workspace-maps)|
18
-
|Workspace Map Metadata Comparison|`/rest/workspaces/<workspace_name>/layers/<layername>/metadata-comparison`|[GET](#get-workspace-map-metadata-comparison)| x | x | x |
17
+
|Workspace Map Metadata Comparison|`/rest/workspaces/<workspace_name>/maps/<mapname>/metadata-comparison`|[GET](#get-workspace-map-metadata-comparison)| x | x | x |
19
18
|Users|`/rest/users`|[GET](#get-users)| x | x | x |
20
19
|User|`/rest/users/<username>`| x | x | x |[DELETE](#delete-user)|
21
20
|Current [User](models.md#user)|`/rest/current-user`|[GET](#get-current-user)| x |[PATCH](#patch-current-user)|[DELETE](#delete-current-user)|
@@ -533,16 +532,12 @@ Get list of published maps (map compositions).
533
532
534
533
Have the same request parameters and response structure and headers as [GET Publications](#get-publications), except only maps are returned.
535
534
536
-
## Workspace Maps
537
-
### URL
538
-
`/rest/workspaces/<workspace_name>/maps`
539
-
540
-
### GET Workspace Maps
541
-
Get list of published maps (map compositions).
542
-
543
-
Have the same request parameters and response structure and headers as [GET Maps](#get-maps).
535
+
Query parameters:
536
+
-*workspace*: String, optional
537
+
- workspace identifier
538
+
- if present, only maps from this workspace are returned
544
539
545
-
### POST Workspace Maps
540
+
### POST Maps
546
541
Publish new map composition. Accepts JSON valid against [map-composition schema](https://github.com/hslayers/map-compositions) version 2 or 3 used by [Hslayers-ng](https://github.com/hslayers/hslayers-ng). Exact version of schema is defined by `describedBy` key of JSON data file.
547
542
548
543
Processing chain consists of few steps:
@@ -563,6 +558,8 @@ Response to this request may be returned sooner than the processing chain is fin
-*uuid*, string, e.g. `959c95fb-ab54-47a6-9694-402926b8fd29`
567
564
- map primary key
568
565
- used if specified, otherwise generated
@@ -603,11 +600,13 @@ JSON array of objects representing posted maps with following structure:
603
600
-**uuid**: String. UUID of the map.
604
601
-**url**: String. URL of the map. It points to [GET Map](#get-map).
605
602
606
-
### DELETE Workspace Maps
603
+
### DELETE Maps
607
604
Delete existing maps and all associated sources, including map-composition JSON file and map thumbnail for all maps in the workspace. The currently running [asynchronous tasks](async-tasks.md) of affected maps are aborted. Only maps on which user has [write access right](./security.md#access-to-multi-publication-endpoints) are deleted.
@@ -674,7 +673,7 @@ JSON object with following structure:
674
673
-**native_bounding_box**: List of 4 floats. Bounding box coordinates [minx, miny, maxx, maxy] in native CRS.
675
674
676
675
### PATCH Map
677
-
Update information about existing map. First, it deletes sources of the map, and then it publishes them again with new parameters. The processing chain is similar to [POST Workspace Maps](#post-workspace-maps), including [asynchronous tasks](async-tasks.md),
676
+
Update information about existing map. First, it deletes sources of the map, and then it publishes them again with new parameters. The processing chain is similar to [POST Maps](#post-maps), including [asynchronous tasks](async-tasks.md),
678
677
679
678
Calling concurrent PATCH requests is not supported, as well as calling PATCH when [POST/PATCH async chain](async-tasks.md) is still running, is not allowed. In such cases, error is returned.
680
679
@@ -683,7 +682,7 @@ Calling PATCH request when [WFS-T async chain](async-tasks.md) is still running
Parameters have same meaning as in case of [POST Workspace Maps](#post-workspace-maps).
685
+
Parameters have same meaning as in case of [POST Maps](#post-maps).
687
686
688
687
Body parameters:
689
688
-*file*, JSON file
@@ -702,7 +701,7 @@ Body parameters:
702
701
#### Response
703
702
Content-Type: `application/json`
704
703
705
-
JSON object, same as in case of [POST Workspace Maps](#post-workspace-maps).
704
+
JSON object, same as in case of [POST Maps](#post-maps).
706
705
707
706
### DELETE Map
708
707
Delete existing map and all associated sources, including map-composition JSON file and map thumbnail. The currently running [asynchronous tasks](async-tasks.md) of affected map are aborted.
@@ -727,8 +726,8 @@ Get JSON file describing the map valid against [map-composition schema](https://
727
726
728
727
Notice that some JSON properties are automatically updated by layman, so file obtained by this endpoint may be slightly different from file that was uploaded. Expected changes:
729
728
-**name** set to the map's name
730
-
-**title** obtained from [POST Workspace Maps](#post-workspace-maps) or [PATCH Map](#patch-map) as `title`
731
-
-**abstract** obtained from [POST Workspace Maps](#post-workspace-maps) or [PATCH Map](#patch-map) as `description`
729
+
-**title** obtained from [POST Maps](#post-maps) or [PATCH Map](#patch-map) as `title`
730
+
-**abstract** obtained from [POST Maps](#post-maps) or [PATCH Map](#patch-map) as `description`
732
731
-**user** updated on the fly during this request:
733
732
-**name** set to `<workspace_name>` in URL of this endpoint
734
733
-**email** set to email of the owner, or empty string if not known
0 commit comments