View In:   ArcGIS Online Map Viewer

Name: Municipality

Display Field: POLYGON_NM

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>City boundaries.</SPAN></P><P><SPAN>NAVTEQ's Administrative Area Boundaries. These layers contain the boundaries that divide countries into administrative areas such as country, state, county, city, or settlement. These designations vary on a country by country basis. (In the US for example, the AdminBndy2 layer contains State boundaries, the AdminBndy3 layer contains County boundaries, and the AdminBndy4 layer contains City boundaries.) See Administrative Level Coding and Boundary Features in the NAVSTREETS manual for a list of the administrative area types by country. This layer is used for map visualisation. Note that an Administrative Area Boundary is represented by multiple region objects when it has names in multiple languages. This NAVTEQ dataset is released on a Quarterly basis. This dataset is a subset of the full NAVTEQ NAVSTREETS database.</SPAN></P><P><SPAN>AdminBndy4 - Lee County city boundaries were updated by SFWMD using the boundaries received from the County. The new boundaries include addition of the Village of Estero. - 20150817</SPAN></P><P><SPAN>With the most accurate geometry, the highest number of attributes, and the most complete detailed coverage, NAVTEQ data is the ideal resource for Fleet applications that offer route planning and optimization, and GIS geocoding and other applications that require superior accuracy, and location-enabled services, from Personal Navigation Devices (PNDs) and mobile social networking, to location-enabled entertainment, leisure, and business applications. Products, applications, and services that rely on digital mapping data can ensure superior performance and accuracy by using NAVSTREETS. NAVTEQ data drives most in-vehicle navigation systems around the world, the top routing Web sites, and the leading brands of wireless devices. Designed for rapid display and retrieval of attributes for routing, NAVTEQ data additionally provides support for express mail services, emergency and government routing plans, efficient field service management, wireless Location Based Services (LBS), and delivery of real-time traffic information.</SPAN></P></DIV></DIV></DIV>

Service Item Id: a1bc0260b77b41a1aba2c8875f312d78

Copyright Text: NAVTEQ incorporates and enhances data from a number of local governments, utility companies, other public agencies, and commercial mapping agencies in building its final products.

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 4622325.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:

XMin: -1318808.2035796698
YMin: 77344.2840033248
XMax: 972412.108983662
YMax: 2478294.2416082397
Spatial Reference: 2881  (2881)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [240, 222, 224, 255]
Outline:
Style: esriSLSSolid
Color: [115, 0, 0, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 26
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [POLYGON_NM]
Use Coded Values: true
Symbol:
Color: [115, 38, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: center
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 8
Font Family: Arial
Font Style: italic
Font Weight: bold
Font Decoration: none

Min. Scale: 144449.0
Max. Scale: 0.0

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: true
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: false
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field:

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )
• POLYGON_ID ( type: esriFieldTypeInteger, alias: POLYGON_ID, editable: true, nullable: true, defaultValue: null, modelName: POLYGON_ID )
• AREA_ID ( type: esriFieldTypeInteger, alias: AREA_ID, editable: true, nullable: true, defaultValue: null, modelName: AREA_ID )
• NM_AREA_ID ( type: esriFieldTypeSmallInteger, alias: NM_AREA_ID, editable: true, nullable: true, defaultValue: null, modelName: NM_AREA_ID )
• POLYGON_NM ( type: esriFieldTypeString, alias: POLYGON_NM, editable: true, nullable: true, length: 105, defaultValue: null, modelName: POLYGON_NM )
• NM_LANGCD ( type: esriFieldTypeString, alias: NM_LANGCD, editable: true, nullable: true, length: 3, defaultValue: null, modelName: NM_LANGCD )
• POLY_NM_TR ( type: esriFieldTypeString, alias: POLY_NM_TR, editable: true, nullable: true, length: 250, defaultValue: null, modelName: POLY_NM_TR )
• TRANS_TYPE ( type: esriFieldTypeString, alias: TRANS_TYPE, editable: true, nullable: true, length: 3, defaultValue: null, modelName: TRANS_TYPE )
• FEAT_TYPE ( type: esriFieldTypeString, alias: FEAT_TYPE, editable: true, nullable: true, length: 40, defaultValue: null, modelName: FEAT_TYPE )
• DETAIL_CTY ( type: esriFieldTypeString, alias: DETAIL_CTY, editable: true, nullable: true, length: 1, defaultValue: null, modelName: DETAIL_CTY )
• FEAT_COD ( type: esriFieldTypeInteger, alias: FEAT_COD, editable: true, nullable: true, defaultValue: null, modelName: FEAT_COD )
• COVERIND ( type: esriFieldTypeString, alias: COVERIND, editable: true, nullable: true, length: 2, defaultValue: null, modelName: COVERIND )
• CLAIMED_BY ( type: esriFieldTypeString, alias: CLAIMED_BY, editable: true, nullable: true, length: 3, defaultValue: null, modelName: CLAIMED_BY )
• CONTROL_BY ( type: esriFieldTypeString, alias: CONTROL_BY, editable: true, nullable: true, length: 3, defaultValue: null, modelName: CONTROL_BY )
• Shape__Area ( type: esriFieldTypeDouble, alias: SHAPE.STArea(), editable: false, nullable: true, defaultValue: null, modelName: Shape.STArea(), required: true )
• Shape__Length ( type: esriFieldTypeDouble, alias: SHAPE.STLength(), editable: false, nullable: true, defaultValue: null, modelName: Shape.STLength(), required: true )

Templates:

• Name: Municipality
  Description:
  Prototype:
  CONTROL_BY: null
  POLYGON_ID: null
  AREA_ID: null
  NM_AREA_ID: null
  POLYGON_NM: null
  NM_LANGCD: null
  POLY_NM_TR: null
  TRANS_TYPE: null
  FEAT_TYPE: null
  DETAIL_CTY: null
  FEAT_COD: null
  COVERIND: null
  CLAIMED_BY: null
  
  Drawing Tool: esriFeatureEditToolPolygon

Capabilities: Query,Extract

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:   Field Groups   Contingent Values

Supported Operations:   Query   Query Analytic   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata