{"id":11670,"date":"2026-07-26T16:06:15","date_gmt":"2026-07-26T08:06:15","guid":{"rendered":"https:\/\/aeosub.com\/axismundi-geodata\/"},"modified":"2026-07-26T16:06:15","modified_gmt":"2026-07-26T08:06:15","slug":"axismundi-geodata","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/axismundi-geodata\/","title":{"rendered":"Axismundi Geodata"},"content":{"rendered":"
\n
LethaldiranMX Insight<\/div>\n
\n
\n

Axismundi Geodata establishes a highly structured, privacy-first spatial data layer for WordPress, effectively decoupling geographic metadata from frontend presentation. By registering dedicated hierarchical and flat taxonomies alongside standardized coordinate meta, it solves the common fragmentation issue where multiple plugins write conflicting location schemas. The inclusion of a robust privacy model\u2014where raw coordinates are decoupled from public REST exposure by default\u2014makes it an exceptionally secure foundation for directory sites, travel blogs, and federated content networks. Its developer-friendly architecture, featuring filter-driven post-type registration and clean API endpoints, positions it as a reliable infrastructure choice for complex geospatial implementations.<\/p>\n

Best Fit & Operational Role:<\/strong> This plugin is an ideal fit for enterprise publishers, travel platforms, and multisite networks that require a centralized, standardized geo-spatial registry without being locked into a monolithic mapping suite. It functions as the foundational data engine in a decoupled WordPress stack, allowing developers to safely store location data (including EXIF-imported GPS coordinates) and expose it via REST to headless frontends or companion plugins like Axismundi Map. By enforcing strict separation between administrative containment (hierarchical) and topical place tagging (flat), it solves the operational headache of managing complex location hierarchies while maintaining clean, queryable database structures.<\/p>\n

Potential Limitations & Pitfalls:<\/strong> While the architecture is highly optimized, operations teams should note that rendering Leaflet mini-maps in the admin panel and processing EXIF metadata on media uploads can introduce minor client-side and server-side overhead during bulk media ingestion. Additionally, because the plugin acts strictly as a data store and relies on external tile providers (configured via Settings) and companion plugins for frontend map rendering, teams must budget for additional configuration and potential third-party API costs. No security vulnerabilities or critical performance bottlenecks were identified based on available information.<\/p>\n<\/div>\n<\/div><\/div>\n

\n
\n \"Axismundi <\/p>\n
\n
Plugin Specification<\/div>\n

WordPress.org Official Data<\/small>\n <\/div>\n<\/p><\/div>\n\n\n\n\n\n\n\n
Developer<\/th>\nJiwoon Kim<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv0.2.3<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n6.7 \/ 7.0.2<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-07-26 8:04am GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details -><\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Canonical geo store for Axismundi: place taxonomies and privacy-aware coordinate metadata, exposed over REST.<\/div>\n

Axismundi Geodata is the data layer that lets posts and attachments carry a
\nlocation, and lets the editor, map blocks, and federation serializers read it
\nback through one shared model. It registers:<\/p>\n

    \n
  • axismundi_geo_area<\/code><\/strong> \u2014 a hierarchical taxonomy for address \/ administrative
    \ncontainment (\ub300\ud55c\ubbfc\uad6d > \ubd80\uc0b0\uad11\uc5ed\uc2dc > \uc218\uc601\uad6c > \uad11\uc548\ub3d9). Answers “where is it?”.<\/li>\n
  • axismundi_geotag<\/code><\/strong> \u2014 a flat taxonomy for place \/ content geo tags (\uad11\uc548\ub9ac\ud574\uc218\uc695\uc7a5,
    \n\uad11\uc548\ub300\uad50). Answers “what place is it about?”.<\/li>\n
  • Coordinate meta<\/strong> on posts, pages, and attachments \u2014 the observation \/
    \ncapture point, using the WordPress-convention geo_latitude<\/code>, geo_longitude<\/code>,
    \n geo_public keys plus ax_geo_*<\/code> extensions.<\/li>\n
  • Place-fact term meta<\/strong> \u2014 centroid, display bounds \/ zoom, and external place id on
    \neach geo taxonomy term.<\/li>\n<\/ul>\n

    The taxonomy identifiers are plugin-prefixed to avoid conflicts with other
    \nplugins. Their public permalink bases remain \/geo-area\/<\/code> and \/geotag\/<\/code>.<\/p>\n

    Privacy is built into the model. The raw exact coordinate is stored, while
    \n geo_public decides whether an attachment coordinate may leave the site.
    \nCallers ask the plugin for the public coordinate rather than reading raw meta.<\/p>\n

    Attachments get a Location (GPS)<\/strong> editor on the Edit Media screen: latitude,
    \nlongitude, altitude, and a public toggle, plus an on-demand Import from EXIF<\/strong>
    \nbutton that reads the original file’s GPS, and a Leaflet mini map with a draggable
    \nmarker (configure a tile provider under Settings \u2192<\/span> Geodata). Nothing is
    \nauto-imported or auto-published \u2014 the public toggle defaults off.<\/p>\n

    Posts and pages express location through the Geo Area \/ Geotag taxonomies. The
    \nseparate Axismundi Map plugin consumes this data for front-end place, media,
    \ntrack, and geo-archive maps. Attachments carry coordinate meta only \u2014 they are
    \nnever auto-tagged with place terms. A future ax_note post type can opt into the
    \ngeo taxonomies through the axismundi_geodata_object_types<\/code> filter.<\/p>\n

    Both public taxonomies include plugin-owned block templates for their archive
    \npages. They retain the tonal archive header, current-term map, inherited card
    \nfeed, and geo navigation sidebar previously supplied by the Axismundi theme.
    \nThemes and site owners can still override them through the normal template
    \nhierarchy. The map remains optional; without Axismundi Map the archive feed and
    \nnavigation continue to render.<\/p>\n

    The theme does not hard-code Geo taxonomy blocks. Insert the plugin-provided
    \nPost geo terms<\/strong> pattern where a post template should expose its areas and
    \nplaces.<\/p>\n

    A demo place hierarchy (\ub300\ud55c\ubbfc\uad6d > \ubd80\uc0b0\uad11\uc5ed\uc2dc > \uc218\uc601\uad6c > \uad11\uc548\ub3d9, with the
    \n\uad11\uc548\ub9ac\ud574\uc218\uc695\uc7a5 geotag) ships with the plugin but is created only on request \u2014 it
    \nis never seeded automatically. Run wp axismundi-geodata seed-demo<\/code> to add it and
    \n wp axismundi-geodata seed-demo –remove to drop it.<\/p>\n

    Term editors can optionally look up a place from an external provider and bind it.
    \nProviders are configured under Settings \u2192<\/span> Geodata and are off by default: Google
    \nPlaces needs a server-side API key, and OpenStreetMap (Nominatim) is enabled by
    \nchoosing the public service (low-volume admin lookup only) or a custom endpoint.
    \nKeys and endpoints are used only from admin AJAX and are never sent to the
    \nbrowser. Selecting a candidate binds the term to a namespaced id \u2014
    \n google: or osm:node\/<id><\/code> \/ osm:way\/<id><\/code> \u2014 and stores the returned
    \ncoordinates, address, and place type.<\/p>\n

    For self-hosted maps, upload a .pmtiles<\/code> map pack under Media. The plugin reads
    \nits tile format, schema, bounds, zoom, and attribution into editable attachment
    \nfields, and a Protomaps map pack can be chosen as the admin preview basemap under
    \nSettings \u2192<\/span> Geodata. Front-end provider settings are enabled when Axismundi Map is
    \nactive. The plugin never bundles or generates tile data.<\/p>\n

    GPX and KML uploads are recognised as GPS tracks and exposed as GeoJSON through
    \nthe REST API. Geotags and public GPS media are also available as GeoJSON for map
    \nclients. The controlled geotag place-type vocabulary uses Google Places tokens as
    \nits baseline plus reviewed local extensions with explicit Google fallbacks.<\/p>\n

    WordPress RSS 2.0 and Atom feeds are extended with GeoRSS Simple when location
    \ndata is available. A post with one coordinate-bearing geotag emits a point;
    \nmultiple geotags emit their bounding box; posts without geotags remain ordinary
    \nfeed items. Geo taxonomy feeds also describe the current term at feed level. The
    \nserializer uses public geotag facts only and never exposes post or attachment GPS
    \nmeta. A server-side adapter uses WordPress fetch_feed()<\/code> \/ SimplePie to convert
    \nexternal GeoRSS and W3C Geo feeds into GeoJSON for map clients.<\/p>\n

    External services<\/h3>\n

    All external services are optional. Choosing None<\/strong> for preview maps and not
    \nconfiguring a lookup provider makes no external request.<\/p>\n

      \n
    • Google Maps Platform<\/strong> is used only when an administrator configures a Google
      \nAPI key and explicitly searches for or reverse-geocodes a place in the term
      \neditor. The server sends the search text or clicked latitude\/longitude, selected
      \nlanguage\/region, and the configured API key to Google. Google Maps Platform
      \nTerms: https:\/\/cloud.google.com\/maps-platform\/terms\/ Privacy Policy:
      \nhttps:\/\/policies.google.com\/privacy<\/li>\n
    • OpenStreetMap Nominatim<\/strong> is used only when an administrator selects the
      \npublic Nominatim provider or configures a custom Nominatim-compatible endpoint,
      \nthen performs a place lookup. The server sends the search text or clicked
      \nlatitude\/longitude to that endpoint. Public Nominatim usage policy:
      \nhttps:\/\/operations.osmfoundation.org\/policies\/nominatim\/ OpenStreetMap privacy
      \npolicy: https:\/\/wiki.osmfoundation.org\/wiki\/Privacy_Policy<\/li>\n
    • Protomaps assets<\/strong> supply glyph and sprite files only when an administrator
      \nselects a Protomaps PMTiles preview style. The administrator’s browser requests
      \nthe selected glyph\/sprite URLs, which disclose the browser IP address and the
      \nrequested map assets to Protomaps’ GitHub Pages host. Protomaps legal terms:
      \nhttps:\/\/protomaps.com\/legal GitHub privacy statement:
      \nhttps:\/\/docs.github.com\/site-policy\/privacy-policies\/github-privacy-statement<\/li>\n
    • MapTiler<\/strong> and Thunderforest<\/strong> are optional raster-tile providers selected
      \nby the site administrator. When selected, the viewer’s browser requests map
      \ntile coordinates and sends its IP address, referrer, and the provider key in
      \nthe configured tile URL. MapTiler Terms: https:\/\/www.maptiler.com\/terms\/
      \nPrivacy Policy: https:\/\/www.maptiler.com\/privacy-policy\/ Thunderforest Terms:
      \nhttps:\/\/www.thunderforest.com\/terms\/ Privacy Policy:
      \nhttps:\/\/www.thunderforest.com\/privacy\/<\/li>\n
    • External GeoRSS\/W3C Geo feeds<\/strong> are fetched only when a site administrator
      \nsupplies a feed URL to the server-side GeoRSS importer. The server sends the
      \nconfigured feed URL request to that feed’s host. Its terms and privacy policy
      \nare determined by the feed provider selected by the site administrator.<\/li>\n<\/ul>\n

      Third-party libraries<\/h3>\n

      Bundled under assets\/vendor\/, each loaded only when the matching admin preview
      \nprovider is active:<\/p>\n

        \n
      • Leaflet 1.9.4 (https:\/\/leafletjs.com\/, BSD-2-Clause) \u2014 raster tile previews.<\/li>\n
      • MapLibre GL JS 5.24.0 (https:\/\/maplibre.org\/, BSD-3-Clause), PMTiles 4.4.1
        \n(https:\/\/github.com\/protomaps\/PMTiles, BSD-3-Clause), and @protomaps\/basemaps
        \n5.7.2 (https:\/\/github.com\/protomaps\/basemaps, BSD-3-Clause) \u2014 PMTiles map-pack
        \npreviews. Label fonts load from the public Protomaps assets host.<\/li>\n<\/ul>\n

        Map strategy<\/h3>\n

        Uploaded PMTiles map packs self-host the tile data, but the Protomaps renderer may
        \nload small glyph\/sprite assets from Protomaps’ public host. Axismundi Map is a
        \nseparate dependent plugin: Geo Data owns the facts, REST exports, providers, and
        \nshared renderer assets; Map owns the public block and Query Map View. See
        \ndocs\/map-strategy.md for the boundary.<\/p>\n

        Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.<\/div>","protected":false},"excerpt":{"rendered":"

        Canonical geo store for Axismundi: place taxonomies and privacy-aware coordinate metadata, exposed over REST.<\/p>","protected":false},"author":1,"featured_media":9317,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[544,2912,2913,1085,2914,555],"class_list":["post-11670","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-geo","tag-geotag","tag-location","tag-rest-api","tag-taxonomy","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11670","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11670"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11670\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/9317"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11670"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11670"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11670"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}