Skip to content

History / Spatial joins and allocation

Revisions

  • Spatial joins and allocation: escape two more table-cell pipes The "left joins, already aggregated" table had the same unescaped-`|` problem as the previous fix: [[impedance_table|impedance_table(...)]] and [[discrete_alloc|Function-discrete-alloc]] each broke their row. Escaped both as `\|`. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

    @MaartenHilferink MaartenHilferink committed Sep 3, 2026
  • Spatial joins and allocation: escape the pipe in a table-cell wiki-link The unescaped `|` inside [[selection|Selection functions]] in the CROSS JOIN row of the "joins on a given key" table was read as a table column separator, breaking that row. Escaped as `\|`, matching how Command-line-options.md and Configuration-examples.md already do this inside a table cell. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

    @MaartenHilferink MaartenHilferink committed Sep 3, 2026
  • Add Spatial joins and allocation: the matching functions as joins, and the road from a database to an allocation model A new page that connects the functions which match two domain units the way a JOIN does in SQL: join_equal_values and rlookup on a given key; the pair-producing spatial pre-selections (join_near_values, connect_matrix / dist_matrix, point_in_all_polygons, geos_overlay_polygon, impedance_matrix) as inner joins; connect, connect_info, point_in_polygon, impedance_table, capacitated_connect and discrete_alloc as left joins that already chose one match per row; and how a pair domain aggregates into a relation but not back. The last section traces, in five steps, how a customer-order-product database differs from a spatial interaction or allocation model: the join table is recorded there, and derived, chosen, distributed and finally optimised under competing claims here. Spatial-join now opens with a sentence (it opened with a code block, which loses the search snippet) and names itself as the Cartesian-product form. Reverse links on How-To-Model, Relational-model-versus-Semantic-arrays, the Relational, Network, Allocation and point-polygon hubs, and the see-also of join_equal_values, join_near_values, connect_matrix, geos_overlay_polygon and impedance_matrix. The page is not in the geodms.nl menu until nav/geodms.md in GeoDmsWikiToStaticHtml lists it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    @MaartenHilferink MaartenHilferink committed Sep 3, 2026