From ead2e066143cc4c7810de78cb1b7fc770fc66ca6 Mon Sep 17 00:00:00 2001 From: ue71603 Date: Wed, 20 Jul 2022 20:58:57 +0200 Subject: [PATCH 1/6] Simplfications of elements --- OJP/OJP_PlaceSupport.xsd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/OJP/OJP_PlaceSupport.xsd b/OJP/OJP_PlaceSupport.xsd index ffd9ddd80..bfd8d9b06 100644 --- a/OJP/OJP_PlaceSupport.xsd +++ b/OJP/OJP_PlaceSupport.xsd @@ -222,12 +222,12 @@ [corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners. - + ID of this Point of Interest. - + Name or description of point of interest for use in passenger information. @@ -366,7 +366,7 @@ descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both - + ID of this address. @@ -376,7 +376,7 @@ Code of this address in private/foreign/proprietary coding schemes. - + Name or description of address for use in passenger information. From 118d5feefe07e57b54e862eeb501edbd22a0528a Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Wed, 20 Jul 2022 19:00:37 +0000 Subject: [PATCH 2/6] Travis CI update [skip ci] --- docs/generated/OJP.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/generated/OJP.html b/docs/generated/OJP.html index 4bbfbfe1e..db715ef82 100644 --- a/docs/generated/OJP.html +++ b/docs/generated/OJP.html @@ -436,7 +436,7 @@

OJP - Open API for distributed Journey StopAttributes

WheelchairAccessible

0:1

xs:boolean

Whether this stop is accessible for wheelchair users.

Lighting

0:1

xs:boolean

Whether this stop is lit.

Covered

0:1

xs:boolean

Whether this stop offers protection from weather conditions like rain, snow, storm etc.

-

9.9. The complex type TopographicPlaceRefStructure

TopographicPlaceRefStructure

Reference to a TopographicPlace

9.10. The toplevel element TopographicPlaceRef

TopographicPlaceRef

+TopographicPlaceRef

Reference to a TopographicPlace

9.11. The complex type TopographicPlaceStructure

TopographicPlaceStructure

[TMv6] A type of PLACE providing the topographical context when searching for or presenting travel information, for example as the origin or destination of a trip. It may be of any size (e.g. County,City, Town, Village) and of different specificity (e.g. Greater London, London, West End, Westminster, St James's).

The element contains a sequence of the following elements:

TopographicPlaceCode

1:1

TopographicPlace ID.

TopographicPlaceName

1:1

+InternationalText

Name or description of TopographicPlace for use in passenger information.

PrivateCode

0:*

+PrivateCode

Code of this TopographicPlace in private/foreign/proprietary coding schemes.

ParentRef

0:1

+TopographicPlaceRef

Reference to a parent TopographicPlace.

ReferredSystemId

0:1

xs:normalizedString

Used in distributed environments (e.g. EU-Spirit). If set, this topographic place resides within the given system (in EU-Spirit "passive server"). This system can be queried for actual places within this topographic place. This is used in an distributed environment for a two-steps place identification. In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

Area

0:1

+Area

Area covered by the locality described as a polygon.

9.12. The complex type PointOfInterestRefStructure

PointOfInterestRefStructure

PointOfInterestCode

Reference to a Point of Interest

9.13. The toplevel element PointOfInterestRef

PointOfInterestRef

+PointOfInterestRef

Reference to a Point of Interest

9.14. The complex type PointOfInterestStructure

PointOfInterestStructure

[corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners.

The element contains a sequence of the following elements:

PointOfInterestCode

1:1

PointOfInterestCode

ID of this Point of Interest.

PointOfInterestName

1:1

+InternationalText

Name or description of point of interest for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the point of interest that may be appended to the name if enough space is available. F.e. "Exhibition Center".

PointOfInterestCategory

0:*

+PointOfInterestCategory

Categories this POI is associated with. Order indicates descending relevance.

PrivateCode

0:*

+PrivateCode

Code of this point of interest in private/foreign/proprietary coding schemes.

→‍TopographicPlaceRef

0:1

→‍TopographicPlaceRef

If at least one is set, only place objects within the given localities are allowed.If at least one is set, only place objects within the given localities are allowed.Reference to a TopographicPlace

9.15. The complex type PointOfInterestCategoryStructure

PointOfInterestCategoryStructure

[a view of POINT OF INTEREST CLASSIFICATION in TMv6] categorisation of POINTs OF INTEREST in respect of the activities undertaken at them (defined by key-value-pairs).

The element contains one of the following elements:

a

OsmTag

-1:*

+OsmTag

Open Street Map tag structure (key-value)

b

PointOfInterestClassification

-1:*

xs:string

Classification of the POI (when it is not from OSM). The codification of the classification Id may include de codification source (for example "IGN:[classificationCode]")

9.16. The complex type OsmTagStructure

OsmTagStructure

Structure of an Open Street Map tag.

The element contains a sequence of the following elements:

Tag

1:1

xs:NMTOKEN

Name of Open Street Map tag (amenity, leisure, tourism, bike, ...)

Value

1:1

xs:NMTOKEN

Value for Open Street Map tag (charging_station, hostel, yes, ...)

9.17. The complex type PointOfInterestFilterStructure

PointOfInterestFilterStructure

Filter POIs by category.

The element contains a sequence of the following elements:

Exclude

0:1

xs:boolean

Whether categories in list are to include or exclude from search. Default is FALSE.

PointOfInterestCategory

0:*

+PointOfInterestCategory

These POI categories can be used to filter POIs. If more than one is given the filtering is by logical "OR" (when Exclude=FALSE) and logical "AND" (when Exclude=TRUE).

9.18. The complex type AddressRefStructure

AddressRefStructure

AddressCode

Reference to an Address

9.19. The toplevel element AddressRef

AddressRef

+AddressRef

Reference to an Address

9.20. The AddressDetailGroup group

+

AddressDetailGroup

An address with its name entities

9.9. The complex type TopographicPlaceRefStructure

TopographicPlaceRefStructure

Reference to a TopographicPlace

9.10. The toplevel element TopographicPlaceRef

TopographicPlaceRef

+TopographicPlaceRef

Reference to a TopographicPlace

9.11. The complex type TopographicPlaceStructure

TopographicPlaceStructure

[TMv6] A type of PLACE providing the topographical context when searching for or presenting travel information, for example as the origin or destination of a trip. It may be of any size (e.g. County,City, Town, Village) and of different specificity (e.g. Greater London, London, West End, Westminster, St James's).

The element contains a sequence of the following elements:

TopographicPlaceCode

1:1

TopographicPlace ID.

TopographicPlaceName

1:1

+InternationalText

Name or description of TopographicPlace for use in passenger information.

PrivateCode

0:*

+PrivateCode

Code of this TopographicPlace in private/foreign/proprietary coding schemes.

ParentRef

0:1

+TopographicPlaceRef

Reference to a parent TopographicPlace.

ReferredSystemId

0:1

xs:normalizedString

Used in distributed environments (e.g. EU-Spirit). If set, this topographic place resides within the given system (in EU-Spirit "passive server"). This system can be queried for actual places within this topographic place. This is used in an distributed environment for a two-steps place identification. In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

Area

0:1

+Area

Area covered by the locality described as a polygon.

9.12. The complex type PointOfInterestRefStructure

PointOfInterestRefStructure

PointOfInterestCode

Reference to a Point of Interest

9.13. The toplevel element PointOfInterestRef

PointOfInterestRef

+PointOfInterestRef

Reference to a Point of Interest

9.14. The complex type PointOfInterestStructure

PointOfInterestStructure

[corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners.

The element contains a sequence of the following elements:

Code

1:1

PointOfInterestCode

ID of this Point of Interest.

Name

1:1

+InternationalText

Name or description of point of interest for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the point of interest that may be appended to the name if enough space is available. F.e. "Exhibition Center".

PointOfInterestCategory

0:*

+PointOfInterestCategory

Categories this POI is associated with. Order indicates descending relevance.

PrivateCode

0:*

+PrivateCode

Code of this point of interest in private/foreign/proprietary coding schemes.

→‍TopographicPlaceRef

0:1

→‍TopographicPlaceRef

If at least one is set, only place objects within the given localities are allowed.If at least one is set, only place objects within the given localities are allowed.Reference to a TopographicPlace

9.15. The complex type PointOfInterestCategoryStructure

PointOfInterestCategoryStructure

[a view of POINT OF INTEREST CLASSIFICATION in TMv6] categorisation of POINTs OF INTEREST in respect of the activities undertaken at them (defined by key-value-pairs).

The element contains one of the following elements:

a

OsmTag

-1:*

+OsmTag

Open Street Map tag structure (key-value)

b

PointOfInterestClassification

-1:*

xs:string

Classification of the POI (when it is not from OSM). The codification of the classification Id may include de codification source (for example "IGN:[classificationCode]")

9.16. The complex type OsmTagStructure

OsmTagStructure

Structure of an Open Street Map tag.

The element contains a sequence of the following elements:

Tag

1:1

xs:NMTOKEN

Name of Open Street Map tag (amenity, leisure, tourism, bike, ...)

Value

1:1

xs:NMTOKEN

Value for Open Street Map tag (charging_station, hostel, yes, ...)

9.17. The complex type PointOfInterestFilterStructure

PointOfInterestFilterStructure

Filter POIs by category.

The element contains a sequence of the following elements:

Exclude

0:1

xs:boolean

Whether categories in list are to include or exclude from search. Default is FALSE.

PointOfInterestCategory

0:*

+PointOfInterestCategory

These POI categories can be used to filter POIs. If more than one is given the filtering is by logical "OR" (when Exclude=FALSE) and logical "AND" (when Exclude=TRUE).

9.18. The complex type AddressRefStructure

AddressRefStructure

AddressCode

Reference to an Address

9.19. The toplevel element AddressRef

AddressRef

+AddressRef

Reference to an Address

9.20. The AddressDetailGroup group

@@ -444,7 +444,7 @@

OJP - Open API for distributed Journey

-

AddressDetailGroup

An address with its name entities

AddressDetail

CountryName

0:1

xs:string

Country of the address.

PostCode

0:1

xs:string

Postal code of the address.

TopographicPlaceName

0:1

xs:string

TopographicPlace name of the address. If set it should at least contain the city name.

Street

0:1

xs:string

Street name of the address.

HouseNumber

0:1

xs:string

House number of the address. If none is given, either a crossing street can be given, or the whole street is meant.

CrossRoad

0:1

xs:string

Crossing. This can be used to be more specific without using house numbers.

9.21. The complex type AddressStructure

+

AddressStructure

descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both

The element contains a sequence of the following elements:

AddressCode

1:1

AddressCode

ID of this address.

PrivateCode

0:*

+PrivateCode

Code of this address in private/foreign/proprietary coding schemes.

AddressName

1:1

+InternationalText

Name or description of address for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the address that may be appended to the name if enough space is available. F.e. "Crossing with Peterstraße".

9.21. The complex type AddressStructure

From 175ae0cd18def032f23e583ba9c43d19c71a69a1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Mon, 8 Aug 2022 14:43:36 +0200 Subject: [PATCH 3/6] Update OJP/OJP_PlaceSupport.xsd Co-authored-by: Stefan de Konink --- OJP/OJP_PlaceSupport.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OJP/OJP_PlaceSupport.xsd b/OJP/OJP_PlaceSupport.xsd index bfd8d9b06..30433e8b0 100644 --- a/OJP/OJP_PlaceSupport.xsd +++ b/OJP/OJP_PlaceSupport.xsd @@ -222,7 +222,7 @@ [corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners. - + ID of this Point of Interest. From 304c1ab27c032bfa2f8ca7498b41f74499963846 Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Mon, 8 Aug 2022 12:44:44 +0000 Subject: [PATCH 4/6] Travis CI update [skip ci] --- docs/generated/OJP.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/generated/OJP.html b/docs/generated/OJP.html index db715ef82..ccc2fb400 100644 --- a/docs/generated/OJP.html +++ b/docs/generated/OJP.html @@ -436,7 +436,7 @@

OJP - Open API for distributed Journey

-

AddressStructure

descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both

The element contains a sequence of the following elements:

Code

1:1

AddressCode

ID of this address.

PrivateCode

0:*

+PrivateCode

Code of this address in private/foreign/proprietary coding schemes.

Name

1:1

+InternationalText

Name or description of address for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the address that may be appended to the name if enough space is available. F.e. "Crossing with Peterstraße".

AddressDetail

CountryName

0:1

xs:string

Country of the address.

PostCode

0:1

xs:string

Postal code of the address.

TopographicPlaceName

0:1

xs:string

TopographicPlace name of the address. If set it should at least contain the city name.

StopAttributes

WheelchairAccessible

0:1

xs:boolean

Whether this stop is accessible for wheelchair users.

Lighting

0:1

xs:boolean

Whether this stop is lit.

Covered

0:1

xs:boolean

Whether this stop offers protection from weather conditions like rain, snow, storm etc.

9.9. The complex type TopographicPlaceRefStructure

TopographicPlaceRefStructure

Reference to a TopographicPlace

9.10. The toplevel element TopographicPlaceRef

TopographicPlaceRef

+TopographicPlaceRef

Reference to a TopographicPlace

9.11. The complex type TopographicPlaceStructure

TopographicPlaceStructure

[TMv6] A type of PLACE providing the topographical context when searching for or presenting travel information, for example as the origin or destination of a trip. It may be of any size (e.g. County,City, Town, Village) and of different specificity (e.g. Greater London, London, West End, Westminster, St James's).

The element contains a sequence of the following elements:

TopographicPlaceCode

1:1

TopographicPlace ID.

TopographicPlaceName

1:1

+InternationalText

Name or description of TopographicPlace for use in passenger information.

PrivateCode

0:*

+PrivateCode

Code of this TopographicPlace in private/foreign/proprietary coding schemes.

ParentRef

0:1

+TopographicPlaceRef

Reference to a parent TopographicPlace.

ReferredSystemId

0:1

xs:normalizedString

Used in distributed environments (e.g. EU-Spirit). If set, this topographic place resides within the given system (in EU-Spirit "passive server"). This system can be queried for actual places within this topographic place. This is used in an distributed environment for a two-steps place identification. In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

Area

0:1

+Area

Area covered by the locality described as a polygon.

9.12. The complex type PointOfInterestRefStructure

PointOfInterestRefStructure

PointOfInterestCode

Reference to a Point of Interest

9.13. The toplevel element PointOfInterestRef

PointOfInterestRef

+PointOfInterestRef

Reference to a Point of Interest

9.14. The complex type PointOfInterestStructure

PointOfInterestStructure

[corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners.

The element contains a sequence of the following elements:

Code

1:1

PointOfInterestCode

ID of this Point of Interest.

Name

1:1

+InternationalText

Name or description of point of interest for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the point of interest that may be appended to the name if enough space is available. F.e. "Exhibition Center".

PointOfInterestCategory

0:*

+PointOfInterestCategory

Categories this POI is associated with. Order indicates descending relevance.

PrivateCode

0:*

+PrivateCode

Code of this point of interest in private/foreign/proprietary coding schemes.

→‍TopographicPlaceRef

0:1

→‍TopographicPlaceRef

If at least one is set, only place objects within the given localities are allowed.If at least one is set, only place objects within the given localities are allowed.Reference to a TopographicPlace

9.15. The complex type PointOfInterestCategoryStructure

PointOfInterestCategoryStructure

[a view of POINT OF INTEREST CLASSIFICATION in TMv6] categorisation of POINTs OF INTEREST in respect of the activities undertaken at them (defined by key-value-pairs).

The element contains one of the following elements:

a

OsmTag

-1:*

+OsmTag

Open Street Map tag structure (key-value)

b

PointOfInterestClassification

-1:*

xs:string

Classification of the POI (when it is not from OSM). The codification of the classification Id may include de codification source (for example "IGN:[classificationCode]")

9.16. The complex type OsmTagStructure

OsmTagStructure

Structure of an Open Street Map tag.

The element contains a sequence of the following elements:

Tag

1:1

xs:NMTOKEN

Name of Open Street Map tag (amenity, leisure, tourism, bike, ...)

Value

1:1

xs:NMTOKEN

Value for Open Street Map tag (charging_station, hostel, yes, ...)

9.17. The complex type PointOfInterestFilterStructure

PointOfInterestFilterStructure

Filter POIs by category.

The element contains a sequence of the following elements:

Exclude

0:1

xs:boolean

Whether categories in list are to include or exclude from search. Default is FALSE.

PointOfInterestCategory

0:*

+PointOfInterestCategory

These POI categories can be used to filter POIs. If more than one is given the filtering is by logical "OR" (when Exclude=FALSE) and logical "AND" (when Exclude=TRUE).

9.18. The complex type AddressRefStructure

AddressRefStructure

AddressCode

Reference to an Address

9.19. The toplevel element AddressRef

AddressRef

+AddressRef

Reference to an Address

9.20. The AddressDetailGroup group

+

AddressDetailGroup

An address with its name entities

9.9. The complex type TopographicPlaceRefStructure

TopographicPlaceRefStructure

Reference to a TopographicPlace

9.10. The toplevel element TopographicPlaceRef

TopographicPlaceRef

+TopographicPlaceRef

Reference to a TopographicPlace

9.11. The complex type TopographicPlaceStructure

TopographicPlaceStructure

[TMv6] A type of PLACE providing the topographical context when searching for or presenting travel information, for example as the origin or destination of a trip. It may be of any size (e.g. County,City, Town, Village) and of different specificity (e.g. Greater London, London, West End, Westminster, St James's).

The element contains a sequence of the following elements:

TopographicPlaceCode

1:1

TopographicPlace ID.

TopographicPlaceName

1:1

+InternationalText

Name or description of TopographicPlace for use in passenger information.

PrivateCode

0:*

+PrivateCode

Code of this TopographicPlace in private/foreign/proprietary coding schemes.

ParentRef

0:1

+TopographicPlaceRef

Reference to a parent TopographicPlace.

ReferredSystemId

0:1

xs:normalizedString

Used in distributed environments (e.g. EU-Spirit). If set, this topographic place resides within the given system (in EU-Spirit "passive server"). This system can be queried for actual places within this topographic place. This is used in an distributed environment for a two-steps place identification. In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

Area

0:1

+Area

Area covered by the locality described as a polygon.

9.12. The complex type PointOfInterestRefStructure

PointOfInterestRefStructure

PointOfInterestCode

Reference to a Point of Interest

9.13. The toplevel element PointOfInterestRef

PointOfInterestRef

+PointOfInterestRef

Reference to a Point of Interest

9.14. The complex type PointOfInterestStructure

PointOfInterestStructure

[corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners.

The element contains a sequence of the following elements:

PublicCode

1:1

PointOfInterestCode

ID of this Point of Interest.

Name

1:1

+InternationalText

Name or description of point of interest for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the point of interest that may be appended to the name if enough space is available. F.e. "Exhibition Center".

PointOfInterestCategory

0:*

+PointOfInterestCategory

Categories this POI is associated with. Order indicates descending relevance.

PrivateCode

0:*

+PrivateCode

Code of this point of interest in private/foreign/proprietary coding schemes.

→‍TopographicPlaceRef

0:1

→‍TopographicPlaceRef

If at least one is set, only place objects within the given localities are allowed.If at least one is set, only place objects within the given localities are allowed.Reference to a TopographicPlace

9.15. The complex type PointOfInterestCategoryStructure

PointOfInterestCategoryStructure

[a view of POINT OF INTEREST CLASSIFICATION in TMv6] categorisation of POINTs OF INTEREST in respect of the activities undertaken at them (defined by key-value-pairs).

The element contains one of the following elements:

a

OsmTag

-1:*

+OsmTag

Open Street Map tag structure (key-value)

b

PointOfInterestClassification

-1:*

xs:string

Classification of the POI (when it is not from OSM). The codification of the classification Id may include de codification source (for example "IGN:[classificationCode]")

9.16. The complex type OsmTagStructure

OsmTagStructure

Structure of an Open Street Map tag.

The element contains a sequence of the following elements:

Tag

1:1

xs:NMTOKEN

Name of Open Street Map tag (amenity, leisure, tourism, bike, ...)

Value

1:1

xs:NMTOKEN

Value for Open Street Map tag (charging_station, hostel, yes, ...)

9.17. The complex type PointOfInterestFilterStructure

PointOfInterestFilterStructure

Filter POIs by category.

The element contains a sequence of the following elements:

Exclude

0:1

xs:boolean

Whether categories in list are to include or exclude from search. Default is FALSE.

PointOfInterestCategory

0:*

+PointOfInterestCategory

These POI categories can be used to filter POIs. If more than one is given the filtering is by logical "OR" (when Exclude=FALSE) and logical "AND" (when Exclude=TRUE).

9.18. The complex type AddressRefStructure

AddressRefStructure

AddressCode

Reference to an Address

9.19. The toplevel element AddressRef

AddressRef

+AddressRef

Reference to an Address

9.20. The AddressDetailGroup group

From 85c7352696c4f79334a2f6743f6e32fad1e070e7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Sun, 21 Aug 2022 18:09:03 +0200 Subject: [PATCH 5/6] Update OJP/OJP_PlaceSupport.xsd Co-authored-by: Stefan de Konink --- OJP/OJP_PlaceSupport.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OJP/OJP_PlaceSupport.xsd b/OJP/OJP_PlaceSupport.xsd index 30433e8b0..8623803a7 100644 --- a/OJP/OJP_PlaceSupport.xsd +++ b/OJP/OJP_PlaceSupport.xsd @@ -366,7 +366,7 @@ descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both - + ID of this address. From fda7e2fa4e29de5259129ff0087a046b611c0758 Mon Sep 17 00:00:00 2001 From: Travis CI User Date: Sun, 21 Aug 2022 16:10:11 +0000 Subject: [PATCH 6/6] Travis CI update [skip ci] --- docs/generated/OJP.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/generated/OJP.html b/docs/generated/OJP.html index ccc2fb400..ce43c80f6 100644 --- a/docs/generated/OJP.html +++ b/docs/generated/OJP.html @@ -444,7 +444,7 @@

OJP - Open API for distributed Journey

-

AddressDetailGroup

An address with its name entities

AddressDetail

CountryName

0:1

xs:string

Country of the address.

PostCode

0:1

xs:string

Postal code of the address.

TopographicPlaceName

0:1

xs:string

TopographicPlace name of the address. If set it should at least contain the city name.

Street

0:1

xs:string

Street name of the address.

HouseNumber

0:1

xs:string

House number of the address. If none is given, either a crossing street can be given, or the whole street is meant.

CrossRoad

0:1

xs:string

Crossing. This can be used to be more specific without using house numbers.

9.21. The complex type AddressStructure

+

AddressStructure

descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both

The element contains a sequence of the following elements:

Code

1:1

AddressCode

ID of this address.

PrivateCode

0:*

+PrivateCode

Code of this address in private/foreign/proprietary coding schemes.

Name

1:1

+InternationalText

Name or description of address for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the address that may be appended to the name if enough space is available. F.e. "Crossing with Peterstraße".

9.21. The complex type AddressStructure

AddressStructure

descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both

The element contains a sequence of the following elements:

PublicCode

1:1

AddressCode

ID of this address.

PrivateCode

0:*

+PrivateCode

Code of this address in private/foreign/proprietary coding schemes.

Name

1:1

+InternationalText

Name or description of address for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the address that may be appended to the name if enough space is available. F.e. "Crossing with Peterstraße".

AddressDetail

CountryName

0:1

xs:string

Country of the address.

PostCode

0:1

xs:string

Postal code of the address.

TopographicPlaceName

0:1

xs:string

TopographicPlace name of the address. If set it should at least contain the city name.