documento generado automáticamente
Descripción global: **Clase de nivel superior para la red de vías descrita como un modelo topológico de nodos y bordes.
versión: 0.0.1
[*] Si no hay un tipo en un atributo es porque puede tener varios tipos o diferentes formatos/patrones.
address[object]: La dirección postal . Model: https://schema.org/addressaddressCountry[string]: El país. Por ejemplo, España . Model: https://schema.org/addressCountryaddressLocality[string]: La localidad en la que se encuentra la dirección postal, y que está en la región . Model: https://schema.org/addressLocalityaddressRegion[string]: La región en la que se encuentra la localidad, y que está en el país . Model: https://schema.org/addressRegiondistrict[string]: Un distrito es un tipo de división administrativa que, en algunos países, gestiona el gobierno localpostOfficeBoxNumber[string]: El número del apartado de correos para las direcciones de apartados postales. Por ejemplo, 03578 . Model: https://schema.org/postOfficeBoxNumberpostalCode[string]: El código postal. Por ejemplo, 24004 . Model: https://schema.org/https://schema.org/postalCodestreetAddress[string]: La dirección . Model: https://schema.org/streetAddressstreetNr[string]: Número que identifica una propiedad específica en una vía pública
alternateName[string]: Un nombre alternativo para este artículoareaServed[string]: La zona geográfica en la que se presta un servicio o se ofrece un artículo . Model: https://schema.org/TextdataProvider[string]: Una secuencia de caracteres que identifica al proveedor de la entidad de datos armonizadadateCreated[date-time]: Fecha de creación de la entidad. Normalmente será asignada por la plataforma de almacenamientodateModified[date-time]: Marca de tiempo de la última modificación de la entidad. Suele ser asignada por la plataforma de almacenamientodescription[string]: Descripción de este artículoid[*]: Identificador único de la entidadlocation[*]: Referencia Geojson al elemento. Puede ser Point, LineString, Polygon, MultiPoint, MultiLineString o MultiPolygon.name[string]: El nombre de este artículoowner[array]: Una lista que contiene una secuencia de caracteres codificada en JSON que hace referencia a los identificadores únicos de los propietarios.seeAlso[*]: lista de uri que apuntan a recursos adicionales sobre el artículosource[string]: Secuencia de caracteres que indica la fuente original de los datos de la entidad en forma de URL. Se recomienda que sea el nombre de dominio completo del proveedor de origen o la URL del objeto de origen.type[string]: Tipo de datos NGSI. Tiene que ser TopologicalObject
Propiedades requeridas
idtype
modelo de datos extraído de la ontología ERA https://data-interop.era.europa.eu/era-vocabulary (Agencia Ferroviaria de la Unión Europea)
Ordenados alfabéticamente (pulse para más detalles)
full yaml details
TopologicalObject:
description: Top level class for the the track network described as a topological node edge model
properties:
address:
description: The mailing address
properties:
addressCountry:
description: 'The country. For example, Spain'
type: string
x-ngsi:
model: https://schema.org/addressCountry
type: Property
addressLocality:
description: 'The locality in which the street address is, and which is in the region'
type: string
x-ngsi:
model: https://schema.org/addressLocality
type: Property
addressRegion:
description: 'The region in which the locality is, and which is in the country'
type: string
x-ngsi:
model: https://schema.org/addressRegion
type: Property
district:
description: 'A district is a type of administrative division that, in some countries, is managed by the local government'
type: string
x-ngsi:
type: Property
postOfficeBoxNumber:
description: 'The post office box number for PO box addresses. For example, 03578'
type: string
x-ngsi:
model: https://schema.org/postOfficeBoxNumber
type: Property
postalCode:
description: 'The postal code. For example, 24004'
type: string
x-ngsi:
model: https://schema.org/https://schema.org/postalCode
type: Property
streetAddress:
description: The street address
type: string
x-ngsi:
model: https://schema.org/streetAddress
type: Property
streetNr:
description: Number identifying a specific property on a public street
type: string
x-ngsi:
type: Property
type: object
x-ngsi:
model: https://schema.org/address
type: Property
alternateName:
description: An alternative name for this item
type: string
x-ngsi:
type: Property
areaServed:
description: The geographic area where a service or offered item is provided
type: string
x-ngsi:
model: https://schema.org/Text
type: Property
dataProvider:
description: A sequence of characters identifying the provider of the harmonised data entity
type: string
x-ngsi:
type: Property
dateCreated:
description: Entity creation timestamp. This will usually be allocated by the storage platform
format: date-time
type: string
x-ngsi:
type: Property
dateModified:
description: Timestamp of the last modification of the entity. This will usually be allocated by the storage platform
format: date-time
type: string
x-ngsi:
type: Property
description:
description: A description of this item
type: string
x-ngsi:
type: Property
id:
anyOf:
- description: Identifier format of any NGSI entity
maxLength: 256
minLength: 1
pattern: ^[\w\-\.\{\}\$\+\*\[\]`|~^@!,:\\]+$
type: string
x-ngsi:
type: Property
- description: Identifier format of any NGSI entity
format: uri
type: string
x-ngsi:
type: Property
description: Unique identifier of the entity
x-ngsi:
type: Property
location:
description: 'Geojson reference to the item. It can be Point, LineString, Polygon, MultiPoint, MultiLineString or MultiPolygon'
oneOf:
- description: Geojson reference to the item. Point
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
type: number
minItems: 2
type: array
type:
enum:
- Point
type: string
required:
- type
- coordinates
title: GeoJSON Point
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. LineString
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
type: number
minItems: 2
type: array
minItems: 2
type: array
type:
enum:
- LineString
type: string
required:
- type
- coordinates
title: GeoJSON LineString
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. Polygon
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
items:
type: number
minItems: 2
type: array
minItems: 4
type: array
type: array
type:
enum:
- Polygon
type: string
required:
- type
- coordinates
title: GeoJSON Polygon
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. MultiPoint
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
type: number
minItems: 2
type: array
type: array
type:
enum:
- MultiPoint
type: string
required:
- type
- coordinates
title: GeoJSON MultiPoint
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. MultiLineString
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
items:
type: number
minItems: 2
type: array
minItems: 2
type: array
type: array
type:
enum:
- MultiLineString
type: string
required:
- type
- coordinates
title: GeoJSON MultiLineString
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. MultiLineString
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
items:
items:
type: number
minItems: 2
type: array
minItems: 4
type: array
type: array
type: array
type:
enum:
- MultiPolygon
type: string
required:
- type
- coordinates
title: GeoJSON MultiPolygon
type: object
x-ngsi:
type: GeoProperty
x-ngsi:
type: GeoProperty
name:
description: The name of this item
type: string
x-ngsi:
type: Property
owner:
description: A List containing a JSON encoded sequence of characters referencing the unique Ids of the owner(s)
items:
anyOf:
- description: Identifier format of any NGSI entity
maxLength: 256
minLength: 1
pattern: ^[\w\-\.\{\}\$\+\*\[\]`|~^@!,:\\]+$
type: string
x-ngsi:
type: Property
- description: Identifier format of any NGSI entity
format: uri
type: string
x-ngsi:
type: Property
description: Unique identifier of the entity
x-ngsi:
type: Property
type: array
x-ngsi:
type: Property
seeAlso:
description: list of uri pointing to additional resources about the item
oneOf:
- items:
format: uri
type: string
minItems: 1
type: array
- format: uri
type: string
x-ngsi:
type: Property
source:
description: 'A sequence of characters giving the original source of the entity data as a URL. Recommended to be the fully qualified domain name of the source provider, or the URL to the source object'
type: string
x-ngsi:
type: Property
type:
description: NGSI data type. It has to be TopologicalObject
enum:
- TopologicalObject
type: string
x-ngsi:
type: Property
required:
- id
- type
type: object
x-derived-from: http://data.europa.eu/949/TopologicalObject
x-disclaimer: 'Redistribution and use in source and binary forms, with or without modification, are permitted provided that the license conditions are met. Copyleft (c) 2023 Contributors to Smart Data Models Program'
x-license-url: https://github.com/smart-data-models/dataModel.ERA/blob/master/TopologicalObject/LICENSE.md
x-model-schema: https://smart-data-models.github.io/dataModel.ERA/Certificate/schema.json
x-model-tags: 'ERA vocabulary, railway, train'
x-version: 0.0.1 Aquí hay un ejemplo de un TopologicalObject en formato JSON-LD como valores-clave. Esto es compatible con NGSI-v2 cuando se utiliza options=keyValues y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:TopologicalObject:id:MDTE:29122911",
"dateCreated": "1997-12-28T14:44:16Z",
"dateModified": "1986-06-03T02:06:03Z",
"source": "Race box market story. Father establish himself everyone",
"name": "Least chair pull serve specific expect modern. Debate end difficult wife. Player various popular southern believe amount lot method.",
"alternateName": "Address happy television wide bu",
"description": "Finish then evidence just. Book hundred kind model opportunity. Always pattern class oil soldier conference involve.",
"dataProvider": "Room affect someone need manager. Range represent compare reality beat.",
"owner": [
"urn:ngsi-ld:TopologicalObject:items:HQJL:52681721",
"urn:ngsi-ld:TopologicalObject:items:RKZS:06098455"
],
"seeAlso": [
"urn:ngsi-ld:TopologicalObject:items:DCVU:82796661"
],
"location": {
"type": "Point",
"coordinates": [
-6.809152,
70.994051
]
},
"address": {
"streetAddress": "Them generation story painting economy hair their. Keep together among she.",
"addressLocality": "Charge win great only.",
"addressRegion": "Popular thank would represent course. Just image represent decision parent. Degree west lay gar",
"addressCountry": "Health history lose defense. About husband market student short cost green. Morning poor example alre",
"postalCode": "Ready course edge author. Century once lead approach after.",
"postOfficeBoxNumber": "Dream now federal nice. Fish give entire home detail against.",
"streetNr": "Turn become hotel game ",
"district": "Cover whole pay customer management approach theory."
},
"areaServed": "Partner a improve about. Because four challenge. Hot north personal benefit.",
"type": "TopologicalObject"
} He aquí un ejemplo de un TopologicalObject en formato JSON-LD normalizado. Esto es compatible con NGSI-v2 cuando no se utilizan opciones y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:TopologicalObject:id:MDTE:29122911",
"dateCreated": {
"type": "DateTime",
"value": "1997-12-28T14:44:16Z"
},
"dateModified": {
"type": "DateTime",
"value": "1986-06-03T02:06:03Z"
},
"source": {
"type": "Text",
"value": "Race box market story. Father establish himself everyone"
},
"name": {
"type": "Text",
"value": "Least chair pull serve specific expect modern. Debate end difficult wife. Player various popular southern believe amount lot method."
},
"alternateName": {
"type": "Text",
"value": "Address happy television wide bu"
},
"description": {
"type": "Text",
"value": "Finish then evidence just. Book hundred kind model opportunity. Always pattern class oil soldier conference involve."
},
"dataProvider": {
"type": "Text",
"value": "Room affect someone need manager. Range represent compare reality beat."
},
"owner": {
"type": "StructuredValue",
"value": [
"urn:ngsi-ld:TopologicalObject:items:HQJL:52681721",
"urn:ngsi-ld:TopologicalObject:items:RKZS:06098455"
]
},
"seeAlso": {
"type": "StructuredValue",
"value": [
"urn:ngsi-ld:TopologicalObject:items:DCVU:82796661"
]
},
"location": {
"type": "geo:json",
"value": {
"type": "Point",
"coordinates": [
-6.809152,
70.994051
]
}
},
"address": {
"type": "StructuredValue",
"value": {
"streetAddress": "Them generation story painting economy hair their. Keep together among she.",
"addressLocality": "Charge win great only.",
"addressRegion": "Popular thank would represent course. Just image represent decision parent. Degree west lay gar",
"addressCountry": "Health history lose defense. About husband market student short cost green. Morning poor example alre",
"postalCode": "Ready course edge author. Century once lead approach after.",
"postOfficeBoxNumber": "Dream now federal nice. Fish give entire home detail against.",
"streetNr": "Turn become hotel game ",
"district": "Cover whole pay customer management approach theory."
}
},
"areaServed": {
"type": "Text",
"value": "Partner a improve about. Because four challenge. Hot north personal benefit."
},
"type": "TopologicalObject"
} He aquí un ejemplo de un TopologicalObject en formato JSON-LD como key-values. Esto es compatible con NGSI-LD cuando se utiliza options=keyValues y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:TopologicalObject:id:MDTE:29122911",
"dateCreated": "1997-12-28T14:44:16Z",
"dateModified": "1986-06-03T02:06:03Z",
"source": "Race box market story. Father establish himself everyone",
"name": "Least chair pull serve specific expect modern. Debate end difficult wife. Player various popular southern believe amount lot method.",
"alternateName": "Address happy television wide bu",
"description": "Finish then evidence just. Book hundred kind model opportunity. Always pattern class oil soldier conference involve.",
"dataProvider": "Room affect someone need manager. Range represent compare reality beat.",
"owner": [
"urn:ngsi-ld:TopologicalObject:items:HQJL:52681721",
"urn:ngsi-ld:TopologicalObject:items:RKZS:06098455"
],
"seeAlso": [
"urn:ngsi-ld:TopologicalObject:items:DCVU:82796661"
],
"location": {
"type": "Point",
"coordinates": [
-6.809152,
70.994051
]
},
"address": {
"streetAddress": "Them generation story painting economy hair their. Keep together among she.",
"addressLocality": "Charge win great only.",
"addressRegion": "Popular thank would represent course. Just image represent decision parent. Degree west lay gar",
"addressCountry": "Health history lose defense. About husband market student short cost green. Morning poor example alre",
"postalCode": "Ready course edge author. Century once lead approach after.",
"postOfficeBoxNumber": "Dream now federal nice. Fish give entire home detail against.",
"streetNr": "Turn become hotel game ",
"district": "Cover whole pay customer management approach theory."
},
"areaServed": "Partner a improve about. Because four challenge. Hot north personal benefit.",
"type": "TopologicalObject",
"@context": [
"https://raw.githubusercontent.com/smart-data-models/dataModel.ERA/master/context.jsonld"
]
} He aquí un ejemplo de un TopologicalObject en formato JSON-LD normalizado. Esto es compatible con NGSI-LD cuando no se utilizan opciones y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:TopologicalObject:id:ANPE:97919193",
"dateCreated": {
"type": "Property",
"value": {
"@type": "DateTime",
"@value": "2018-09-17T09:21:53Z"
}
},
"dateModified": {
"type": "Property",
"value": {
"@type": "DateTime",
"@value": "1996-07-18T12:43:19Z"
}
},
"source": {
"type": "Property",
"value": "Yes serve free seat. Room including each yard walk attack."
},
"name": {
"type": "Property",
"value": "Actually large man expect eye voic"
},
"alternateName": {
"type": "Property",
"value": "Season area fill station news stop. Choice marriage"
},
"description": {
"type": "Property",
"value": "Guy remain them seven general. Worker term address. Education detail not share human win item."
},
"dataProvider": {
"type": "Property",
"value": "Current treatment sing. Hour bed song all tend success fine. Develop guy if them interest high bed. Strong certain say offer i"
},
"owner": {
"type": "Property",
"value": [
"urn:ngsi-ld:TopologicalObject:items:HBZC:96164619",
"urn:ngsi-ld:TopologicalObject:items:SZBJ:87847721"
]
},
"seeAlso": {
"type": "Property",
"value": [
"urn:ngsi-ld:TopologicalObject:items:VWRI:32992685"
]
},
"location": {
"type": "Property",
"value": {
"type": "Point",
"coordinates": [
0.125705,
0.810063
]
}
},
"address": {
"type": "Property",
"value": {
"streetAddress": "Building out then when gas address face. Increase tele",
"addressLocality": "Also house growth leave now food information. Management across tree factor Republican.",
"addressRegion": "F",
"addressCountry": "Score him say majority drug catch figure however. Eat condition subject least. Purpose guess such quickly management wear ",
"postalCode": "Southe",
"postOfficeBoxNumber": "Fear surface but effect. Sing structure growth with personal western.",
"streetNr": "Window down clear window describe hand determine. Talk bill thousand lay recognize. Customer trip place really poor after ene",
"district": "Family opportunity leg industry theory smile image. Into "
}
},
"areaServed": {
"type": "Property",
"value": "Hear her year population be."
},
"type": "TopologicalObject",
"@context": [
"https://raw.githubusercontent.com/smart-data-models/dataModel.ERA/master/context.jsonld"
]
} Consulte FAQ 10 para obtener una respuesta sobre cómo tratar las unidades de magnitud.
