View In:   ArcGIS Online Map Viewer

Name: VFCC_FacilityMaps

Display Field: name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This dataset contains address points from the Countywide Address Management System, a collaborative program between the County’s Registrar/Recorder, Chief Information Officer, Public Works Department, Department of Regional Planning, and many local cities to manage addresses and street centerlines for the purposes of geocoding and cartography. More information about this layer can be found on the </SPAN><A href="http://egis3.lacounty.gov/dataportal/2012/06/19/la-county-address-points/"><SPAN>eGIS Data Repository data layer page</SPAN></A><SPAN>.</SPAN></P><P><SPAN STYLE="font-weight:bold;">What this data is (and isn’t)</SPAN></P><P><SPAN /><SPAN>This dataset contains the best available information, with close to 3 million primary and secondary addresses in the County of Los Angeles. It does NOT include information about every unit, suite, building, and sub-address. With probably over 7 million addresses, we have a ways to go.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Description</SPAN></P><P><SPAN>This dataset includes over 2.9 million individual points for addresses in the County. Data has been compiled from best available sources, including city databases, LA County Assessor parcels, and the County’s House Numbering maps. Please see the Source field for information.</SPAN></P><P><SPAN>Street Name information has been split into multiple fields to support the County’s specifically designed geocoders – please see the entry on LA County Specific Locators and Matching rules for more information.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Multi-address Parcels</SPAN></P><P><SPAN>Some of our data sources (LA City, LA County, for example) have mapped each individual address in their city. These may also show unit information for an address point. A property with multiple addresses will show a point for each address. For some cities where this has not happened, the data source is the Assessor, where the primary address of the property may be the only address shown. We invite cities and sources with more detailed information to join the CAMS consortium to continue to improve the data.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Legal vs. Postal Cities</SPAN></P><P><SPAN>Many users confuse the name the Post Office delivers main to (e.g. Van Nuys, Hollywood) as a legal city (in this case Los Angeles), when they are a postal city. The County contains 88 legal cities, and over 400 postal names that are tied to the zipcodes. To support useability and geocoding, we have attached the first 3 postal cities to each address, based upon its zipcocode.</SPAN></P></DIV></DIV></DIV>

Service Item Id: c486fe8315ae42c39f2ec184c336c445

Copyright Text: Mark Greninger Geographic Information Officer County of Los Angeles Internal Services Department 350 South Figueroa St Suite 188 Los Angeles, CA 90071 mgreninger@isd.lacounty.gov (213) 253-5624

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 180000.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

Extent:

XMin: -1.315723151143273E7
YMin: 4047682.505704403
XMax: -1.314597469876552E7
YMax: 4053086.518439725
Spatial Reference: 102100  (3857)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: false
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: false
Supports Binning LOD: true
Supports Query With LOD Spatial Reference: true
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: true

HasM: true

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields:

• objectid ( nullable: false, defaultValue: null, editable: false, length: 4, type: esriFieldTypeOID, modelName: OBJECTID, alias: OBJECTID )
• number ( modelName: Number, nullable: true, editable: true, defaultValue: null, alias: Number, type: esriFieldTypeInteger )
• predir ( modelName: PreDir, nullable: true, editable: true, defaultValue: null, length: 10, alias: PreDir, type: esriFieldTypeString )
• starticle ( modelName: StArticle, nullable: true, editable: true, defaultValue: null, length: 10, alias: StArticle, type: esriFieldTypeString )
• streetname ( modelName: StreetName, nullable: true, editable: true, defaultValue: null, length: 50, alias: StreetName, type: esriFieldTypeString )
• posttype ( modelName: PostType, nullable: true, editable: true, defaultValue: null, length: 20, alias: PostType, type: esriFieldTypeString )
• zipcode ( modelName: ZipCode, nullable: true, editable: true, defaultValue: null, length: 5, alias: ZipCode, type: esriFieldTypeString )
• legalcomm ( modelName: LegalComm, nullable: true, editable: true, defaultValue: null, length: 30, alias: LegalComm, type: esriFieldTypeString )
• fulladdress ( modelName: FullAddress, nullable: true, editable: true, defaultValue: null, length: 75, alias: FullAddress, type: esriFieldTypeString )
• maps ( modelName: Maps, nullable: true, editable: true, defaultValue: 0, alias: Maps, type: esriFieldTypeSmallInteger )
• name ( modelName: name, nullable: true, editable: true, defaultValue: null, length: 50, alias: Name, type: esriFieldTypeString )
• globalid ( nullable: false, editable: false, defaultValue: null, length: 38, type: esriFieldTypeGlobalID, modelName: globalid, alias: globalid )

Templates:

• Name: VFCC_FacilityMaps
  Description:
  Prototype:
  Drawing Tool: esriFeatureEditToolPoint

Capabilities: Query

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: true

Supports ApplyEdits By Upload Id: true

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:   Field Groups   Contingent Values

Supported Operations:   Query   Query Attachments   Query Analytic   Query Top Features   Query Bins   Append   Validate SQL   Generate Renderer   Return Updates   Metadata   Update Metadata