Wikidata:Property proposal/georeferencing data
georeferencing control point data
georeferencing pixel mask data
georeferencing mask geoshape
Moving Georeferencing data from its present silo in the MapWarper application into the Commons Data: namespace brings it much more naturally into the domain of the Commons community, and will make it much more accessible for use in gadgets or other reuse.
These SDC properties will enable apps to find what has been put where, for the two main types of information used as input for the process; and for queries and apps to access a geoshape showing the real-world position and characteristic boundary of the georectified map.
Note that multiple sets of control-point (gcps) data may exist concurrently for the same image. Different sets of control points may relate to different maps contained in the image (eg multiple sub-maps; or main map/inset map(s) combinations); to sets of control point data obtained independently from different sources (eg Commons MapWarper / external source); or to control point data obtained from different features for different purposes (eg projection estimation  is often most effectively achieved based on control points representing a graticule of intersections of lines of latitude and longitude, whereas final map-warping often aims to distort the map to most accurately place depicted land-features and population centres).
Different sets of control points may be associated with the same or with different pixel masks.
The output mask geoshape will in turn relate to a particular pair of control-point and pixel-mask datafiles.
These potentially complicated relationships can be captured by qualifiers on the statements, in particular parallel applies to part (P518) qualifiers on each of the statements to indicate a particular part of the image (eg main map / top-left map / inset map / second inset map etc), object has role (P3831) to distinguish sets of control points relating to different features; and referencing to distinguish sets of control points with different provenances.
The control-point and pixel-mask statements should also be qualified to associate them with a particular revision-id of the file (Wikidata:Property proposal/image revision-id), in case it may subsequently have been cropped/modified.
The georectified mask should be linked to the inputs it is derived from (Wikidata:Property proposal/based on tabular data). It should also have, for convenience, a P518 to indicate the particular map it relates to, where the image contains multiple maps. Jheald (talk) 06:01, 17 August 2019 (UTC) (revised proposal)
- Support I've just watched the summary of what is possible at min 22.30 of this presentation at Wikimania. The potential for this looks amazing. - Ambrosia10 (talk) 20:58, 18 August 2019 (UTC)
- Support I also saw this demoed at the Wikimania hackathon showcase and think it makes a lot of sense. --Daniel Mietchen (talk) 00:31, 19 August 2019 (UTC)
- Support Thisismattmiller (talk) 13:20, 19 August 2019 (UTC)
- Support --Sabas88 (talk) 16:12, 19 August 2019 (UTC)
- Support Buccalon (talk) 17:54, 19 August 2019 (UTC)
- Support link Wikimania 2019: Hackathon Showcase 22:05 --Salgo60 (talk) 06:33, 22 August 2019 (UTC)