spatial-data-maching

See https://www.openstreetmap.org/user/fititnt/diary/404303.

TL;DR:

1. Allows visualize datasets, with special focus with spatial reference (e.g. position on earth), and export the results of your filters to other programs
2. Can be used to load data and then as a companion (side by side or alt tabbing) with other editing tools (OpenStreetMap, Wikidata, reviewing data from the government/company you work, etc).
3. The internal data model uses GeoJSON. It also allows importing tabular data, trying to auto detect latitude and longitude
4. There's no "automatic conflation button". You need to explore how datasets are related to each other, such as deciding distance and/or attributes in common, then it can assist you.

Configuration

to be documented

The JSON-Schema for the latest version is available at public/sdm.schema.json. This schema can be used to strictly document and validate configuration files, such as examples on the filter tests/.

Quickstart to internals

After data is imported into memory, it's organized similar to a GeoJSON feature. Two extra references:

• @did: dataset identifier (unique).
  • A sequential number, starting from 1, by default based on the order of import
• @fid: feature identifier (unique).
  • A sequential number, starting from 1, based on order of files and order of items in the files.
• @mgi: pattern matching identifier group.
  • For an given set of maching strategy, calculate for the entire target dataset. All features with same code are considered be the same group.
• @mmi: manual maching identifier.
  • It's similar to @mgi, however with manual explicit matching. May contradict the inference of active strategy maching

For attributes (when a feature have attributes added or changed from the original)

• @msa: metadata of source of an attribute.

each feature is calculated, and the ones with the same group are considered be from the same group

All features with same code are considered to be in the same group ()

Quickstart to debug

1. Using the console of your browser, the variable SDMData will contain most of the underlining data of the memory (the v0.5.0 the close equivalent would be WorkingData). The SDMConf also contains some internal configurations and reference to some options defined by the user.