1.14.0

Added

• A note you already wrote can be placed from the map. The right-click menu
  could create a note at the spot you clicked, but not put that spot into a note
  that already existed — which meant copying the coordinate, finding the note,
  and pasting it into the properties by hand. Set a note's coordinates here
  now opens a fuzzy note picker and writes the clicked coordinate into whichever
  note you choose.

  Each row in the picker shows the note's folder and, when it already has a
  coordinate, the value it holds, so a near-miss on a name is visible before it
  is chosen rather than after. Templates are left out of the list — read from the
  folder the core Templates plugin names, since a coordinate written into a
  template would go into every note stamped from it afterwards. Picking a note
  with no coordinate writes straight away; picking one that already has a
  coordinate shows the old value and the new one and asks, because a property has
  no undo. Only the coordinate property is written, and the coordinate is the
  same one the menu's other entries use — converted out of the basemap's datum
  and back into longitude range exactly once.

• Track statistics can be written into a note's properties. The numbers under
  an inline map existed only in that embed, where no Base could sort, filter or
  total them. Write track statistics to properties measures the track files
  the current note links and writes distance, ascent, descent, elevation range,
  elapsed and moving time, pace and start time into that note's frontmatter as
  numbers — track-distance-km: 13.62, not "13.6 km", because a formatted
  string sorts 10 km before 9 km. The unit is stated in each property name, since
  a bare number in frontmatter is otherwise unlabelled forever.

  Only what a file recorded is written: a GeoJSON route with no elevation and no
  timestamps leaves one property, a GPX from a watch leaves nine, and a figure
  with nothing behind it is removed rather than left stale. Property names come
  from the new Track property prefix setting, track by default, and the
  command reads, writes and removes nothing outside that prefix — if the prefix
  would collide with the coordinate or place property it refuses rather than
  overwrite. It runs when invoked and at no other time; a track file edited
  afterwards does not rewrite the notes that link it.

• Areas are drawn. A GeoJSON or KML file can hold a region rather than a
  route, and one used to reach the map already transformed, already counted for
  framing, and then drawn by nothing at all — the camera flew to the area and
  showed empty map, with no way to tell an unsupported shape from an empty file.
  An area is now filled in its note's colour beneath everything else, its
  boundary stroked at the track's own width and opacity, and its holes left
  unfilled. It gets no direction arrows and no start or end markers, since a
  region has no travel direction, and it adds nothing to distance, ascent or the
  elevation profile.

  Fill opacity follows the existing Track opacity setting at a fraction of
  it, so a large area never hides the roads and labels underneath. There is no
  new setting to find.

  An area is the last thing a click or hover reaches. A marker, waypoint or
  photo standing inside one keeps its own click, and the map's context menu opens
  over an area exactly as it does anywhere else.

Fixed

• A route that crosses the 180th meridian is drawn where it is. A file whose
  positions run east past 180° and continue as negative longitudes was drawn as
  a line straight back across every other continent, with its arrows pointing
  the wrong way and its start and end markers pushed to opposite screen edges —
  and the camera fitted the whole globe, because a 166 km track off Fiji was
  measured as 359° wide. Such a route now draws as the one short path it is, and
  automatic framing covers the route rather than the planet. The figures under an
  inline map never had this problem and are unchanged.

• A coordinate read from a map panned across that meridian is in range.
  Copy coordinates, New note here, and the external-map links took the
  longitude the camera had counted past 180°, so a place a note should record as
  -179.5 was handed over as 180.5. All three now give the ordinary value.
  This was reachable before by panning; the framing fix above makes the camera go
  there on its own, so it is fixed alongside.

Changed

• A KML polygon now draws as an area rather than an outline. Its
  <outerBoundaryIs> becomes the region and each <innerBoundaryIs> becomes a
  hole, where before every ring was read as a separate line and a hole was
  indistinguishable from a boundary. A ring left open by its writer is closed; a
  <LinearRing> that no polygon declares as a boundary keeps being read as a
  line.