Api session event editor geolink set mapping: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 37: | Line 37: | ||
|} | |} | ||
===Example POST=== | ===Example POST=== | ||
Example POST: https://engine.tygron.com/api/session/event/editorgeolink/set_mapping/?f= | Example POST: https://engine.tygron.com/api/session/event/editorgeolink/set_mapping/?f=JSON&token=API_TOKEN | ||
with content: | with content: | ||
Revision as of 08:16, 1 April 2026
API Event to Map orginal Attribute name to a new name in the created feature.
| Name | Importance | Type | Description | Values |
|---|---|---|---|---|
| 0 | REQUIRED | (GEO_LINK Integer ID or multiple values in array [1, 2, 3]) | CustomGeo Link IDs | |
| 1 | REQUIRED | (String or multiple values in array ["a", "b", "c"]) | Orginal Attribute Names | |
| 2 | REQUIRED | (String or multiple values in array ["a", "b", "c"]) | New Attribute Names |
Response Codes
| Response Code: | Description |
|---|---|
| 204 | No Content |
| 300-600 | Codes Overview |
Example POST
Example POST: https://engine.tygron.com/api/session/event/editorgeolink/set_mapping/?f=JSON&token=API_TOKEN
with content:
[ [ 1, 2, 3 ], [ "Orginal Attribute Name 1", "Orginal Attribute Name 2", "Orginal Attribute Name 3" ], [ "New Attribute Name 1", "New Attribute Name 2", "New Attribute Name 3" ] ]