home.social

#mapcache — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mapcache, aggregated by home.social.

  1. Howard Chu @ Symas @[email protected] ·

    MapCache 1.14 adds #LMDB support mapserver.org/development/chan

    "MapServer is an Open Source geographic data rendering engine written in C. Beyond browsing GIS data, MapServer allows you create “geographic image maps”, that is, maps that can direct users to content."

    #MapCache #MapServer

    #lmdb #mapcache #mapserver
  2. Niklas Alt @[email protected] ·

    So today i had a strange revelation which has the potential for a PSA in #gischat : while our #mapcache powered #wmts for #historicalmap in Hessen has worked from the start in #qgis i have received reports from #arcmap users (v10) that they could not use the service. It was showing the notorious red exclamation mark. Not being #opensource there was no way to determine the reason it failed. Turns out it was a colon in the scale (1:25.000) in the metadata title Tag. IMHO a tale to #switch2qgis

    #gischat #mapcache #wmts #historicalmap #qgis #arcmap
  3. Niklas Alt @[email protected] ·

    So today i had a strange revelation which has the potential for a PSA in #gischat : while our #mapcache powered #wmts for #historicalmap in Hessen has worked from the start in #qgis i have received reports from #arcmap users (v10) that they could not use the service. It was showing the notorious red exclamation mark. Not being #opensource there was no way to determine the reason it failed. Turns out it was a colon in the scale (1:25.000) in the metadata title Tag. IMHO a tale to #switch2qgis

    #gischat #mapcache #wmts #historicalmap #qgis #arcmap
  4. Niklas Alt @[email protected] ·

    So today i had a strange revelation which has the potential for a PSA in #gischat : while our #mapcache powered #wmts for #historicalmap in Hessen has worked from the start in #qgis i have received reports from #arcmap users (v10) that they could not use the service. It was showing the notorious red exclamation mark. Not being #opensource there was no way to determine the reason it failed. Turns out it was a colon in the scale (1:25.000) in the metadata title Tag. IMHO a tale to #switch2qgis

    #gischat #mapcache #wmts #historicalmap #qgis #arcmap
  5. Niklas Alt @[email protected] ·

    So today i had a strange revelation which has the potential for a PSA in #gischat : while our #mapcache powered #wmts for #historicalmap in Hessen has worked from the start in #qgis i have received reports from #arcmap users (v10) that they could not use the service. It was showing the notorious red exclamation mark. Not being #opensource there was no way to determine the reason it failed. Turns out it was a colon in the scale (1:25.000) in the metadata title Tag. IMHO a tale to #switch2qgis

    #switch2qgis #opensource #arcmap #qgis #historicalmap #wmts
  6. Niklas Alt @[email protected] ·

    So today i had a strange revelation which has the potential for a PSA in #gischat : while our #mapcache powered #wmts for #historicalmap in Hessen has worked from the start in #qgis i have received reports from #arcmap users (v10) that they could not use the service. It was showing the notorious red exclamation mark. Not being #opensource there was no way to determine the reason it failed. Turns out it was a colon in the scale (1:25.000) in the metadata title Tag. IMHO a tale to #switch2qgis

    #gischat #mapcache #wmts #historicalmap #qgis #arcmap