Skip to main content
Beta! Dokumentasjonen er automatisk generert. Informasjonen kan være ufullstendig og inneholde feil, spesielt skjermbilder og videoer. Se Om hjelpesidene. Vi vil veldig gjerne ha innspill: Kontakt oss via «Fant du det du lette etter?» nederst, i chatten nede til høyre eller på support@placepoint.no – vi svarer så fort vi kan!

Datasets

The Datasets area lets you upload your own lists of properties, buildings or geometry and use them as a reference layer on the map or as an input list for further work. Click Datasets in the left menu to open the panel.

The Datasets panel in Placepoint Fusion

Uploading a dataset

Click Upload dataset at the top of the panel to open the upload dialogue.

The dataset upload dialogue with a drag-and-drop field

Drag the file into the field, or click to select a file. Then work through the wizard: choose the sheet, choose how the rows connect to the map, check the column types and give the dataset a name.

File requirements

RequirementValue
FormatExcel, .xlsx. Other formats must be converted first
File sizeMax 30 MB
RowsUp to 5,000 rows per upload
SheetsOne sheet per upload. You choose the sheet in the wizard
Column namesThe first row with content becomes the column names. The names must be unique
Row contentOne row per property, address or point

Two ways to connect the rows

The wizard asks Choose how to connect your data to our map, and you choose one of two routes:

  • Use your own coordinates or geometry. The file contains the geometry itself, such as latitude and longitude, WKT or GeoJSON. The rows appear on the map without any lookup against Placepoint.
  • Match and connect with Placepoint. The rows are matched against Addresses or Cadastre units based on address or matrikkel columns. The rows then also carry the Placepoint data about the property.

You can use both on the same dataset: matching connects the row to the property, and your own geometry gives you your own drawing on the map.

Your own geometry in the file

FormatWhat a cell looks like
Latitude and longitudeTwo numeric columns, 59.9139 and 10.7522
WKTPOINT(10.7522 59.9139), POLYGON((10.74 59.91,10.75 59.91,10.75 59.92,10.74 59.91))
GeoJSON{"type":"Point","coordinates":[10.7522,59.9139]}

All coordinates are interpreted as WGS84, that is EPSG:4326, in decimal degrees. The upload does not reproject anything. If the data is in EUREF89 UTM zone 32 or 33 (EPSG:25832 and EPSG:25833), which is common for Norwegian map data, you must transform it to WGS84 before you upload it.

You point out the geometry columns yourself in the wizard. The suggestions come from the values in the cells, not from the column name, so a column called Y works just as well as one called breddegrad. Keep the decimals from the source: coordinates rounded to two decimals are not recognised as coordinates, and they are also several hundred metres off.

Matrikkel and address columns

In the Select your address and/or cadastre number columns step you choose what each column contains. You must include either the postal code and postal town, or the municipality number.

Column type in the wizardContent
Municipality codeMunicipality number, four digits, for example 0301
MatrikkelnummerThe whole matrikkelnummer in one column
Registration numberGårdsnummer
Subregistration numberBruksnummer
Lease NumberFestenummer, 0 when the property is not leased
Story NumberSeksjonsnummer, 0 when the property is not divided into sections
Street, Number, Entrance, Postal code, CityThe address split across separate columns

If you have both separate number columns and a matrikkelnummer column, the number columns are used. The matrikkelnummer column is interpreted loosely, so all of these spellings work:

0301 48/99/4
0301-48/99
gnr. 48, bnr. 99
Oslo gnr 48 snr 3

In the same way, addresses can sit in a single free-text column, Karl Johans gate 22, 0159 Oslo, instead of being split into street, number, postal code and postal town. Matching against matrikkel and address applies to Norway.

Excel pitfalls

  • Leading zeros disappear. 0301 becomes 301 if the column is a number. Format the column as text before you paste, or leave the municipality number in the matrikkelnummer column.
  • Decimal separators. Both 59,9139 and 59.9139 are read as numbers. A thousands separator makes the cell invalid as a number.
  • Dates. 2026-09-03, 03.09.2026, 03/09/2026 and 2026/09/03 are recognised, with a time of HH:MM or HH:MM:SS if you include it.
  • One sheet. Formulas that point to other sheets in the workbook are not included. Paste the values before you upload.

