Parent Layer: Municipal Areas

Name: BM_City_Limits

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The LADOTD publish date for this base map feature was 2/3/2016. This feature only includes incorporated municipalities along with the two military features for Fort Polk. Census Designated Places have been removed.The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2015, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. LA DOTD REVISION NOTES: The initial feature was a shapefile downloaded directly from the US Census. Then, LA DOTD Mapping/GIS Section in Baton Rouge , LA. made the below revisions to this Census 2015 Lousiana Places data in January 2016. Only the revised records (below) that note that there are attachments available have attachments. To view available feature attachments open attribute table -> r-click in grey box to left side of table -> choose "Open Attachment Manager" -> in the Attachment Manager, highlight document then click "Open". Also, the HTML Pop-Up identify tool can be used to access available attachments. Any questions should be addressed to the DOTD Mapping Unit.LA DOTD REVISIONS: The following listed municipalities were edited and published February 3, 2016.Abbevillefeature from City of Abbeville engineering contractor Sellers and Associates recieved 09/17/2015 & attached legal description, Alexandriafeature from Rapides Area Planning Commission RAPC recieved recieved 9/17/2015, Bakerfeature from East Baton Rouge City Parish Planning Commission EBR CPPC recieved 9/17/2015 & attached legal description , Ballfeature from Rapides Area Palnning Commission RAPC recieved recieved 9/17/2015, Baton Rouge feature from East Baton Rouge City Parish Planning Commission EBR CPPC recieved 9/17/2015, Bentonfeature from Bossier Parish Government - 911 Communications recieved 9/30/2015 & attched legal description, Bossier City feature from City of Bossier City Engineering Department received 9/21/2015 & attached legal description, Boycefeature from Rapides Area Palnning Commission RAPC recieved recieved 9/17/2015, Broussardfeature from Lafayette Consolidated Government recieved 9/22/2015 & attached legal description, Carencrofeature from Lafayette Consolidated Government recieved 9/22/2015, Centralfeature from City of Central Municipal Services recieved 9/21/2015 & attached legal description, Choudrantfeature from Lincoln Parish Government, Grand Isle attachment of rev 1967 DOTD map of the town of Grand Isle & 1959 legal description recieved from Jefferson Parish via Jefferson Parish Attorney's 0ffice, Gretnafeature from Jefferson Parish recieved 9/17/2015; DOTD closed gaps between adjacent municipal polygons, Haughtonfeature from Bossier Parish Government - 911 Communications recieved 9/30/2015, Houmafeature from Terrebonne Parish Consolidated Government recieved 9/18/2015 & attached legal description, Kenner feature from Jefferson Parish recieved 9/28/2015 & attached 1913 Legal description with accompanying (2) maps, 1994 & 2012 annexations via Kenner City Attorney's Office, Lafayettefeature from Lafayette Consolidated Government recieved 1/6/2016 & attached legal description, Jean Lafitte feature from Jefferson Parish recieved 9/17/2015 (DOTD edited boundary with adjacent CDP polygons), Lake Charles feature from City of Lake Charles Public Works recieved 9/29/2015 & attached legal description; DOTD adjusted adjacent West Lake polygon boundary to close gaps. Mandevillefeature from Mandeville Planning and Development & attached legal description, annexations, and map, New Orleans feature clip of parish boundary from DOTD BM_Parishes layer as of 01/12/2016 & attached legal description; DOTD closed gaps with adjacent municipal polygons, Pinevillefeature from Rapides Area Planning Commission recieved 9/30/2015; DOTD closed gap bewteen adjacent Shreveport polygon, Roselandfeature from Tangipahoa Parish recieved 9/17/2015, Rustonfeature from Lincoln Parish Government recieved 9/22/2015 & attached last annexation, Scottfeature from Lafayette Consolidated Government recieved 9/22/2015 & attached last annexation description 9/3/2015; DOTD closed gap between adjacent municipal polygon, Shreveportfeature from Shreveport Engineering and Environmental Services recieved 9/23/2015 (feature up to date through June 20, 2015) & attached legal description for boundary as of December 31, 2014; DOTD closed gaps bewteen adjacent municipal polygons, Slidellfeature from City of Slidell - Engineering recieved 1/8/2016 & attached last annexation dated 11/10/2015, Thibodauxfeature from Thibodaux Public Works recieved 9/28/2015 & attached legal description dated 2/2008, Youngsvillefeature from Lafayette Consolidated Government recieved 9/22/2015 & attached legal description and map dated 3/24/2015; DOTD closed gaps between adjacent municipal polygons, Zacharyfeature from East Baton Rouge City Parish Planning Commission EBR CPPC recieved 9/17/2015; DOTD closed gaps between adjacent municipal polygons.

Service Item Id: 4b48e96e15f04336aa215d4543edbe75

Copyright Text: Louisiana Department of Transportation and Development downloaded the source data for production of this data set from US Cenus. Credit should be given to US Census based on their request for credit. Their metadata is included here. This feature class was developed using original linework that was manually digitized using USGS Quadrangle Maps along with legal parish boundary descriptions. Anomalies will be noted between these data compiled by LADOTD and boundaries that are depicted in other reference data sets (e.g. USGS DRGs). The depiction of boundaries in this data set has been heavily researched and is believed to be a better representation of the actual boundary than USGS sources.

Default Visibility: true

MaxRecordCount: 10000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 250000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.0467223066833733E7
YMin: 3395197.2641727366
XMax: -9965551.912301183
YMax: 3898319.153794666
Spatial Reference: 102100  (3857)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [225, 225, 225, 153]
Outline:
Style: esriSLSDashDotDot
Color: [0, 0, 0, 153]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [NAME]
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: baseline
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 8
Font Family: Arial
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 0.0
Max. Scale: 750000.0
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [NAME]
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: baseline
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 7
Font Family: Arial
Font Style: normal
Font Weight: normal
Font Decoration: none

Min. Scale: 750000.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: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• STATEFP ( type: esriFieldTypeString, alias: STATEFP, length: 2 )
• PLACEFP ( type: esriFieldTypeString, alias: PLACEFP, length: 5 )
• PLACENS ( type: esriFieldTypeString, alias: PLACENS, length: 8 )
• GEOID ( type: esriFieldTypeString, alias: GEOID, length: 7 )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 100 )
• NAMELSAD ( type: esriFieldTypeString, alias: NAMELSAD, length: 100 )
• LSAD ( type: esriFieldTypeString, alias: LSAD, length: 2 )
• CLASSFP ( type: esriFieldTypeString, alias: CLASSFP, length: 2 )
• PCICBSA ( type: esriFieldTypeString, alias: PCICBSA, length: 1 )
• PCINECTA ( type: esriFieldTypeString, alias: PCINECTA, length: 1 )
• MTFCC ( type: esriFieldTypeString, alias: MTFCC, length: 5 )
• FUNCSTAT ( type: esriFieldTypeString, alias: FUNCSTAT, length: 1 )
• ALAND ( type: esriFieldTypeDouble, alias: ALAND )
• AWATER ( type: esriFieldTypeDouble, alias: AWATER )
• INTPTLAT ( type: esriFieldTypeString, alias: INTPTLAT, length: 11 )
• INTPTLON ( type: esriFieldTypeString, alias: INTPTLON, length: 12 )
• Source ( type: esriFieldTypeString, alias: Source, length: 150 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata