Zoning Plan - SOSI Construction¶
Construction of Zoning Plan¶
The procedure in Gemini Terrain is based on the guide for digital plans regarding construction principles for digital production of zoning plans.
Construction sequence:
- Road geometry
- Boundary lines for purpose areas
- The plan's outer boundary
We have created a suggested procedure for Gemini Terrain. If we follow this procedure, we can deliver a constructed plan proposal in complete form, i.e., correct SOSI file with surfaces and properties (SOSI level 4).
Properties and drawing rules in the templates in Gemini Terrain are adapted to the national product specification for land use plans and digital plan register.
You can read more about the product specification on the Ministry of the Environment's websites.
Procedure in Gemini Terrain¶
Procedure
- Import of map base
- Create layers for the plan
- Construct centerline for roads
- Construct lines for land use purposes
- Construct lines for consideration zones
- Construct lines for plan area
- Create polygons
- Create legal lines and points and annotations
This is a suggested procedure. In practice, we will often jump back and forth between the various steps. The procedure also does not cover plans with multiple vertical levels. We refer to the national product specification for further description.
How we create presentation drawings for the plan is described in more detail in the section Presentation Drawings.
Step 1: Import of Map Base¶
We import the data base to relevant application layers. We can choose to import the data base with minimum layer division or full layer division, i.e., follow the SOSI object catalog's division, for example:
- Buildings
- Roads
- Property boundaries
- And so on
This is described in more detail under the section on Application Layers.
Step 2: Create Application Layers for the Plan¶
The legislation operates with several layers in zoning plans.
Various layers included in a zoning plan
From the figure, we see that the plan boundary is always equal to the purpose boundary. This means that in the plan's outer boundary, at least two lines with the same course lie. In addition, lines from consideration zones may occur.
When we create a plan in Gemini Terrain, it is most appropriate to create the application layers we need. The following templates are created for the layers that can appear in a plan:
- Rp45_AngittHensynsoner.al_
- Rp45_Arealformål.al_
- Rp45_Bestemmelseområder.al_
- Rp45_Båndleggingsoner.al_
- Rp45_Detaljeringsoner.al_
- Rp45_Faresoner.al_
- Rp45_Gjennomføringsoner.al_
- Rp45_Infrastruktursoner.al_
- Rp45_Linjer_punkt_og_påskrift.al_
- Rp45_Planområde.al_
- Rp45_Regulerthøyde
- Rp45_Sikringsoner.al_
- Rp45_Støysoner.al_
When you select a template, the program suggests the same name for the layer. Here it may be appropriate to replace Rp45 with the name or ID of the plan.
Step 3: Construct Centerline for Roads¶
Plan construction starts with all roads. We must always have control over the road geometry, i.e., road centerline. Road centerline should lie in the layer Rp45_Linjer_punkt_og_påskrift.
Illustration of centerlines
The guide says: "If the terrain is difficult, cutting and filling should be calculated and shown on the plan map". The strength of Gemini Terrain is that we can also perform complete design of roads and intersections with calculation of cutting and filling volumes. We then just take hold of the centerline and create a road project for this. This is described in more detail in the section Use of 3D during construction.
At the intersection point between centerlines, we must snap the start point on the secondary road to a point on the primary road. For lines in this layer, we recommend snapping to other lines without splitting them. It is an advantage that, for example, centerlines for roads are continuous, among other things, with a view to creating parallels.
Legal information we can attach to the lines is shown in the table below.
| Property | Value |
|---|---|
| OBJTYPE | RpJuridiskLinje |
| PLANID | |
| KOMM | |
| RPJURLINJE | |
| VERTNIV | |
| FØRSTEDIGITALISERINGSDATO | |
| OPPDATERINGSDATO | |
| MÅLEMETODE | |
| NØYAKTIGHET |
Step 4: Construct Lines for Land Use Purposes¶
In step 4, we create the lines that will form boundaries for all purposes. We do this on the application layer Rp45_Arealformål. Some purpose boundaries will be determined by the road geometry. Others will be determined by existing lines in the map, for example property boundaries. It is therefore important that we copy lines from the base map where these are determining for the purpose (alternatively we can snap lines). For this, we use the general functions for copying data from one layer to another.
Purpose boundaries
Legal information we can attach to the lines is shown in the table below. As a minimum, we must enter object type:
| Property | Value |
|---|---|
| OBJTYPE | RpFormålGrense |
| FØRSTEDIGITALISERINGSDATO | |
| OPPDATERINGSDATO | |
| MÅLEMETODE | |
| NØYAKTIGHET |
The entire plan area should contain a fully covering mosaic of land use purposes. All areas should have a specified use. It is important that the lines on this layer have topology structure. This is necessary for polygonization and later export of data to SOSI to go smoothly. We must therefore build up the lines according to certain guidelines. We must keep this in mind when we construct the lines.
Topology is described in more detail in a separate chapter. This also applies to steps 5 and 6.
Step 5: Construct Lines for Designation Areas and Consideration Zones¶
In step 5, we create lines for the consideration zones. We do this on relevant application layers:
- Rp45_AngittHensynsoner
- Rp45_Bestemmelseområder
- Rp45_Båndleggingsoner
- Rp45_Detaljeringsoner
- Rp45_Faresoner
- Rp45_Gjennomføringsoner
- Rp45_Infrastruktursoner
- Rp45_Sikringsoner
- Rp45_Støysoner
Legal information we can attach to the lines is shown in the table below. As a minimum, we must enter object type:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpAngittHensynGrense RpBåndleggingGrense RpDetaljeringGrense RpFareGrense RpGjennomføringGrense RpInfrastrukturGrense RpSikringGrense RpStøyGrense |
Each consideration zone has its own object type |
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO | ||
| MÅLEMETODE | ||
| NØYAKTIGHET |
Step 6: Construct Lines for Plan Surface¶
In step 6, we create lines for the plan's boundary on the application layer Rp45_Planområde. We create the plan's boundary as a continuous line along the outermost purpose lines. Plan boundary and purpose boundary should coincide. We can do this by marking the relevant lines in Rp45_Arealformål and using the general functions for Copy and Paste.
Plan boundary
Legal information we can attach to the lines is shown in the table below. As a minimum, we must enter object type:
| Property | Value |
|---|---|
| OBJTYPE | RpGrense |
| FØRSTEDIGITALISERINGSDATO | |
| OPPDATERINGSDATO | |
| MÅLEMETODE | |
| NØYAKTIGHET |
Step 7: Create Polygons¶
Now all the lines in the plan are finished constructed. The next step is to create polygons for all purposes, consideration zones, and the plan's boundary. The plan's boundary is a continuous line identical to the outermost purpose lines.
The chapter on polygonization describes the method in detail. It also discusses what you must do if you edit points in lines and polygons.
When the polygons are created, we must attach properties to them. Which properties we can attach to the plan area, purpose areas, and consideration zones are defined in the SOSI standard. When the properties are entered, the surfaces are presented according to the standard.
Land use purposes and consideration zones are polygonized
Information linked to plan area:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| PLANTYPE | Plan type | |
| PLANSTAT | Plan status | |
| VERTNIV | Vertical level for the plan | |
| LOVREFERANSE | Legal reference | |
| PLANBEST | Plan provisions | |
| PLANNAVN | Plan name | |
| IKRAFT | Entry into force date | |
| LOVREFERANSEBESKRIVELSE | ||
| GJENNOMFØRINGSFRIST | ||
| FORSLAGSSTILLERTYPE | ||
| VEDTAKENDELIGPLANDATO | ||
| KUNNGJØRINGSDATO | ||
| OPPRINNELIGPLANID | ||
| OPPRINNELIGADMINISTRATIVENHET | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO | ||
| PROSESSHISTORIE | ||
| INFORMASJON | ||
| LINK |
Information linked to purpose areas:
| Property | Value | Description | Note |
|---|---|---|---|
| OBJTYPE | RpArealformålOmråde | ||
| PLANID | Plan identification | ||
| KOMM | Municipality number | ||
| RPAREALFORMÅL | Zoning purpose | ||
| VERTNIV | Vertical level for the plan | ||
| EIERFORM | |||
| UTNTYP | Degree of utilization | UTNTYP, UTNTALL and UTNTALL_MIN give the property UTNYTT in exported SOSI file | |
| UTNTALL | Numerical value for degree of utilization | ||
| UTNTALL_MIN | |||
| BESKRIVELSE | |||
| FELTNAVN | Field designation | ||
| UTEAREAL | Requirement for outdoor area | ||
| BYGGVERK | Building provisions | ||
| AVKJ | Access provisions | ||
| FØRSTEDIGITALISERINGSDATO | |||
| OPPDATERINGSDATO |
Information linked to security zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpSikringOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPSIKRING | Security | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to hazard zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpFareOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPFARE | Hazard | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to noise zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpStøyOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPSTØY | Noise | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to specified consideration zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpAngittHensynOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPANGITTHENSYN | Specified consideration | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to infrastructure zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpInfrastrukturOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPINFRASTRUKTUR | Infrastructure | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to implementation zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpGjennomføringOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPGJENNOMFØRING | Implementation | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to detailing zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpDetaljeringOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPDETALJERING | Detailing | |
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Information linked to restriction zones:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpBåndleggingOmråde | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPBÅNDLEGGING | Restriction | |
| BÅNDLAGTFREMTIL | ||
| HENSYNSONENAVN | ||
| BESKRIVELSE | ||
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO |
Step 8: Create Legal Lines, Points and Annotations¶
Legal lines:
In step 8, we enter legally binding lines and points in the application layer Rp45_Linjer_og_punkt_og_påskrift. These are not included in surface formations. Examples of lines are shown in the figure below (regulated centerline, building line, regulated lot boundary, measurement line).
Legal lines
The table below shows which codes exist for zoning plans in the SOSI standard. Codes in emphasized italics are used only where the plan establishes a legally binding placement, so that changes to these must be treated as minor significant changes.
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpJuridiskLinje | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPJURLINJE | Legal line type | |
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO | ||
| MÅLEMETODE | ||
| NØYAKTIGHET |
Legal points:
| Property | Value | Description |
|---|---|---|
| OBJTYPE | RpJuridiskPunkt | |
| PLANID | Plan identification | |
| KOMM | Municipality number | |
| RPJURPUNKT | Legal point type | |
| VERTNIV | ||
| FØRSTEDIGITALISERINGSDATO | ||
| OPPDATERINGSDATO | ||
| MÅLEMETODE | ||
| NØYAKTIGHET |