GET Download the dataset files in .kml, .shp or .geojson files on server.

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

GEThttps://mgis-apiv2.mappls.com/export_feature?datasetNme=ind_rails&fileType=.kml%2C+.shp+or+.geojson

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

Authenticationbearer

Journey roleobserve

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

datasetNmerequired

querystring

layername

ind_rails

fileTyperequired

querystring

Type of file you want to Download(.kml, .shp or .geojson).

.kml, .shp or .geojson

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

GEThttps://mgis-apiv2.mappls.com/export_feature?datasetNme=ind_rails&fileType=.kml%2C+.shp+or+.geojson

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://mgis-apiv2.mappls.com/export_feature?datasetNme=ind_rails&fileType=.kml%2C+.shp+or+.geojson' \
  --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.

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.

GET /export_feature

curl --request GET \
  --url 'https://mgis-apiv2.mappls.com/export_feature?datasetNme=ind_rails&fileType=.kml%2C+.shp+or+.geojson' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Success and failure behavior

Responses

200

Response when file successfully saved on server.

404

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

200 response fields

FieldTypeDescriptionExample

code

integer

No field description in the source contract.

200

success

string

No field description in the source contract.

true

message

string

No field description in the source contract.

File downloaded successfully.

download_url

string

No field description in the source contract.

https://mgis-apiv2.mappls.com/export_data/prj_ID/datasetNme_timestamp.fileType

Response example

{
  "code": 200,
  "success": true,
  "message": "File downloaded successfully.",
  "download_url": "https://mgis-apiv2.mappls.com/export_data/prj_ID/datasetNme_timestamp.fileType"
}

stateful integration

Operate it safely

observe

This operation observes durable platform state. Preserve resource identifiers and account for pagination, delay, and eventual consistency.

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/export-features-apis.yml
SHA-256: 0e6609fbac25fedcc94e168c9de96d9398dea70b3fdd3cdeaa12659133fa09ab
Normalization: Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.
Source record: Open repository audit