GSD-Property Map database does not contain entities for areas, areas are dynamically created from the lots found in the GSD-Property Map database by grouping lots according to the Area creation strategy chosen in the type-specific import settings. Table 1 shows the available options and their effects on the creation of lots. The geometry of an area is calculated as the geometrical union of all lots that make up the area.
Strategy |
Description |
Community name + District name |
This strategy in this list will create more blocks and is therefore better suited for densely populated areas. Technically this creates blocks by grouping lots like this GROUP BY IIF(CHARINDEX(':', BLOCKENHET) > 0, |
Community name + District name |
This strategy will create less but bigger blocks and is therefore better suited for rural areas. Group BY LAN_KOD, KOMMUNKOD, KOMMUNNAMN, TRAKT |
Table 1: Block creation strategies
Which data from the source will be processed
The geometry of an area is the geometrical union all lots that make up that area. Only those lots are processed, that are intersecting with the given filter-geometry. It might therefore be that imported areas are smaller than the real world areas.
Naming of features in Redbex
Areas will be named depending on your selected Area creation strategy:
Strategy |
Description |
Community name + District name + Block name |
<CommunityName> <District name> <Block name> |
Community name + District name |
<CommunityName> <District name> |
Table 1: Naming of Importing areas features depending on the selected area creation strategy
How areas are matched against existing Redbex features
During the import the importer tries to match the areas in the GSD database (that are in the selected filter-geometry) to feature of type Landregister Area in Redbex. The importer will only try to find matches for features that are within the selected filter-geometry. The matching is done by comparing the name generated from the data in the GSD database to the feature name in Redbex.
