glassmap.clyeh.xyz

remove_from_map

Take something off the map: a shape or a note an agent put there, or a feature out of the highlighted selection. Ids come in three forms and can be mixed in one call - "drawing: " and "annotation: ", as map state lists them under drawings and annotations, and the id of a currently selected feature such as "osm:node:123". This never deletes map data. Features and places cannot be removed; naming a selected feature only takes it out of the highlight. Taking a shape or a note off the map is permanent: there is no undo, and the only way back is to draw or pin it again. Shapes and notes the human made themselves - source "user" in map state - are not removed: they come back under refused, and the human takes their own mark off by tapping it on the map and pressing Remove. Everything else in the same call still happens. No per-id problem fails the batch: what could not be removed is accounted for by name under refused (with one refused_reason for all of them), not_selected (a loaded feature that was not highlighted, so there was nothing to take out), unknown_ids, and malformed_ids with one malformed_error saying which forms do work. Returns what was removed and the new map state, so no follow-up read is needed.

Input schema

{
  "type": "object",
  "properties": {
    "ids": {
      "type": "array",
      "minItems": 1,
      "maxItems": 100,
      "items": {
        "type": "string"
      },
      "description": "What to take off the map, in any mix of the three forms: \"drawing:<n>\" for a shape, \"annotation:<n>\" for a note, or the id of a currently selected feature, which leaves the selection and stays on the map (at most 100; repeats count once). There is no \"remove everything\": an empty array is refused, and clearing the highlight is select_features({ids: []})."
    }
  },
  "required": [
    "ids"
  ],
  "additionalProperties": false
}