Thing > Place > AdministrativeArea

A geographical region under the jurisdiction of a particular government.

Usage: Between 100 and 1000 domains
[more...]
PropertyExpected TypeDescription
Properties from Place
additionalProperty PropertyValue A property-value pair representing an additional characteristics of the entitity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.

Note: Publishers should be aware that applications designed to use specific schema.org properties (e.g. http://schema.org/width, http://schema.org/color, http://schema.org/gtin13, ...) will typically expect such data to be provided using those properties, rather than using the generic property/value mechanism.
address PostalAddress Physical address of the item.
aggregateRating AggregateRating The overall rating, based on a collection of reviews or ratings, of the item.
containedIn Place The basic containment relation between places.
event Event Upcoming or past event associated with this place, organization, or action. Supersedes events.
faxNumber Text The fax number.
geo GeoShape  or
GeoCoordinates 
The geo coordinates of the place.
globalLocationNumber Text The Global Location Number (GLN, sometimes also referred to as International Location Number or ILN) of the respective organization, person, or place. The GLN is a 13-digit number used to identify parties and physical locations.
hasMap URL  or
Map 
A URL to a map of the place. Supersedes map, maps.
isicV4 Text The International Standard of Industrial Classification of All Economic Activities (ISIC), Revision 4 code for a particular organization, business person, or place.
logo URL  or
ImageObject 
An associated logo.
openingHoursSpecification OpeningHoursSpecification The opening hours of a certain place.
photo Photograph  or
ImageObject 
A photograph of this place. Supersedes photos.
review Review A review of the item. Supersedes reviews.
telephone Text The telephone number.
Properties from Thing
additionalType URL An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
alternateName Text An alias for the item.
description Text A short description of the item.
image URL  or
ImageObject 
An image of the item. This can be a URL or a fully described ImageObject.
mainEntityOfPage CreativeWork  or
URL 
Indicates a page (or other CreativeWork) for which this thing is the main entity being described.

Many (but not all) pages have a fairly clear primary topic, some entity or thing that the page describes. For example a restaurant's home page might be primarily about that Restaurant, or an event listing page might represent a single event. The mainEntity and mainEntityOfPage properties allow you to explicitly express the relationship between the page and the primary entity.

Related properties include sameAs, about, and url.

The sameAs and url properties are both similar to mainEntityOfPage. The url property should be reserved to refer to more official or authoritative web pages, such as the item’s official website. The sameAs property also relates a thing to a page that indirectly identifies it. Whereas sameAs emphasises well known pages, the mainEntityOfPage property serves more to clarify which of several entities is the main one for that page.

mainEntityOfPage can be used for any page, including those not recognized as authoritative for that entity. For example, for a product, sameAs might refer to a page on the manufacturer’s official site with specs for the product, while mainEntityOfPage might be used on pages within various retailers’ sites giving details for the same product.

about is similar to mainEntity, with two key differences. First, about can refer to multiple entities/topics, while mainEntity should be used for only the primary one. Second, some pages have a primary entity that itself describes some other entity. For example, one web page may display a news article about a particular person. Another page may display a product review for a particular product. In these cases, mainEntity for the pages should refer to the news article or review, respectively, while about would more properly refer to the person or product.
Inverse property: mainEntity.
name Text The name of the item.
potentialAction Action Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
sameAs URL URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Freebase page, or official website.
url URL URL of the item.


Instances of AdministrativeArea may appear as values for the following properties
PropertyOn TypesDescription
applicableLocation DrugLegalStatus  or
DrugCost 
The location in which the status applies.
areaServed ContactPoint The location served by this contact point (e.g., a phone number intended for Europeans vs. North Americans or only within the United States).
availableIn DrugStrength The location in which the strength is available.
geographicArea Audience The geographic area associated with the audience.
serviceArea Service The geographic area where the service is provided. Supersedes area.
studyLocation MedicalStudy The location in which the study is taking/took place.
validIn Permit The geographic area where the permit is valid.

More specific Types
  • City
  • Country
  • State

    Examples

    <div>
    NYC Food Service Establishment Permit, issued by Department of Health and Mental Hygiene.
    (issued through NYC Food Service Establishment Permit Service; valid in New York for 1 year).
    </div>
    
    <div itemscope itemtype="http://schema.org/GovernmentPermit">
      <span itemprop="name">NYC Food Service Establishment Permit</span>
      <div itemprop="issuedBy" itemscope itemtype="http://schema.org/GovernmentOrganization">
        <span itemprop="name">Department of Health and Mental Hygiene"</span>
      </div>
      <div itemprop="issuedThrough" itemscope itemtype="http://schema.org/GovernmentService">
        <span itemprop="name">NYC Food Service Establishment Permit Service</span>
       </div>
      <div itemprop="validIn" itemscope itemtype="http://schema.org/AdministrativeArea">
        <span itemprop="name">New York</span>
      </div>
      <time itemprop="validFor" content="P1Y">1 year</time>
    </div>
    
    <div vocab="http://schema.org/" typeof="GovernmentPermit">
      <span property="name">NYC Food Service Establishment Permit</span>
      <div property="issuedBy"  typeof="GovernmentOrganization">
        <span property="name">Department of Health and Mental Hygiene"</span>
      </div>
      <div property="issuedThrough"  typeof="GovernmentService">
        <span property="name">NYC Food Service Establishment Permit Service</span>
       </div>
      <div property="validIn"  typeof="AdministrativeArea">
        <span property="name">New York</span>
      </div>
      <time property="validFor" content="P1Y">1 year</time>
    </div>
    
    <script type="application/ld+json">
    {
      "@context": "http://schema.org",
      "@type": "GovernmentPermit",
      "issuedBy": {
        "@type": "GovernmentOrganization",
        "name": "Department of Health and Mental Hygiene\""
      },
      "issuedThrough": {
        "@type": "GovernmentService",
        "name": "NYC Food Service Establishment Permit Service"
      },
      "name": "NYC Food Service Establishment Permit",
      "validFor": "",
      "validIn": {
        "@type": "AdministrativeArea",
        "name": "New York"
      }
    }
    </script>
    
    This example shows a JSON-LD description of services that do not necessarily have a direct
    human-oriented HTML description. It describes a GovernmentService named "Veterans Affairs Emergency Mental Health",
    its operator, service area and service details, such as its Veterans Crisis Line (including  phone contact line
    hours of operation, language and other details).
    
    This example is JSON only.
    
    This example is JSON only.
    
    <script type='application/ld+json'>
    {
      "@context": "http://schema.org",
      "@type": "GovernmentService",
      "name": "Veterans Affairs Emergency Mental Health",
      "serviceType": "Psychiatric Emergency Services",
      "operator": {
        "@type": "GovernmentOrganization",
        "name": "US Department of Veterans Affairs"
      },
      "serviceArea": {
        "@type": "AdministrativeArea",
        "name": "Massachusetts"
      },
      "audience": {
        "@type": "CivicAudience",
        "name": "Veterans"
      },
      "availableChannel": {
        "@type": "ServiceChannel",
        "name": "Urgent Care Clinic",
        "availableLanguage": {
          "@type": "Language",
          "name": "Spanish"
        },
        "serviceLocation": {
          "@type": "Hospital",
          "name": "VA Boston -- West Roxbury",
          "address": {
            "@type": "PostalAddress",
            "streetAddress": "1400 VFW Parkway",
            "addressLocality": "West Roxbury",
            "addressRegion": "MA",
            "postalCode": "02132"
          }
        }
      }
    }
    </script>
    

    Schema Version 2.0