Antwerp - Presentation of measures
-
- ANT_MS2: Realtime information for passengers
-
- ANT_MS3: Multimodal journey planner app
-
- ANT_MS4: Traffic management / PT prioritization
-
@stijnvernaillen Hi! Here are few question for Antwerp regarding Multimodal hub since Šibenik is going to establish one during SPINE project- what components does your multimodal hub include and how did you set it up in terms of determining what are the important items that were needed to be included? Do you have possibility to track how many users are using it and in what ways?
-
Hi, City Zilina has a question for Lead City Antwerp:
- have you got already any expectations or even data about whether the introduction of smart parking management will lead to less interest in parking (and car using) and therefore people prefer more sustainable mobility? How inhabitants react to introduction of smart parking management?
-
Hi, Rouen has also a few questions for Antwerp.
Map components and accessibility :
To ensure a clear and user-friendly interface, could you elaborate on the specific cartography components and data layers planned for the Multimodal Journey Planner App?
Will there be options for users to customize the level of detail displayed on the map ?
Can you describe the functionalities planned for users to personalize their map experience?
Will this include options to adjust map features like color schemes, font sizes, or other accessibility settings?
Will there be features like screen reader compatibility, high-contrast themes, or audio guidance for navigation to improve the experience for the users with disabilities ?Data Quality :
To ensure accurate and reliable journey planning, how will you approach data quality within the application?
Are there specific strategies in place to maintain up-to-date information on public transportation schedules, real-time disruptions, and accessibility features?RT info and security :
Considering the importance of real-time data for the users, what kind of measures related to cybersecurity are being implemented ? -
We would like to thank Antwerp for the information they gave us about the displays and we would like to confirm that these displays are simple led screens , whose cost is covered by SPINE's Budget
-
-
We would like to ask if the Journey Planner app can be used by people with disabilities and how
-
And finaly, to all the partners we would like to ask: on the platform OBB do we only discuss the issues of SPINE , or also the vision of each body for mobility in the city ?
Also we would like you to confirm to us that in the section of Heraklion the local stakeholders can participate in the discussion
-
-
@antonia-buric: we used to have a clearly defined set of features per type of hub but while rolling out and designing the first hubs it became clear that every locations requires a custom approach. It all depends on the environment, other services already available in the neighbourhood, what can be moved and what cannot be moved. I'll see if I can find the list of features and typologies that we used to have.
We're not tracking users. However, we do have our shared mobility trip data and we do yearly surveys on usage. Some questions are linked to multimodality.@Miroslava: we're not really counting on smart parking management to switch behaviour. I personally think the smartest parking management measure we took is not allowing on-street parking for visitors in the old town. (and paid on-streek parking in large areas of the city). Other measures like showing available on-street parking spaces and guiding car users to those spots only makes it easier for car users, not harder. The smartest parking management strategy is to make it difficult for car users as early as possible in their trip. So car to closest trainstation and then into the city by train is better then car to P&R close to the city and then tram.
@Christophe: There's a list of +70 data layers we use for the various modes. Beside that we use the network data from OpenStreetMap and our routeplanner is also based on this. For map visualisation and theming we use Mapbox Studio. Users are able to turn on and off some layers. As a city we can also ensure that some layers we think are essential are always on. This can be P&R or mobility hubs. By showing them we make people aware about the options. Past the possibility of turning on and off layers, we don't give the user more options to theme a map. It is a very complex thing and most users won't use it. We do have an accessibility map style that makes everything more readable (still needs finetuning). In our app we do have guidance and navigation. It is possible to turn off or on the sound of the navigation. Everything is available in 4 languages and the website should be screenreadable. For the map component we're still looking into ways to make it screen readable. To my knowledge there's not a single application that has managed to do this. You can now check it out on the live site: www.sna.be
We get our data directly from the mobility providers and often it's the same source as they use themselves. We don't further try to improve the data.
I don't completely agree with the importance of RT-data for the user. In a good mobility system, the user does not need realtime data. Beside that, the whole IT-system of the city of Antwerp has been rebuild from scratch after a cyberattack last year. Even the design of a simple button on a website has been checked to ensure that it's not possible to gain access through such things.
@MARIA-VASILAKI : the screens we're installing are eInk screens like ereaders. The reason for this is that they can operate for a reasonably long time on batteries without the need to connect the infrastructure to the net. This makes it easier for us to install the screens anywhere we want on the public domain without having to open the ground to make an electric connection. As part of the service contract, the company installing the screen, replaces the batteries when needed. The cost of all this is covered in the SPINE budget.
The journey planner app, as well as the rest of the website is WCAG approved. It is useable with screenreaders and alike. However, making maps suitable and 100% WCAG proof is something nobody has found a solution for yet. I've seen a thesis on the use of AI to provide a spoken output of what is shown on the map but it stays tricky. We did include an accessibility layer in which we created a seperate more readable baselayer. We're still planning to fine-tune it with the community more but currently the focus is on improving the accessibility data we have and show to the user.
On the topic of discussing wider topics then spine or involving local stakeholders I think that's the whole goal of this platform. Sharing knowledge, not only during meetings but also through this platform.
-
This post is deleted!
