Support
For the Nivel Regulator
Support
For the Nivel Regulator
Support
For the Nivel Regulator
How to Get Started with Nivel Regulator
Even though the Nivel Regulator is quite intuitive to understand, we are here making it even easier to get started with short step-by-step guides to different parts of the Regulator.
Creating a zone
Click on "Zones" on the top left.
Then on the "…" icon and "Create a new zone"
Once you're in this menu, you can then click on the map to decide where the zone should go. There are also many different policies which a zone can have. Like parking forbidden or even just a simple analysis zone. Remember to set the zone to active!
Creating dedicated parking areas
Click on "Parking areas" in the top left. If you are still in the "Zones" tab, you need to exit this menu.
Click on the "…" icon and "Create new parking area"
Once you're in the menu, give the parking area name and set it to active. Notice that there are no options to edit the parking area until it has been saved.
Once saved, upon hovering over each of the fields in the box you will see a pencil icon. Click this one and do the edits necessary.
Difference between parking area and a zone
A parking area and a zone can sound pretty similar. However, once a parking area is created it is not possible to turn that into a zone that is a slow zone or the like. A zone and a parking area are different. In other words, if a parking area should be replaced by a zone - the parking area needs to be deleted and a zone created.
A parking area will have the same fee as the zone which it exists in. If a Street fee has been set, the parking spot will have the same. A way to solve this is to create a smaller zone by the parking area to have a different Street fee there.
Sorting zones
After a while, there might be many zones in the Regulator. In this case you want for the larger zone (for example the city border) to be at a lower priority layer than the rest - if not, you will be unable to click on the smaller zones.
How to Get Started with Nivel Regulator
Even though the Nivel Regulator is quite intuitive to understand, we are here making it even easier to get started with short step-by-step guides to different parts of the Regulator.
Creating a zone
Click on "Zones" on the top left.
Then on the "…" icon and "Create a new zone"
Once you're in this menu, you can then click on the map to decide where the zone should go. There are also many different policies which a zone can have. Like parking forbidden or even just a simple analysis zone. Remember to set the zone to active!
Creating dedicated parking areas
Click on "Parking areas" in the top left. If you are still in the "Zones" tab, you need to exit this menu.
Click on the "…" icon and "Create new parking area"
Once you're in the menu, give the parking area name and set it to active. Notice that there are no options to edit the parking area until it has been saved.
Once saved, upon hovering over each of the fields in the box you will see a pencil icon. Click this one and do the edits necessary.
Difference between parking area and a zone
A parking area and a zone can sound pretty similar. However, once a parking area is created it is not possible to turn that into a zone that is a slow zone or the like. A zone and a parking area are different. In other words, if a parking area should be replaced by a zone - the parking area needs to be deleted and a zone created.
A parking area will have the same fee as the zone which it exists in. If a Street fee has been set, the parking spot will have the same. A way to solve this is to create a smaller zone by the parking area to have a different Street fee there.
Sorting zones
After a while, there might be many zones in the Regulator. In this case you want for the larger zone (for example the city border) to be at a lower priority layer than the rest - if not, you will be unable to click on the smaller zones.
How to Get Started with Nivel Regulator
Even though the Nivel Regulator is quite intuitive to understand, we are here making it even easier to get started with short step-by-step guides to different parts of the Regulator.
Creating a zone
Click on "Zones" on the top left.
Then on the "…" icon and "Create a new zone"
Once you're in this menu, you can then click on the map to decide where the zone should go. There are also many different policies which a zone can have. Like parking forbidden or even just a simple analysis zone. Remember to set the zone to active!
Creating dedicated parking areas
Click on "Parking areas" in the top left. If you are still in the "Zones" tab, you need to exit this menu.
Click on the "…" icon and "Create new parking area"
Once you're in the menu, give the parking area name and set it to active. Notice that there are no options to edit the parking area until it has been saved.
Once saved, upon hovering over each of the fields in the box you will see a pencil icon. Click this one and do the edits necessary.
Difference between parking area and a zone
A parking area and a zone can sound pretty similar. However, once a parking area is created it is not possible to turn that into a zone that is a slow zone or the like. A zone and a parking area are different. In other words, if a parking area should be replaced by a zone - the parking area needs to be deleted and a zone created.
A parking area will have the same fee as the zone which it exists in. If a Street fee has been set, the parking spot will have the same. A way to solve this is to create a smaller zone by the parking area to have a different Street fee there.
Sorting zones
After a while, there might be many zones in the Regulator. In this case you want for the larger zone (for example the city border) to be at a lower priority layer than the rest - if not, you will be unable to click on the smaller zones.
Frequently Asked Questions
How can we effectively monitor the location of operators' vehicles in our regulatory system to address challenges of non-compliance with vehicle location requirements in specific areas?
We have implemented a functionality in our regulation system that registers whether the vehicles are placed out by the operators or by the users at the end of a trip. This registered information gives us the basis for generating statistics that show whether operators are complying with the requirements set.
How can we best determine which data standard to use for future license periods? How can we ease the transition for operators from MDS 1.0 to MDS 2.0?
We recommend starting with MDS 1.0 as a starting point. However, we expect operators to gradually migrate to MDS 2.0 with a notice period of either 30 or 90 days. We have already started the implementation of MDS 2.0 in our car sharing project and we plan to support both standards during a transition period. The most significant difference between Agency 1.0 and 2.0 is that Provider and Agency will be more similar, which is expected to significantly improve the quality of the data. Operators with data science skills should be able to complete this migration quickly.
How can we easily access API documentation and extract data from the Nivel platform to data stream.
All necessary documentation for Agency data from the operators can be found here at the following link: https://github.com/openmobilityfoundation/mobility-data-specification/tree/main/agency.
The most commonly used version at the moment is 1.0.0. Regarding a standard API for data extraction from our system to a data lake, we have not currently implemented such a solution. However, we are willing to create a collaboration to establish a suitable API.
Frequently Asked Questions
How can we effectively monitor the location of operators' vehicles in our regulatory system to address challenges of non-compliance with vehicle location requirements in specific areas?
We have implemented a functionality in our regulation system that registers whether the vehicles are placed out by the operators or by the users at the end of a trip. This registered information gives us the basis for generating statistics that show whether operators are complying with the requirements set.
How can we best determine which data standard to use for future license periods? How can we ease the transition for operators from MDS 1.0 to MDS 2.0?
We recommend starting with MDS 1.0 as a starting point. However, we expect operators to gradually migrate to MDS 2.0 with a notice period of either 30 or 90 days. We have already started the implementation of MDS 2.0 in our car sharing project and we plan to support both standards during a transition period. The most significant difference between Agency 1.0 and 2.0 is that Provider and Agency will be more similar, which is expected to significantly improve the quality of the data. Operators with data science skills should be able to complete this migration quickly.
How can we easily access API documentation and extract data from the Nivel platform to data stream.
All necessary documentation for Agency data from the operators can be found here at the following link: https://github.com/openmobilityfoundation/mobility-data-specification/tree/main/agency.
The most commonly used version at the moment is 1.0.0. Regarding a standard API for data extraction from our system to a data lake, we have not currently implemented such a solution. However, we are willing to create a collaboration to establish a suitable API.
Frequently Asked Questions
How can we effectively monitor the location of operators' vehicles in our regulatory system to address challenges of non-compliance with vehicle location requirements in specific areas?
We have implemented a functionality in our regulation system that registers whether the vehicles are placed out by the operators or by the users at the end of a trip. This registered information gives us the basis for generating statistics that show whether operators are complying with the requirements set.
How can we best determine which data standard to use for future license periods? How can we ease the transition for operators from MDS 1.0 to MDS 2.0?
We recommend starting with MDS 1.0 as a starting point. However, we expect operators to gradually migrate to MDS 2.0 with a notice period of either 30 or 90 days. We have already started the implementation of MDS 2.0 in our car sharing project and we plan to support both standards during a transition period. The most significant difference between Agency 1.0 and 2.0 is that Provider and Agency will be more similar, which is expected to significantly improve the quality of the data. Operators with data science skills should be able to complete this migration quickly.
How can we easily access API documentation and extract data from the Nivel platform to data stream.
All necessary documentation for Agency data from the operators can be found here at the following link: https://github.com/openmobilityfoundation/mobility-data-specification/tree/main/agency.
The most commonly used version at the moment is 1.0.0. Regarding a standard API for data extraction from our system to a data lake, we have not currently implemented such a solution. However, we are willing to create a collaboration to establish a suitable API.