Converting from other formats

Shapefile, GeoPackage, GeoJSON, GML, KML and CSV must be converted to .xlsx with the geometry in a WKT column. With GDAL and LibreOffice this takes two steps: reproject to WGS84 and write the geometry as WKT, then convert to Excel:

# Which coordinate system is the file in?
ogrinfo -so -al eiendommer.gpkg

# Reproject to WGS84 and write the geometry as a WKT column
ogr2ogr -f CSV eiendommer.csv eiendommer.gpkg \
-t_srs EPSG:4326 -lco GEOMETRY=AS_WKT

# Point data: two coordinate columns instead of WKT. X is longitude, Y is latitude
ogr2ogr -f CSV punkter.csv punkter.shp \
-t_srs EPSG:4326 -lco GEOMETRY=AS_XY

# CSV to Excel
soffice --headless --convert-to xlsx eiendommer.csv

Without the command line, QGIS does the same: right-click the layer, choose Export, Save Features As, format Comma Separated Value, CRS EPSG:4326 and GEOMETRY set to AS_WKT. Open the CSV file in Excel or LibreOffice and save it as .xlsx.

For small jobs, geojson.io (draw or paste geometry, export GeoJSON) and mapshaper (simplify large polygons, convert between formats) are enough.

If you download from Geonorge, choose GeoJSON or GML rather than SOSI. SOSI has to be converted in a separate step, and all three formats contain the same thing.

You can drop columns you do not need before uploading. The limit of 5,000 applies to rows, not columns, but a narrow dataset is faster to work with in the table.

When something fails

  • The file is rejected at the file step if it is too large, has the wrong format, is corrupt, lacks usable sheets or has too many rows. The message says what was detected and what is supported.
  • Errors at row and cell level are grouped in the list below the table: duplicate column names, missing or extra columns, values that do not fit the column type, duplicate keys and invalid geometry. Click an error to jump to the row or cell it applies to.
  • Rows without a match stay in the dataset, but without a connection to a property or address. You can run the matching again from the dataset settings, under Run matching, with Only unmatched rows or Full dataset. The most common causes are a missing municipality number, a truncated postal code or addresses that have since been renamed.

After upload, the dataset appears in the panel list with its name, row count and date.

If you want to skip the wizard, Claude can do the upload and the matrikkel matching for you through Placepoint Dataset MCP.

Showing the dataset on the map

Click a dataset in the list to open it. The properties or geometry in the dataset are shown as a separate layer over the background map. Change visibility with the toggle next to the dataset name.

When a dataset is active, a toolbar of row actions appears:

An active dataset with the toolbar of actions

IconAction
PlusDraw new geometry into the dataset
FilterFilter the rows in the dataset
TableOpen the dataset as a table
PaletteStyling: colour, size, labels, clustering and heat maps
CogSettings: name, column mapping, matching and locking
UploadUpdate the dataset with a new file
ToggleShow or hide the dataset on the map

Styling

The palette icon opens the style panel. It has five tabs, and the choices are saved on the dataset, so everyone in the project sees the same map layer.

TabWhat you control
StylingColour. One colour for the whole dataset, one colour per value in a column (categorical), or a colour scale over a numeric column. Categorical values are listed with the number of rows per value, and values without a match are collected in an Others group
SizePoint size, fixed or scaled by a numeric column
LabelText on the map from a column, with text colour, font size, font weight and halo
ClusteringMerge nearby points into clusters, with a minimum and maximum cluster size and the count shown in the cluster
VisibilityWhether the layer is always visible, regardless of zoom level

The heat map is a separate option with a colour scale and radius. While it is on, the heat map overrides the colour and size settings, and the panel tells you so.

If you need your own symbols, upload icons to the symbol library and use them instead of the default symbols.

For numeric columns, the colour scale shows a histogram of the values, so you can see where rows actually sit before you choose the breaks.

The table

The table icon opens the dataset at the bottom of the screen. You can drag the panel up to almost full height. The table has one tab per content type:

TabContent
ExternalThe rows as they came from your file, with your own columns
AddressThe addresses the rows were matched to
CadastreThe matrikkelenhet records the rows were matched to
BuildingThe buildings, when the rows are matched to buildings

