Partially update parcel
PATCH /obp/v7.0.0/banks/ogcr/dynamic-entities/parcel/PARCEL_ID
OBPv7.0.0-dynamicEntity_patchparcel_ogcr Roles: CanUpdateDynamicEntityRecord_parcel(per bank) _Parcel(ogcr)Dynamic-EntityDynamic
Partially update parcel: only the fields supplied in the body are changed; others are preserved.
This is also the write path for field-level write-restricted fields (those declared with
write_role_required or an explicit write_role). Authorisation is per field present in the body:
a write-restricted field requires that field's write role, and an unrestricted field requires the entity
update role. You may change a field if (and only if) you hold the role that governs it; the request is
rejected with 403 (missing role) listing the roles you lack. There is no blanket entity-update
precondition — holding only a field's write role is sufficient to PATCH that field alone.
Parcel' means a geospatially defined unit of land, identified by its boundary geometry. parcel holds the stable, rarely-changing identity of the land (geometry, CRS, official land-registry codes). This Dynamic Entity is part of OGCR.
Property List:
- parcel_id: Internal identifier for the parcel.
- multipolygon_coordinates: GeoJSON MultiPolygon boundary of the parcel.
- coordinate_reference_system: Coordinate Reference System (CRS) identifier that defines how to interpret the geometry coordinates (e.g., EPSG:4326 for WGS84).
- cadastral_reference: Member state national cadastral registry ID
- iacs_codes: Array of identifiers referencing the parcel in the Member State’s IACS (Integrated Administration and Control System). Only if applicable.
- lpis_codes: Identifiers from the Land Parcel Identification System (LPIS) that reference official “reference parcels”/land blocks. Only if applicable.
MethodRouting settings example:
<details>
{
"is_bank_id_exact_match":false,
"method_name":"dynamicEntityProcess",
"connector_name":"rest_vMar2019",
"bank_id_pattern":".*",
"parameters":[
{
"key":"entityName",
"value":"parcel"
}
{
"key":"url",
"value":"http://mydomain.com/xxx"
}
]
}
</details>
User Authentication is Required. The User must be logged in. The Application must also be authenticated.
Example request body
{
"parcel_id": "parcel_03OGNWO397234DQ",
"multipolygon_coordinates": {
"type": "MultiPolygon",
"coordinates": [
[
[
[
13.405,
52.52
],
[
13.406,
52.52
],
[
13.406,
52.521
],
[
13.405,
52.521
],
[
13.405,
52.52
]
]
]
]
},
"coordinate_reference_system": "EPSG:4326",
"cadastral_reference": "string",
"iacs_codes": "DE-BB-IACS-2026-0012345678",
"lpis_codes": "DE-BB-LPIS-REFPARCEL-0098765432"
}Example success response
{
"bank_id": "ogcr",
"parcel": {
"parcel_id": "parcel_03OGNWO397234DQ",
"multipolygon_coordinates": {
"type": "MultiPolygon",
"coordinates": [
[
[
[
13.405,
52.52
],
[
13.406,
52.52
],
[
13.406,
52.521
],
[
13.405,
52.521
],
[
13.405,
52.52
]
]
]
]
},
"coordinate_reference_system": "EPSG:4326",
"cadastral_reference": "string",
"iacs_codes": "DE-BB-IACS-2026-0012345678",
"lpis_codes": "DE-BB-LPIS-REFPARCEL-0098765432"
},
"metadata": {
"created": {
"at": "2026-09-30T10:12:00Z",
"user_id": "a9f2c7e1-3d4b-4a5c-8e6f-7a8b9c0d1e2f",
"on_behalf_of_user_id": "9ca9a7e4-6d02-40e3-a129-0b2bf89de9b1"
},
"updated": {
"at": "2026-09-30T11:40:00Z",
"user_id": "9ca9a7e4-6d02-40e3-a129-0b2bf89de9b1",
"on_behalf_of_user_id": "9ca9a7e4-6d02-40e3-a129-0b2bf89de9b1"
}
}
}Possible errors (4)
- OBP-20001: User not logged in. Authentication is required!
- OBP-20006: User is missing one or more roles:
- OBP-10001: Incorrect json format.
- OBP-50000: Unknown Error.