ArcGIS REST Services Directory Login | Get Token
Home > services > HubSiteData (MapServer) > Building Entrances Help | API Reference
JSON

Layer: Building Entrances (ID: 6)

Name: Building Entrances

Display Field: Name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: This layer includes entrances to buildings and other structures. Each point is a single door. The primary focus of edits to-date have been on the ground floor, although the data model accommodates upper floors, and some of those entrances have been mapped. Entry points are also shown at elevator doors, Parking Garage pedestrian access points, parking Garage Vehicle Entrances, perimeter gates into building courtyards, and at portals into performance and sports venues.FieldsOBJECTID* System maintained field.EntranceID: Unique identifier for each entrance.IsOnAccessibilityMap: Partially populated with codes 1, 2, or 3, but it is unclear at this point what the codes correspond to, so this field is not currently being populated. Type: Provides attributes for level of use of a door. Used for symbolizing features on maps. Populated by CVD: dmnEntranceType1 Primary Pedestrian Access2 Secondary Pedestrian Access3 Limited Pedestrian Access4 Unknown5 Inactive6 Main Pedestrian AccessFollowing are guidelines for categorizing doors according to these categories of significance:Main Pedestrian Access: This code applies to what would be considered the building’s architectural entry. Architectural queues could be a grand staircase, the front lobby entrance, columns, or anything that indicates the “front” of the building. A building should have just one. Note that if there were two adjacent doors at a single main entry, both would be coded as “Main”. Primary Pedestrian Access: This code applies to what would be considered the building’s main entry. In some cases, a building will have more than one main entry, but often there is just one. Note that if there were two adjacent doors at a single main entry, both would be coded as “Primary”. Secondary Pedestrian Access: This code applies to doors that are open and used throughout a regular day, but which lead to secondary spaces, do now have architectural or landscape queues that give them prominence.Limited Pedestrian Access: This code applies to doors that are often locked during the day (or only can be exited from in an emergency), or which are used mainly for utilitarian purposes such as deliveries, maintenance, etc.Inactive: This code applies to existing doors that are closed indefinitely.SymbolDirection: Conveys the direction one is facing when entering a door. This is used for symbolizing maps with arrows pointing into the building at entrance points.Populated by CVD: dmnSymbolDir 1 N2 NE3 E4 SE5 S6 SW7 W8 NWAssociatedSpaceNum: This field is used to connect BuildingEntrance points with building polygons via their SpaceNum value.FloorNumEntersOn: Represents the number of the floor the door enters onto, with the floor number determined per the floor number as assigned by REA (shown on keyplan). There may be a second field created for 3D purposes in the future, which is keyed to the “level” coding system of G1, G2, B1, etc.Shape* Default system-maintained field listing the geometry type associated with the feature class.BuildingAddressDoor: May be used at some point put is not currently being populated.SingleDoorSymbol: Coded as yes/no to denote which of the door points will be used when we want to show only one door point at a particular entry (which may actually have many individual doors). If the door has an Auto Opener (see field description below), use the door with the Auto Opener as the one to code as the “SingleDoorSymbol”.Populated with CVD: dmnYesNo 1 Yes2 NoEntersAtGrade: This field indicates if the door leads into the building from the ground level. Note that the proper code is “yes” if any entrance can be accessed from walkways leading from open space to the building. For buildings that are on sloping ground, this may mean that there are grade entrances on several sides of the building, which enter onto different floors. They are all still considered to “enter at grade”.Entrances that would not be considered to “enter at grade” are ones where someone must go up an exterior stairwell to get to the entry (ex: second floor of Yavapai), or where the entry is only accessible from an upper or lower level walk that itself is only accessible from within the building (ex: Harvill).Populated with CVD: dmnYesNo 1 Yes2 NoHasAutoOpener: Indicates if the building entrance has an automatic opener.Populated with CVD: dmnYesNo 1 Yes2 NoHasKeyCard: Indicates whether the building entrance is locked with a key card reader.Populated with CVD: dmnYesNo 1 Yes2 NoAccessible: Codes whether or not the door is considered accessible. At this point, the definition of “accessible” means that there is a wheelchair accessible ramp leading to the door. This can be used to filter entrance points that are not relevant to the map, such as utility entrances.Populated with CVD: dmnYesNo 1 Yes2 NoInaccessibleFoyer: This indicates whether a door enters onto an inaccessible foyer. Some doors are accessible from the outside, and would be coded as such in the “Accessible” field, but do not actually provide access to the building due to an inaccessible foyer. A foyer that has an elevator leading to an interior floor would be considered accessible.Populated with CVD: dmnYesNo 1 Yes2 NoCategory: This field contains the type of building entrance.Populated with CVD: EntranceCategory1 Building Exterior Door2 Building Interior Door3 Exterior Elevator4 Interior Elevator5 Parking Garage Level Access6 Parking Garage Vehicle Entrance7 Perimeter Gate into Building Courtyard8 Other9 Venue PortalName: The name associated with the building entrance.EGISID: The Enterprise GIS unique identification number. This number is automatically generated and incremented by a script. This is a Long field with a precision = 10. Do not edit this number.

Copyright Text: University of Arizona Enterprise GIS (EGIS)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

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

  Iteminfo   Thumbnail   Metadata