You can sort and move columns, and a toggle shows only the rows you have selected on the map. The number of rows shown appears at the bottom. Click a row to open the details, where you can also change the values in your own columns.

Filtering the rows

The filter icon filters on column values. The filter is saved on the dataset under Dataset filter, and active filters appear as pills above the table, so you can see why the row count has dropped. The map layer and the table show the same selection.

Exporting

Export to Excel downloads the rows. You choose between:

  • Export with customized columns and filters, the dataset as it looks now, with your column choices and filters.
  • Export with original columns and no filters, the whole dataset as it was uploaded.

If you have selected rows on the map, only the selected rows are exported.

Drawing and editing geometry

The plus icon lets you draw a point, line or area straight into the dataset, without uploading a file. Existing geometry can be moved and changed in the same way. The rows you draw get the same columns as the rest of the dataset.

Updating the dataset with a new file

The upload icon starts the update wizard. It follows the same steps as a new upload: choose the file, choose the sheet, review the preview and finish. New rows are matched as in the first upload, and the old rows keep their connection.

Running matching again

The settings include Run matching, with two options:

  • Only unmatched rows, try again on the rows that did not get a match.
  • Full dataset, match all the rows again, for example after you have corrected an address column.

Every run is saved. View report shows the runs with the date, the number of rows from the dataset, matches per type, precision and how long the run took.

If you turn matching off in the settings, the matches you have are kept, but new rows are not connected.

Managing datasets

From the panel list you can:

  • See the row count and last updated date for each dataset.
  • Click a dataset to open its content and change the styling.
  • Rename the dataset, or delete it.

The cog icon on the active row opens the settings for the dataset, where you adjust the name, display and customisation:

Settings for a dataset

A dataset can be locked. If it is set to read-only, the rows can be read and shown on the map, but not changed. If uploading is turned off, no one can upload a new file over it. This is useful for a dataset several people work against, or one that is kept up to date from Claude through Placepoint Dataset MCP.

Access

A dataset belongs to a project. Everyone with access to the project sees the datasets in it, with the same styling and filters. The settings show who has access to each dataset.

Limits and rules per organisation

The default limit is 5,000 rows per upload, but it is not fixed for everyone. Placepoint can set a higher row limit on a single dataset when you have a larger list to work with.

The same goes for the rules the upload uses: what should stop an upload, what should only be reported as a note, and how values are recognised as numbers, dates or geometry. The rules sit at four levels, from general to specific: the default setup, your organisation, the project and the individual dataset. The most specific level wins, and the rules are locked when the upload starts, so they do not change part-way through a job.

If you have a file format with its own conventions, for example dates written in a fixed way or code fields that should be read as text rather than numbers, your contact at Placepoint can have it set up for your organisation instead of each user having to correct the file first.

What datasets are used for

Use caseDescription
Reference layer on the mapShow your own properties or locations over the background map for geographic orientation.
Bulk lookupPull property data for many properties in one step by opening each match from the list.
StylingChange the colour, size and icon type of the points to tell different types of location apart.

Typical use cases

Prospect list from a broker report. Upload a CSV of matrikkelnummer values from a broker report and show all the properties as a layer on the map for a quick geographic assessment.

Store locations. Upload addresses or coordinates for shops, offices or other locations and analyse them against demographics, population or the competitive situation through the map layers.

Portfolio overview. Import a defined list of commercial properties from an internal register and use it as a reference when you pull ownership and transactions from the property panel.

Tips

  • Keep the columns in the Excel file in the shape the wizard expects. Duplicate or empty column names stop the upload.
  • A dataset belongs to the project it was uploaded in. Colleagues with access to the project see it.

See also

  • Tags, an alternative for collecting and filtering individual properties without uploading a file.
  • Map layers, thematic datasets from Placepoint and public registers.
Beta! Dokumentasjonen er automatisk generert. Informasjonen kan være ufullstendig og inneholde feil, spesielt skjermbilder og videoer. Se Om hjelpesidene. Vi vil veldig gjerne ha innspill: Kontakt oss via «Fant du det du lette etter?» nederst, i chatten nede til høyre eller på support@placepoint.no – vi svarer så fort vi kan!