Skip to content

AREA_FUNC.md

Latest commit

 

History

History
91 lines (56 loc) · 2.37 KB

AREA_FUNC.md

File metadata and controls

91 lines (56 loc) · 2.37 KB
Raw

Area

This document provides an overview of SDEP areas.

Status: implemented.

Reference links:

Table of contents

Goal

Competent authorities (CAs) can opt-in for short-term rental regulation by designating one or more regulated areas.

Sequence

sequenceDiagram
    participant CA as CA
    participant SDEP as SDEP

    Note over CA: For each regulated area.

    CA->>SDEP: 1. POST: areas
Loading

Legend:

  • CA - Competent Authority
  • SDEP - Single Digital Entry Point
  • All actions happen periodically/asynchronously

Area management is country-specific (not EU-harmonized).

Data

See:

Process

Regulation

An area carries a regulation attribute, which says what the area is regulated for:

Value The area accepts
listing Listings (random checks) only
activity Rental activities only
all Both (the default when the CA supplies no value)

This is the switch between the two subject areas:

  • A listing for an area that is regulated for activities only is rejected per item, see Listing
  • An activity for an area that is regulated for listings only is rejected per item (STR v2 and up), see Activity

It also lets two competent authorities designate the same geographic area for different purposes: one for listings, the other for activities.

Versioning

Areas contain shapefiles, that represent the geospatial location.

Areas are versioned.

As discussed in the EU technical working group:

  • It is assumed that shapefiles are updated at the beginning of each month.
  • This logic is not handled by the SDEP, but by agreement on a process.

For example, a new Competent Authority wants to regulate their area.

  • The regulation should start at the beginning of a month
  • And the platforms should be informed 'timely' about the new regulation for that area

See also #22.