Skip to content

Update relation

  • One of the main OpenStreetMap API usabilities

Updates data for a existing relation element.

To update existing relation you must operate inside an open changeset

Insert the ongoing changeset ID changeset to the request body. After completing various operations on the element, you should close a changset (or it will close automatically). You can also do multiple operations on many elements (create, update, delete) in one ongoing changeset.

A full representation of the element as it should be after the update has to be provided

Any tags, way-node refs, and relation members that remain unchanged must be in the update as well. A version number must be provided as well, it must match the current version of the element in the database.

In request body the relation ID id, relation version version, member role role and tag k=" " v=" " are also required (check the example).

Request

/api/0.6/relation/{id}
Body parameters Inserts options
<member ... role=" "> "outer" / "inner" / "forward" / "backward"
<tag k="type" v=" "> "relation" / "multipolygon"
Example body request for update relation with ID
<osm>
  <relation id="4305233945" version="1" changeset="412389">
    <member type="way" ref="4307240014" role="outer"/>
    <member type="way" ref="4307240017" role="outer"/>
    <tag k="landuse" v="garden"/>
    <tag k="type" v="multipolygon"/>
    <tag k="name" v="Fragment of plot no 103 on ROD-Association garden"/>
  </relation>
</osm>

Response

succesUpdateRelation_example.xml
1
2

Error codes

When there are errors parsing the XML – a text message explaining the error is returned (example: Version is required when updating). This can also happen if you forget to pass the Content-Length header. When a changeset ID is missing.

When no element with the given ID could be found (example: Requested resource could not be found).

If the changeset in question has already been closed – either by the user or as a result of the auto-closing feature (example: The changeset 412384 was closed at 2025-04-23 11:51:26 UTC). Also, if the user trying to update the changeset is not the same, as the one that created it.

When a relation has nodes that do not exist, were deleted or aren't visible.

When the request has been blocked due to rate limiting.