API reference/mGIS Analytics
DELETEstatefulexact public snapshot

Deletes the feature from the featureList.

/sat/deleteFeature

Deletes the feature from the featureList on the basis of the filter value or the featureID value 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.

Call the operation

DELETEhttps://mgis-apiv2.mappls.com/sat/deleteFeature?datasetNme=a01072020
Base URLhttps://mgis-apiv2.mappls.com/
Authenticationbearer
Journey roleretire
Content typesNo request body

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

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
DELETERequest inputs
3 editable · 0 protected
Generated in eight languages
Environment-backed credentials
DELETEhttps://mgis-apiv2.mappls.com/sat/deleteFeature?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 DELETE \
  --url 'https://mgis-apiv2.mappls.com/sat/deleteFeature?datasetNme=a01072020&filter=id%3D34801&featureID=a01072020.55%2Ca01072020.60%2Ca01072020.57' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}"

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.

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.

DELETE /sat/deleteFeature
curl --request DELETE \
  --url 'https://mgis-apiv2.mappls.com/sat/deleteFeature?datasetNme=a01072020' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Responses

200

OK

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 the columns specified by the user in the updatedValues have been updated.

Feature deleted.
data
unknown

No field description in the source contract.

{}
Response example
{
  "code": "200",
  "success": true,
  "message": "Feature deleted.",
  "data": {}
}

Operate it safely

retire

This operation removes or retires state. Confirm ownership, dependent resources, audit retention, and recovery behavior before execution.

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.

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.