LocationFeatureSpecification Schema Generator and Guide

LocationFeatureSpecification

Schema.org Type

Specifies a location feature by providing a structured value representing a feature of an accommodation as a property-value pair of varying degrees of formality.

Generate this schema

We Can Help

LocationFeatureSpecification schema is a sub type of:

This schema has no sub types

LocationFeatureSpecification Schema Generator in JSON-LD

Create Knowledge Graph

LocationFeatureSpecification schema code:

This Schema can take the following complex properties:


How to Create a LocationFeatureSpecification Schema

Step 1: Fill out the form above as much as possible.

Note:Use this Schema.org based structured data generator tool to easily create LocationFeatureSpecification schema.
The properties are the description of your entity. You don't have to fill in all the properties on this page. Provide what is available and leave what is not. To learn more about each property in your schema type please check LocationFeatureSpecification schema properties


Step 2: When complete click the Copy Code button to get your JSON-LD code

Notes:To check if your code is eligible for featured snippets (rich snippets or rich results) test your code with the Rich Results Test tool to learn more about which schema are qualified for rich results check out Google’s search gallery.
To validate your markup code, check your JSON-LD code with the Schema Markup Validator


Step 3: To add a sub-schema, click on the Create Knowledge Graph button

Important Notes: to describe the relationship between your entities you must design a custom schema, this is where the 'creation of knowledge graph' is needed.
For example: if you have a local business and you want to add a service catalogue, or if you have a recipe schema and you want to add a HowTo steps, or if you have a product and you want to add a FAQ about it, to learn more watch this semantic SEO workshop




Generate this schema

Hire Us


LocationFeatureSpecification Schema Properties

LocationFeatureSpecification has 23 properties:

  • additionalType 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 An alias for the item.
  • description A description of the item.
  • disambiguatingDescription A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.
  • hoursAvailable The hours during which this service or contact is available.
  • identifier The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
  • image An image of the item. This can be a URL or a fully described ImageObject.
  • mainEntityOfPage Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details.
  • maxValue The upper value of some characteristic or property.
  • measurementTechnique A technique or technology used in a Dataset (or DataDownload, DataCatalog), corresponding to the method used for measuring the corresponding variable(s) (described using variableMeasured). This is oriented towards scientific and scholarly dataset publication but may have broader applicability; it is not intended as a full representation of measurement, but rather as a high level summary for dataset discovery.

    For example, if variableMeasured is: molecule concentration, measurementTechnique could be: "mass spectrometry" or "nmr spectroscopy" or "colorimetry" or "immunofluorescence".

    If the variableMeasured is "depression rating", the measurementTechnique could be "Zung Scale" or "HAM-D" or "Beck Depression Inventory".

    If there are several variableMeasured properties recorded for some given data object, use a PropertyValue for each variableMeasured and attach the corresponding measurementTechnique.
  • minValue The lower value of some characteristic or property.
  • name The name of the item.
  • potentialAction Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.
  • propertyID A commonly used identifier for the characteristic represented by the property, e.g. a manufacturer or a standard code for a property. propertyID can be (1) a prefixed string, mainly meant to be used with standards for product properties; (2) a site-specific, non-prefixed string (e.g. the primary key of the property or the vendor-specific id of the property), or (3) a URL indicating the type of the property, either pointing to an external vocabulary, or a Web resource that describes the property (e.g. a glossary entry). Standards bodies should promote a standard prefix for the identifiers of properties from their standards.
  • sameAs URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.
  • subjectOf A CreativeWork or Event about this Thing.
  • unitCode The unit of measurement given using the UN/CEFACT Common Code (3 characters) or a URL. Other codes than the UN/CEFACT Common Code may be used with a prefix followed by a colon.
  • unitText A string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for unitCode.
  • url URL of the item.
  • validFrom The date when the item becomes valid.
  • validThrough The date after when the item is not valid. For example the end of an offer, salary period, or a period of opening hours.
  • value The value of the quantitative value or property value node.

    • For QuantitativeValue and MonetaryAmount, the recommended type for values is 'Number'.
    • For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'.
    • Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similiar Unicode symbols.
    • Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
  • valueReference A secondary value that provides additional information on the original value, e.g. a reference temperature or a type of measurement.