- URL:
- https://<mapservice-url>/<layerOrTableId>
- Methods:
GET
- Required Capability:
- Map
- Version Introduced:
- 9.3
Description
An individual layer/table resource represents a single layer/table in a map of a map service published by ArcGIS Server. It provides basic information about the layer/table such as its name, type, and fields. For layers, it provides additional information about the layer such as its parent and sublayers, minimum and maximum scales, extent, and copyright text.
If a layer is authored with display expression and not a display field, display
will be the first field used in the display expression.
supports
and supports
are dependent on the layer data source.
supports
would return false in the following scenarios:
- The layer / table resides in a workspace other than an enterprise or file geodatabase.
- The layer / table has more than one join defined on it.
- The layer / table is joined with another layer / table from a different workspace.
- The layer / table has an outer join and where the workspace is earlier than 10.1, Geodatabase and application server connection is used.
supports
would return false in the following scenarios:
- The layer / table resides in a workspace other than an enterprise database or File Geodatabase.
- The layer / table is joined with another layer / table from a different workspace.
New at 11.4
- A new property,
unique
was added that describes if a layer or a table, typically a query layer, supports non-integer based identifiers.Id Info type
issimple
when a single field is used to define unique identifiers for features or rows.type
iscomposite
when attributes from more than one fields are used to uniquely identify a feature or row in a layer or table.fields
reports which field(s) are chosen by the author as identifier field(s).- when
OID
isField Contains Hash Value true
, clients should ignore or avoid using values from the objectid field. These values are randomly generated.
- A new property,
max
reports the maximum number of unique-ids be returned in a query call.Unique ID Count - A new property,
max
reports the maximum number of object-ids or unique-ids are allowed to pass in anSelection Count export
operation'sselection
parameter.Definitions - Values for
max
andUnique ID Count max
can be modified in a service definition.Selection Count
New at 11.1
-
A new property,
supported
, was added that lists the supported spatial operators for the layer.Spatial Relationships -
A new property,
feature
, was added to describe cluster renderers.Reduction -
The
order
property was added to report on the feature drawing order. When this property is included as part of the export operation'sBy dynamic
parameter, the following rules are used to interpret the values:Layers - When
order
is not present in the layer definition, or is null, the layer's defaultBy order
is used (if the layer has a default forBy order
).By - If
order
is an empty array,By order
will be removed from the layer.By
- When
New in 10.9
-
preferred
is added as new property to allow the author recommend which time zone a client application should display all date-time values for this layer.Time Reference date
must be set to a time zone (i.e. cannot be null) whenFields Time Reference preferred
is set.Time Reference
-
When a layer has features with date-time values from multiple time zones and you want to keep those date-time values as-is (not convert them to a single time zone), you need to set
dates
toIn Unknown Timezone true
.-
When
dates
isIn Unknown Timezone true
, bothpreferred
andTime Reference date
must not be set.Fields Time Reference -
When
dates
isIn Unknown Timezone true
, date-time values, in a map service query results, are returned encoded numbers representing milliseconds since epoch (January 1, 1970) in each local time zone and don't get converted to UTC.Client applications must not perform any time zone conversion with these data.
-
When
dates
isIn Unknown Timezone false
, date-time values, in a map service query results, are returned encoded numbers representing milliseconds since epoch (January 1, 1970) in UTC.Client applications can perform any time zone conversion with these data since they are all returned in UTC.
-
-
-
The
Supports
property indicates if the ability to do lod queries can be turned on for a feature service layer. Lod queries have been turned on and can be queried when the layer includes anLOD lod
property. This allows to get tessellation of regularly shaped polygons such as hexagons, rectangles, square etc. Attributes for each features represent aggregated results from the point features fall within them.Infos -
Two new properties are added in
advanced
section for map service published from ArcGIS Pro.Query Capabilities supports
allows client applications like ArcGIS Pro to have more control while working with time-aware layers using time sliders. You can decide whether to include or exclude start or end time.Time Relation supports
allows client applications use SQL conforms to standardized queries specifications whenSql Format use
isStandardized Queries false
.
-
supports
isPercentile Statistics true
for layers/tables off a File Geodatabase. -
Layers that have
has
andAttachments supports
both asQuery Attachments true
now have the following features:- The
attachment
object is included for ArcGIS Enterprise feature services. This was already a feature for ArcGIS Online hosted feature services.Properties - A new fieldname property that can be used with the
query
operation'sAttachments attachments
parameter to limit results based on values in the attachment table.Definition Expression - Enterprise hosted feature services support both
keywords
andexif
(Info is
asEnabled true
). These columns are added automatically when publishing a new feature services with attachments, or enabling attachments on an existing layer. If upgrading from an earlier release, thekeywords
andexif
columns will not be available. However, they can be added using theInfo update
operation. Hosted feature services in ArcGIS Online already support attachment columns.Definition - New attachment properties,
id
andglobalid
, have been added for all feature service layers that support attachments, including ArcGIS Online hosted feature services. - A new
attachment
object lists information about the attachment fields, such as the type and length. TheFields attachment
Fields name
property can be matched to theattachment
Properties field
property. This information can be used to properly format queries and understand limits in the field length response. Only fields that match properties withName is
asEnabled true
will be listed inattachment
.Fields - Field names are now returned in addition to the field properties in the
query
operation response. If the field name and property name match, including case, only one value is returned in the response to represent both field and property. As best practice, it is best to go by the fieldname rather than the property when consuming this in an application.Attachments
- The
New in 10.8
-
reference
is added as a new property to represent the scale at which the size of a symbol and text for layer, if participates, is fixed.Scale This property is only available when
can
isScale Symbols true
.
New in 10.7.1
supported
now includesQuery Formats pbf
(protocol buffer), a compact binary encoding for geographic data.
New in 10.6.1
- New property named
archiving
is added.Info supports
property added inside theCount Distinct advanced
element.Query Capabilities - New property named
has
is added. This value is true when the service is published using ArcGIS Pro 2.2 or later, false otherwise.Metadata - If
has
is true, the layer / table supportsMetadata iteminfo
,thumbnail
, andmetadata
resources.
New in 10.6
-
New property named
display
is added; it returns the tile of the expression and an Arcade expression.Field Expression Info - When a layer is authored with
display
, its resources still reportExpression display
, which is a field picked from the Arcade expression or the default displayField, in case the expression does not have any field in it.Field
- When a layer is authored with
New in 10.5.1
return
is a parameter on the layer resource in which domain information includes only the domain name. The domain names can be matched with the full domain information as returned by the queryDomains operation. This approach is a more efficient way to work with domains, as it requires returning the full domain information only once instead of with each layer.Domain Names
New in 10.5
-
Layer reports its
source
, which can be different than what is in itsSpatial Reference extent
or its container map service's spatial reference. -
Added new flags:
supports
to indicate the layer supports datum transformation while query results get projected.Datum Transformation supports
indicates that the layer/table supports sql expressions in query operation'sSql Expression order
,By group
andBy Fields For Statistics out
.Statistics
-
New properties are added to report ranges and parameterized filters:
range
returns a list of available ranges including their names, current values, and full extent.Infos parameter
returns a list of available parameterized filters. These are preauthored filters to limit what you want to query or display. This is likeInfos layer
except that layerDefs requires you to pass in an entire sql where clause whereas for parameterized filters, you need to pass in the name-value pair.Defs
-
return
response includes updated full spatial extent when the layer is from an enterprise geodatabase.Updates
New in 10.3.1
supports
supports Query Layers, for example, such as layers / tables defined by a SQL query from a database, geodatabase archived layer, and so on.Statistics - Layers from file geodatabases support pagination (
supports
property). Other supported workspaces include Altibase, Hana, Oracle 12c (and later releases), PostgreSQL, SQLite, and SQL Server 2012 (and later releases). The following are not supported: DB2, Informix, Netezza, and Teradata.Pagination
New in 10.3
- All properties related to query are grouped inside
advanced
. See section below titled 'advancedQueryCapabilities' for more information.Query Capabilities supports
indicates whether the layer supports pagination in a query result.Pagination supports
indicates whether the service supports accepting and returning true curves as a segment of a polyline or polygon.True Curve supports
is split intoAdvanced Queries supports
andOrder By supports
.Distinct
New in 10.2
- A new property is reported to indicate whether the layer requires the use of standardized queries—
use
. A value ofStandardized Queries true
indicates the layer requires the use of standardized queries, a value offalse
indicates otherwise. Learn more about standardized queries. - Layer / table resources no longer report the existing definition expression set in the source map document.
New in 10.1 SP1
- If ownership-based access control is enabled on features,
ownership
property of a layer will include anBased Access Control For Features allow
property.Others To Query supports
is true if the layer/table supportsAdvanced Queries return
parameter in a query operation.Distinct Values
New in 10.1
- Layer resource supports a new parameter (
return
) that accepts a Boolean value. Pass this parameter to retrieve updatedUpdates time
for the layer.Extent - Layer now supports a new operation, generateRenderer. Use this to generate class breaks or a unique value renderer.
- A new property,
can
was added. Use this property on the Layer / Table resource to determine if a layer supports modifying its renderer and/or data source.Modify Layer - Layer resource contains
has
to indicate whether the layer has labels defined on it, andLabels can
if the text and symbols on the layer will change as the map scale varies.Scale Symbols - Layer resource contains
has
that returns a Boolean value. This value is true if the layer's data gets updated frequently. This property is independent ofLive Data has
that is available on the map service resource.Live Data - Layer resource contains
max
that represents the maximum number of records that can be returned byRecord Count query
,find
, andidentify operations
. - Layer resource contains
supports
that indicates whether the layer supports statistical functions in query operations andStatistics supports
to indicate if the layer supportsAdvanced Queries order
in a query operation.By Fields - Layer resource contains
supported
. This value indicates the supported output formats for a query operation.Query Formats - Layer resource contains
has
andZ has
to indicate whether the layer geometry contains z- or m-values, respectively.M - Layer resource now returns
role, cardinality, key
, andField, composite, relationship Table Id key
properties forField In Relationship Table relationships
. - Layer resource now returns two new properties:
effective
andMin Scale effective
. Effective minimum and maximum scale are calculated based on theMax Scale min
andScale max
values of the current layer and its ancestors. These represent the effective minimum and maximum scales at which the layer is visible.Scale - Layer resource includes
is
if the layer is versioned.Data Versioned
New in 10.0
- The layer/table resource represents a single layer/table in a map of a map service published by ArcGIS Server. It provides basic information about the layer/table such as its name, type, and fields. For layers, it provides additional information about the layer such as its parent and sublayers, minimum and maximum scales, extent, and copyright text. In 10.0 and later, it also provides information regarding the relationship of this layer/table with other layers/tables in the map service. A property to indicate whether the layer/table has attachments was also added at 10.0.
- Support for time-aware layers/tables was added at 10.0. If a layer/table supports querying and exporting maps based on time, the response will include a
time
property that includes information such as the start time field (or the time instance field), the end time field, the track ID field, the layer's time extent, and the suggested draw time interval.Info
Request parameters
Parameter | Details |
---|---|
| If value is Values: |
| If the value is Values: |
| The response format. The default response format is Values: |
advanced Query Capablities
-
advanced
capabilities are dependent on the support of these functionality by the layer/table's datasource. As a map service author, you do not have any control to turn them on or off except forQuery Capabilities use
.Standardized Queries For example:
- A layer referring to a shapefile will return false for
supports
,Statistics supports
,Order By supports
, and so on, and you will not be able to make use ofPagination out
,Statistics order
, orBy Fields result
andOffset result
, respectively, in aRecord Count query
operation request. - Whereas, a layer referring to a FeatureClass from an Enterprise Database will most likely return true for
supports
,Statistics supports
,Order By supports
, and so on.Pagination
- A layer referring to a shapefile will return false for
-
When
use
is true, you must conform aStandardized Queries where
clause and any expression you pass inorder
,By Fields out
, and so on to ArcGIS Server standardizedQueries specifications. When it is false, you can pass in SQL expression that conforms to the source database. As an admin, you can disable StandardizedQueries for all services running on a server instance.Statistics -
supports
indicates that you can pass values in aStatistics query
operation'sout
parameter to get some statistical results for that layer/table.Statistics -
supports
indicates that you can get a query result sorted by ascending or descending order based on values from one or multiple fields or expression (whenOrder By supports
is true) by passing in values toSql Expression order
.By Fields -
supports
indicates that you can make a query to retrieve unique values from a field or fields specified in theDistinct out
.Fields -
supports
indicates whether the layer supports paging through query result. When it is supported, you can usePagination result
orOffset result
to fetch, for example, the first 10 records and then make subsequent request to fetch next the 10 records. To support pagination, a supported workspace must be used: Altibase, Hana, Oracle 12c (and later releases), PostgreSQL, SQLite, and SQL Server 2012 (and later releases). The following are not supported: file geodatabase, DB2, Informix, Netezza, and Teradata.Record Count -
supports
indicates whether the service supports accepting and returning true curves as a segment of a polyline or polygon.True Curve -
supports
indicates pass true toReturning Query Extent return
to return an extent covering all features in a query result, instead of returning features.Extent Only -
When
supports
is true, you can pass include a bufferQuery With Distance distance
in a query request. -
supports
indicates that the layer/table supports sql expressions in query operation'sSql Expression order
,By group
andBy Fields For Statistics out
.Statistics
Example usage
Example one
The following is a sample request URL used to access a specific layer (id 3) in the Census map service:
https://sampleserver6.arcgisonline.com/arcgis/rest/services/Census/MapServer/3
Example two
The following is a sample request URL used to access an individual layer/table resource, which demonstrates using the return
parameter to return updated temporal information:
JSON Response syntax
Below is an example of the JSON response syntax:
{
"currentVersion": <currentVersion>,
"id": <layerOrTableId>,
"name": "<layerOrTableName>",
"type": "<layerOrTableType>", //for tables, the type will be "Table"
"description": "<description>",
"definitionExpression": "<definitionExpression>",
//properties specific to layers only
"geometryType": "<geometryType>",
"hasZ": <true|false>,
"hasM": <true|false>,
"copyrightText": "<copyrightText>",
"parentLayer": {
"id": <parentLayerId>,
"name": "<parentLayerName>"
},
"subLayers": [
{
"id": <subLayerId1>,
"name": "<subLayerName1>"
},
{
"id": <subLayerId2>,
"name": "<subLayerName2>"
}
],
"minScale": <minScale>,
"maxScale": <maxScale>,
"effectiveMinScale": <effectiveMinScale>,
"effectiveMaxScale": <effectiveMaxScale>,
"defaultVisibility": <true | false>,
"extent": <envelope>,
//from 10 onward - if the layer / table supports querying and exporting maps based on time
"timeInfo": {
"startTimeField": "<startTimeFieldName>",
"endTimeField": "<endTimeFieldName>",
"trackIdField": "<trackIdFieldName>",
"timeExtent": [<startTime>, <endTime>],
"timeReference": {
"timeZone": "<timeZone>",
"respectsDaylightSaving": <true | false>
},
"timeInterval": <timeInterval>,
"timeIntervalUnits": "<timeIntervalUnits>",
//the default time-related export options for this layer
"exportOptions": {
//If true, use the time extent specified by the time parameter
"useTime": < true | false >,
//If true, draw all the features from the beginning of time for that data
"timeDataCumulative": < true | false >,
//Time offset for this layer so that it can be overlaid on the top of a previous or future time period
"timeOffset": <timeOffset1>,
"timeOffsetUnits": "<esriTimeUnitsCenturies | esriTimeUnitsDays | esriTimeUnitsDecades |
esriTimeUnitsHours | esriTimeUnitsMilliseconds | esriTimeUnitsMinutes |
esriTimeUnitsMonths | esriTimeUnitsSeconds | esriTimeUnitsWeeks | esriTimeUnitsYears |
esriTimeUnitsUnknown>"
}
"hasLiveData": <true | false>,
},
//for feature layers only
"drawingInfo": {
"renderer": <renderer>,
"transparency": <transparency>,
"labelingInfo": <labelingInfo>
},
"orderBy": [ //Added at 11.1
{
"field":"<fieldName>",
"order": "<asc | desc>"
}
],
"featureReduction": { //Added at 11.1
"type": "cluster",
"clusterRadius": double,
"clusterMinSize": double,
"clusterMaxSize": double,
"showLabels": <true | false>,
"drawingInfo": {
"labelingInfo": <labelingInfo>
},
"visibilityInfo": {
"type": "scale",
"maxScale": double
}
},
//indicates whether the layer / table has attachments or not
"hasAttachments": <true | false>,
//indicates whether the layer / table has htmlPopups
"htmlPopupType": "<esriServerHTMLPopupTypeNone | esriServerHTMLPopupTypeAsURL | esriServerHTMLPopupTypeAsHTMLText>",
//layer / table field information
"displayField": "<displayFieldName>",
//the typeIdField is new at 10.0
"typeIdField": "<typeIFieldName>",
//fields of type (String, Date, GlobalID, GUID and XML) have an additional length property
//the field domains are also included
"fields": [
{
"name": "<fieldName1>",
"type": "<fieldType1>",
"alias": "<fieldAlias1>",
"length": "<length1>",
"domain": <domain1>
},
{
"name": "<fieldName2>",
"type": "<fieldType2>",
"alias": "<fieldAlias2>",
"length": "<length2>",
"domain": <domain2>
}
],
//if the layer has sub-types, they'll be included
"types": [
{
"id": <typeId1>,
"name": "<typeName1>",
"domains": {
"<domainField11>": <domain11>,
"<domainField12>": <domain12>
}
},
{
"id": <typeId2>,
"name": "<typeName2>",
"domains": {
"<domainField11>": <domain21>,
"<domainField12>": <domain22>
}
}
],
//if the layer / table participates in relationships with other layers / tables
"relationships": [
{
"id": <relationshipId1>,
"name": "<relationshipName1>",
"relatedTableId": <relatedTableId1>,
"role": "<esriRelRoleOrigin>|<esriRelRoleDestination>";,//Added at 10.1
"cardinality": "<esriRelCardinalityOneToOne>|<esriRelCardinalityOneToMany>|<esriRelCardinalityManyToMany>";,//Added at 10.1
"keyField": "<keyFieldName2>",//Added at 10.1
"composite": <true>|<false>,//Added at 10.1
"relationshipTableId": <attributedRelationshipClassTableId>, //Added in 10.1. Returned only for attributed relationships
"keyFieldInRelationshipTable": "<key field in AttributedRelationshipClass table that matches keyField>" //Added in 10.1. Returned only for attributed relationships
},
{
"id": <relationshipId2>,
"name": "<relationshipName2>",
"relatedTableId": <relatedTableId2>,
"role": "<esriRelRoleOrigin>|<esriRelRoleDestination>";,//Added at 10.1
"cardinality": "<esriRelCardinalityOneToOne>|<esriRelCardinalityOneToMany>|<esriRelCardinalityManyToMany>";,//Added at 10.1
"keyField": "<keyFieldName2>",//Added at 10.1
"composite": <true>|<false>,//Added at 10.1
"relationshipTableId": <attributedRelationshipClassTableId>, //Added in 10.1. Returned only for attributed relationships
"keyFieldInRelationshipTable": "<key field in AttributedRelationshipClass table that matches keyField>" //Added in 10.1. Returned only for attributed relationships
}
],
"maxRecordCount": <recordCount>,
//if the layer / table supports modifying its renderer, data source, or join information.
"canModifyLayer": <true | false>,
//if the layer / table supports statistical functions in query operation.
"supportsStatistics": <true | false>,
//if the layer / table supports orderBy parameter in query operation.
"supportsAdvancedQueries": <true | false>,
//if the layer has labels defined on it.
"hasLabels": <true | false>,
//if the layer renders its symbols based on scale.
"canScaleSymbols": <true | false>,
//comma separated list of supported capabilities - e.g. "Map,Query,Data"
"capabilities": "<capabilities>",
//comma separated list of supported query output formats - e.g. "JSON"
"supportedQueryFormats": "<supported query output formats>",
//true if the layer is versioned.
"isDataVersioned": <true | false>,
"ownershipBasedAccessControlForFeatures": {
"allowOthersToQuery": <true | false>
},
"supportedSpatialRelationships": [
"esriSpatialRelIntersects",
"esriSpatialRelContains",
"esriSpatialRelCrosses",
"esriSpatialRelEnvelopeIntersects",
"esriSpatialRelIndexIntersects",
"esriSpatialRelOverlaps",
"esriSpatialRelTouches",
"esriSpatialRelWithin",
"esriSpatialRelRelation"
],
//container for below properties.
"advancedQueryCapabilities": {
"useStandardizedQueries": <true | false>,
"supportsStatistics": <true | false>,
"supportsOrderBy": true,
"supportsDistinct": true,
"supportsPagination": false,
"supportsTrueCurve": true
}
}
JSON Response syntax
When return
is true
:
{
"id": <layer id>,
"timeExtent": [
<start time>,
<end time>
],
"fullExtent": {
"xmin": <xmin>,
"ymin": <ymin>,
"xmax": <xmax>,
"ymax": <ymax>,
"spatialReference": <spatialReference>
}
}
JSON Response example
{
"currentVersion": 11.1,
"id": 0,
"name": "BuildingPermits",
"type": "Feature Layer",
"description": "",
"geometryType": "esriGeometryPoint",
"copyrightText": "",
"parentLayer": null,
"subLayers": [],
"minScale": 0,
"maxScale": 0,
"drawingInfo": {
"renderer": {
"type": "simple",
"symbol": {
"type": "esriSMS",
"style": "esriSMSCircle",
"color": [
135,
99,
0,
255
],
"size": 4,
"angle": 0,
"xoffset": 0,
"yoffset": 0,
"outline": {
"color": [
0,
0,
0,
255
],
"width": 1
}
},
"label": "",
"description": ""
},
"transparency": 0,
"labelingInfo": null
},
"featureReduction": {
"type": "cluster",
"clusterRadius": double,
"clusterMinSize": double,
"clusterMaxSize": double,
"showLabels": true | false,
"drawingInfo": {
"labelingInfo": <labelingInfo>
},
"visibilityInfo": {
"type": "scale",
"maxScale": double
}
},
"defaultVisibility": true,
"extent": {
"xmin": -1.366377185708964E7,
"ymin": 5699225.41829418,
"xmax": -1.3663618388213603E7,
"ymax": 5699411.767458527,
"spatialReference": {
"wkid": 102100,
"latestWkid": 3857
}
},
"hasAttachments": false,
"htmlPopupType": "esriServerHTMLPopupTypeNone",
"displayField": "CITYNAME",
"typeIdField": null,
"fields": [
{
"name": "RECORD",
"type": "esriFieldTypeDouble",
"alias": "RECORD",
"domain": null
},
{
"name": "PERMITDATE",
"type": "esriFieldTypeDate",
"alias": "PERMITDATE",
"length": 36,
"domain": null
},
{
"name": "PERMIT_NO",
"type": "esriFieldTypeString",
"alias": "PERMIT_NO",
"length": 15,
"domain": null
},
{
"name": "CITYNAME",
"type": "esriFieldTypeString",
"alias": "CITYNAME",
"length": 17,
"domain": null
},
{
"name": "VALUE",
"type": "esriFieldTypeDouble",
"alias": "VALUE",
"domain": null
},
{
"name": "SQFT",
"type": "esriFieldTypeDouble",
"alias": "SQFT",
"domain": null
},
{
"name": "TLID",
"type": "esriFieldTypeString",
"alias": "TLID",
"length": 17,
"domain": null
},
{
"name": "SUBDIV",
"type": "esriFieldTypeString",
"alias": "SUBDIV",
"length": 63,
"domain": null
},
{
"name": "LOT",
"type": "esriFieldTypeString",
"alias": "LOT",
"length": 11,
"domain": null
},
{
"name": "BLOCK",
"type": "esriFieldTypeString",
"alias": "BLOCK",
"length": 7,
"domain": null
},
{
"name": "WORK_DESC",
"type": "esriFieldTypeString",
"alias": "WORK_DESC",
"length": 111,
"domain": null
},
{
"name": "CONST_TYPE",
"type": "esriFieldTypeString",
"alias": "CONST_TYPE",
"length": 13,
"domain": null
},
{
"name": "STRUCT_TYP",
"type": "esriFieldTypeString",
"alias": "STRUCT_TYP",
"length": 12,
"domain": null
},
{
"name": "NO_UNITS",
"type": "esriFieldTypeDouble",
"alias": "NO_UNITS",
"domain": null
},
{
"name": "ADDRESS",
"type": "esriFieldTypeString",
"alias": "ADDRESS",
"length": 37,
"domain": null
},
{
"name": "X_COORD",
"type": "esriFieldTypeDouble",
"alias": "X_COORD",
"domain": null
},
{
"name": "Y_COORD",
"type": "esriFieldTypeDouble",
"alias": "Y_COORD",
"domain": null
},
{
"name": "CODE",
"type": "esriFieldTypeString",
"alias": "CODE",
"length": 13,
"domain": null
},
{
"name": "RuleID",
"type": "esriFieldTypeInteger",
"alias": "RuleID",
"domain": null
},
{
"name": "OwnerName",
"type": "esriFieldTypeString",
"alias": "OwnerName",
"length": 50,
"domain": null
},
{
"name": "OBJECTID",
"type": "esriFieldTypeOID",
"alias": "OBJECTID",
"domain": null
},
{
"name": "Permit_Status",
"type": "esriFieldTypeString",
"alias": "Permit_Status",
"length": 10,
"domain": null
}
],
"relationships": [
{
"id": 0,
"name": "for taslot",
"relatedTableId": 2,
"role": "esriRelRoleDestination",
"keyField": "TLID",
"cardinality": "esriRelCardinalityOneToMany",
"composite": false
},
{
"id": 1,
"name": "owns TaxLots",
"relatedTableId": 2,
"role": "esriRelRoleDestination",
"keyField": "OwnerName",
"cardinality": "esriRelCardinalityOneToMany",
"composite": false
}
],
"canModifyLayer": false,
"canScaleSymbols": false,
"hasLabels": false,
"capabilities": "Map,Query,Data",
"maxRecordCount": 1000,
"supportsStatistics": true,
"supportsAdvancedQueries": true,
"supportedQueryFormats": "JSON, geoJSON, PBF",
"isDataVersioned": true,
"ownershipBasedAccessControlForFeatures": {"allowOthersToQuery": true},
"useStandardizedQueries": true,
"supportedSpatialRelationships": [
"esriSpatialRelIntersects",
"esriSpatialRelContains",
"esriSpatialRelCrosses",
"esriSpatialRelEnvelopeIntersects",
"esriSpatialRelIndexIntersects",
"esriSpatialRelOverlaps",
"esriSpatialRelTouches",
"esriSpatialRelWithin",
"esriSpatialRelRelation"
],
"advancedQueryCapabilities": {
"useStandardizedQueries": true,
"supportsStatistics": true,
"supportsOrderBy": true,
"supportsDistinct": true,
"supportsPagination": false,
"supportsTrueCurve": true,
"supportsReturningQueryExtent": true,
"supportsQueryWithDistance": true
},
"dateFieldsTimeReference": null
}