Organised Editing/Activities/Natvaro

Nätvaro – Organised Editing Activity

Organisation: Nätvaro AB (https://natvaro.se)
Contact: info@natvaro.se
Country: Sweden
Area: Sweden
Start date: 2026-03
Status: Pre-launch / internal testing

Purpose

Nätvaro helps local businesses in Sweden keep their public information accurate across platforms, including OpenStreetMap.

For OpenStreetMap, Nätvaro only works with business-owner provided first-party data that is suitable for OSM contribution. The goal is to improve the accuracy of business POI information in Sweden through assisted editing with human review.

Workflow

1. A business owner enters or confirms their information in the Nätvaro platform.
2. The system evaluates each field against an internal eligibility policy and blocks fields that are not suitable for OSM contribution.
3. The system searches for an existing OSM candidate using Overpass API and internal matching logic based on proximity and name similarity.
4. A trained human operator reviews the proposed match and proposed tag changes in an internal review queue before any edit is submitted.
5. If there is a sufficiently confident node match and the operator approves, a changeset is submitted via the OSM API v0.6 using OAuth 2.0.
6. If no sufficiently confident direct edit is appropriate, an OSM Note may be created instead as a fallback.
7. Every submitted edit or note is logged internally for traceability and follow-up.

Data source

All data used for OSM contributions comes directly from the business owner (first-party data). No Google Business Profile data or other third-party directory/platform data is used for OSM edits.

Data used for OSM contributions is intended to be first-party, lawful to contribute, and independently verifiable where applicable.

Hashtag

The primary hashtag used in changeset comments for this activity is:

#NatvaroPOI

Tags edited

Edits are limited to business-owner provided data such as:

• name
• phone / contact:phone
• website / contact:website
• opening_hours
• addr:street
• addr:housenumber
• addr:postcode
• addr:city
• contact:email (public business email only, such as info@)

Initial scope is limited to node-based POI edits. Ways and relations are not part of the first version.

Changeset attribution

Changeset comments for this activity include:

• a human-readable summary of the edit
• the hashtag #NatvaroPOI
• a link to this wiki page

Example format:

Update POI fields for Example Business in Stockholm #NatvaroPOI https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/Natvaro

Additional tags may include:

• source=owner
• created_by=Nätvaro

Timeframe

This activity is currently in pre-launch / internal testing.

A public community notice will be posted before production start. Production edits will begin no earlier than two weeks after that public notice. The activity will remain in pre-launch status until the first real supervised production edits have been completed.

Tools and data sources

The following tools and data sources are used:

• Nätvaro internal admin/review queue
• Internal field eligibility policy for OSM contribution
• Overpass API for candidate matching and review preparation
• OSM API v0.6 for approved edits
• OAuth 2.0 for authenticated OSM write access
• OSM Notes as fallback when direct edits are not appropriate
• First-party business-owner provided data only

Not used for OSM edits:

• Google Business Profile as a source for OSM contributions
• Third-party directory data
• Bulk automated write flows
• Blind auto-sync from other platforms into OSM

Participants

At present, this activity is coordinated by Nätvaro AB.

The OSM account(s) used for this organised editing activity will be listed here as they are used on an ongoing basis. Reviewing operators may be added here if and when applicable.

Traceability

Every edit passes through human operator review before submission.

Edits are traceable through:

• the internal review/approval step in Nätvaro
• the recorded changeset ID
• the recorded OSM object identifier where applicable
• the linked OSM account used for the submission
• internal audit logs containing before/after tag snapshots where applicable
• note identifiers for note-based fallback submissions

Community consultation

A public community notice will be posted in the Sweden category of the OpenStreetMap Community Forum before production start.

That post will describe:

• who we are
• what data we edit
• which data we do not use
• how review works
• that the initial scope is node-only
• that OSM Notes may be used as fallback
• how to contact us

Production edits will begin no earlier than two weeks after that public notice.

This section will be updated with a date and link to the public discussion thread once posted.

Training/instructions

Reviewing operators follow internal written instructions covering:

• source policy and first-party data rules
• prohibited use of Google Business Profile or third-party data for OSM edits
• field eligibility rules
• matching and confidence thresholds
• when to use Notes instead of direct edits
• note content restrictions
• traceability and audit requirements
• how to respond to community feedback

Key policy constraints are summarised on this wiki page.

Notes policy

OSM Notes are used only as a fallback when direct editing is not appropriate, for example because matching confidence is too low or manual community review is preferable.

Notes do not contain personal contact details. They may include limited public business correction information relevant for community review.

Measuring our success

Success is measured primarily by edit quality, traceability, and low community friction, not by edit volume.

Internal review includes:

• match confidence
• whether the edited fields are eligible for OSM contribution
• whether fallback to Notes is more appropriate than direct editing
• follow-up on community feedback and changeset comments

Post-event clean-up

If any edit is found to be problematic, Nätvaro will review the corresponding internal audit record and the public OSM history.

Follow-up actions may include:

• manual review of the affected object
• direct correction
• note follow-up
• revert of the relevant changeset where appropriate
• response to changeset comments or forum feedback

Results

No production results are reported yet because the activity is still in pre-launch / internal testing.

After production start, this section will be updated with a summary of results such as:

• number of reviewed edits
• number of notes used as fallback
• any corrections or reverts
• any policy/process adjustments made based on community feedback

Compliance

This activity follows the Organised Editing/Guidelines and the associated OpenStreetMap Foundation organised editing expectations.

Questions or concerns can be directed to info@natvaro.se.