POST Updates the geometry of the feature on the basis of the dataset name and any one of the filter or featureId provided by the user.

Exact public source snapshot

This operation is retained because its version-labelled public specification differs structurally from another generation. It is comparison evidence, not a promise of current support, compatibility, entitlement, or availability.

Request target

Call the operation

POSThttps://mgis-apiv2.mappls.com/sat/updateGeom?datasetNme=a01072020

Base URLhttps://mgis-apiv2.mappls.com/

Authenticationbearer

Journey rolecommand

Content typesapplication/json

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

datasetNmerequired

querystring

The name of the datasetNme that user wants to delete.

a01072020

filter

querystring

The unique filter condition specifically used to selectively include or exclude items from a set or dataset.

id=34801

featureID

querystring

unique feature id to delete the particular feature id. featureID can take input multiple values which should be comma separated.It can delete multiple feature.

a01072020.55,a01072020.60,a01072020.57

Required body

Body schema

FieldTypeDescriptionExample

geometry

object

No field description in the source contract.

28.612964,77.229463

geometry.coordinates

unknown

updated geomtery coordinates. Case-1 multipoint {"geometry":{"coordinates":[500000,54505678]}} Case-2 multipolygon {"geometry":{"coordinates":[[[76.55555,24.046464],[76.552734,28.844674],[83.056641,28.844674],[83.056641,24.046464],[76.55555,24.046464]]]}} Case-3 multiline {"geometry":{"coordinates":[[500000,54505678],[0,540000],[5450000,0]]}}

28.612964,77.229463

Request body example

{
  "geometry": {
    "coordinates": "example"
  }
}

Interactive, local, and credential-safe

Build your request in eight languages

Change source-backed examples once, validate required inputs, and copy the synchronized cURL, JavaScript, Python, Java, C#, Go, PHP, or Ruby request. Credentials remain environment references, and this page never sends a provider request.

Local request composerCode stays local · fixtures are explicit

Generated in eight languages

Environment-backed credentials

POST

https://mgis-apiv2.mappls.com/sat/updateGeom?datasetNme=a01072020&filter=id%3D34801&featureID=a01072020.55%2Ca01072020.60%2Ca01072020.57

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request POST \
  --url 'https://mgis-apiv2.mappls.com/sat/updateGeom?datasetNme=a01072020&filter=id%3D34801&featureID=a01072020.55%2Ca01072020.60%2Ca01072020.57' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{"geometry":{"coordinates":"example"}}'

Credential-safe by constructionSet MAPPLS_ACCESS_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Five language quickstarts

Send a production-shaped request

Examples use environment-backed access tokens, explicit timeouts where supported, status checks, and JSON bodies derived from the source schema. Replace sample identifiers and coordinates with values from your application.

POST /sat/updateGeom

curl --request POST \
  --url 'https://mgis-apiv2.mappls.com/sat/updateGeom?datasetNme=a01072020' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "geometry": {
    "coordinates": "example"
  }
}'

Success and failure behavior

Responses

200

400

Bad Request, User made an error while creating a valid request.

401

Unauthorized.

500

Internal Server Error, the request caused an error in our systems.

200 response fields

FieldTypeDescriptionExample

code

string

Error code.

200

success

string

No field description in the source contract.

true

message

string

If everything goes ok then user receives a message indicating that geometry updated on mGIS platform

Geometry Updated

data

unknown

No field description in the source contract.

{}

Response example

{
  "code": "200",
  "success": true,
  "message": "Geometry Updated",
  "data": {}
}

stateful integration

Operate it safely

command

This operation creates or triggers durable state. Supply an idempotency strategy and persist the returned identifier before continuing.

Keep credentials and raw tokens out of source, client bundles, prompts, and logs.Record the operation ID, status, latency, retry count, and source contract version in traces.Classify 4xx responses before retrying; back off and add jitter for retryable 5xx or transport failures.Persist resource identifiers and apply commands exactly once in effect across retries and event replay.

Auditable source

Contract provenance

Source file: mappls-developer-platform/data/corpus/public-api-contracts/mapmyindia-mgis-apis/docs/v2/custom/sat-apis.yml
SHA-256: a2a4cba3e839f88138a9856683d09a09e1ca7a5a9f0ab93785da7b28f3ba215e
Normalization: Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.
Source record: Open repository audit