Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PassengerBeacon in OJP #195

Open
ue71603 opened this issue May 19, 2022 · 5 comments
Open

PassengerBeacon in OJP #195

ue71603 opened this issue May 19, 2022 · 5 comments
Labels
documentation enhancement New feature or request
Milestone

Comments

@ue71603
Copy link
Contributor

ue71603 commented May 19, 2022

We introduced a new PassengerBeaconEquipment in NeTEx. This is for Accessibility purposes. I think we should adapt TripResponse and TripInformationResponse to also be able to transfer information on the Beacon. Or should this be done via Siri?

@ue71603 ue71603 added enhancement New feature or request documentation labels May 19, 2022
@ue71603 ue71603 added this to the v2.0 milestone May 19, 2022
@ue71603
Copy link
Contributor Author

ue71603 commented Aug 23, 2022

Christophe: The existence of a beacon is possible. depending what level is provided in the journey description. Or we could refer to the reference data. We don't have all equipment in there. Otherwise go to NeTex.
Matthias: Some Equipment are there.
Christophe: google does enrichment from the map. beacon on the map would help with stationary.

@ue71603 ue71603 modified the milestones: v2.0, later Aug 23, 2022
@Aurige
Copy link
Contributor

Aurige commented Sep 30, 2022

I started investigating however, I came up with more questions than answer, so a short additional discussion may be needed:

  1. the first point is that it may be needed to complement the NeTEx PR: for example in the BeaconProtocolEnumeration there is an Eddystone value which correspond to a technology that is not available anymore - https://en.wikipedia.org/wiki/Eddystone_(Google) - and the VDV431 value is a bit unclear to me ... and we may need to mention AltBeacon or GeoBeacon ...
  2. I'm not sure about what the functional expectation is in OJP about beacons: just mention that some are available in some PathLinks ? or provide more details like the technology/protocol used, the beacon locations, etc. ? My own take would be to just mention the availability of beacons (and refer to the static data for more details)

@ue71603
Copy link
Contributor Author

ue71603 commented Oct 1, 2022

@Aurige

  • The NeTEx PR we would need to update with the values that you researched.
  • Functional expectations. Existence I guess and id, if possible. Probably mainly a link to static data.

@normanoffel
Copy link

As @Aurige says, I would also question the current use within OJP and I personally would probably wait and see what SIRI does with it. With the information above about the enumeration, it seems a bit neglected then in NeTEx as well and may be changed in the rather near future as well. So I also assume that there will be references to beacons at best if at all in SIRI or OJP. What is the information used for if it's part of NeTEx? Does it need to be part of SIRI or OJP? Because this information about Beacons is rather static, I would think that it probably won't be part of SIRI but only of NeTEx.

@ue71603
Copy link
Contributor Author

ue71603 commented Oct 18, 2022

Aurige: It's passenger beacon bluetooth or wifi. We should call them passenger beacon. Indoor location system. Multiple protocols. The difficult point is, that it is not stabilised. Precoded values would not help.

@ue71603 ue71603 removed this from the later milestone Oct 18, 2022
@ue71603 ue71603 added this to the later milestone Oct 18, 2022
@ue71603 ue71603 modified the milestones: later, v2.1 Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants