OpenGeofiction:Carto layer: Difference between revisions

Latest revision as of 08:51, 9 October 2025

The term "carto" (short for cartographic) has become a kind of standard way of referring to the default style of the OpenStreetMap render. The so-called openstreetmap-carto (osm-carto) has its code base hosted on github and is freely downloadable and installable. The particular style of map render has become idiosyncratic to OpenStreetMap, an aspect of its image or "brand" online, but it is also constantly evolving.

OpenGeofiction uses the same osm-carto style for its main (default) map layer.

Is OpenGeofiction's carto layer out of date?

Yes and no... We have two instances of the carto layer available:

OGF-Carto - 5.9.0, and was current as of October 2024
OGF-Carto (old) - 5.3.0, and was current as of August 2021

Updating the render software is not a simple task. Therefore we have opted not to try to "keep up" with the osm-carto code base. We anticipate updating maybe once a year or so.

Can we customize OpenGeofiction's carto layer?

In theory yes. In practice, no. It's hard. Sorry. Eventually we may develop a separate, custom OpenGeofiction render layer, similar to the way the histor layer used to work. This is not currently in development, however.

What are the technical specifications of the OpenGeofiction carto layer?

The OpenGeofiction carto layer is called ogf-carto in the code base.

Caption text
Layer	Version	Server	Location	Code letter	Tiles path (e.g. for adding as a TMS image layer to JOSM or iD)
OGF-Carto	5.9.0	`tiles05.opengeofiction.net`	UK	`5`	https://tiles05.opengeofiction.net/ogf-carto/{zoom}/{x}/{y}.png
OGF-Carto (old)	5.3.0	`tiles04.rent-a-planet.com`, aliased as `tile.opengeofiction.net`	US West Coast	`B`	https://tile.opengeofiction.net/ogf-carto/{zoom}/{x}/{y}.png

Maximum zoom is the same as for OpenStreetMap: zoom=19

@@ Line 1: / Line 1: @@
-=What is a carto layer?=
+The term '''"carto"''' (short for cartographic) has become a kind of standard way of referring to the default style of the OpenStreetMap render. The so-called openstreetmap-carto (osm-carto) has its code base hosted on [https://github.com/gravitystorm/openstreetmap-carto github] and is freely downloadable and installable. The particular style of map render has become idiosyncratic to OpenStreetMap, an aspect of its image or "brand" online, but it is also constantly evolving.
-That's easy! The term "carto" (short for cartographic) has become a kind of standard way of referring to the default style of the OpenStreetMap render. The so-called openstreetmap-carto (osm-carto) has its code base hosted on [https://github.com/gravitystorm/openstreetmap-carto github] and is freely downloadable and installable. The particular style of map render has become idiosyncratic to OpenStreetMap, an aspect of its image or "brand" online, but it is also constantly evolving, with small changes made to the style on an almost weekly basis.
 OpenGeofiction uses the same osm-carto style for its main (default) map layer.
-=Why is OGF's carto layer out of date?=
+==Is OpenGeofiction's carto layer out of date?==
-Updating the render software is not a simple task. Therefore we have opted not to try to "keep up" with the osm-carto code base. We anticipate updating maybe once a year or so. The current version of the OGF Carto layer is 5.3.0, and was current as of August, 2021.
-=Can we customize OGF's carto layer?=
-In theory yes. In practice, no. It's hard. Sorry. Eventually we may develop a ''separate, custom'' OGF render layer, similar to the way the histor layer used to work. This is not currently in development, however.
+Yes and no... We have two instances of the carto layer available:
-=What are the technical specifications of the OGF carto layer?=
+* OGF-Carto - [[Forum:Announcements/Updated map style: Carto v5.9.0|5.9.0, and was current as of October 2024]]
+* OGF-Carto (old) - 5.3.0, and was current as of August 2021
-The OGF carto layer is called ogf-carto in the code base. It is rendered on the current main render server, tiles04.rent-a-planet.com. This server is also aliased as tile.opengeofiction.net.
+Updating the render software is not a simple task. Therefore we have opted not to try to "keep up" with the osm-carto code base. We anticipate updating maybe once a year or so.
-You can find the tiles at this path (e.g. for adding as a TMS image layer to JOSM or iD):
+==Can we customize OpenGeofiction's carto layer?==
-<pre>
+In theory yes. In practice, no. It's hard. Sorry. Eventually we may develop a ''separate, custom'' OpenGeofiction render layer, similar to the way the histor layer used to work. This is not currently in development, however.
- https://tile.opengeofiction.net/ogf-carto/{zoom}/{x}/{y}.png
-</pre>
-Maximum zoom is the same as for OpenStreetMap: zoom=19
+==What are the technical specifications of the OpenGeofiction carto layer?==
-It's "layer code letter" is "B" (this is a suffix to the URL, e.g. ''"...&layers=B"'') but because it's the default layer, this URL suffix is often "eaten" by the browser.
+The OpenGeofiction carto layer is called ogf-carto in the code base.
-The topo render database receives incoming replication from the main apidb (opengeofiction.net) which currently "ticks" about every 10 minutes (not minutely, as in OSM).
+{| class="wikitable"
+|+ Caption text
+|-
+! Layer !! Version || Server !! Location !! Code letter || Tiles path<br /><small>(e.g. for adding as a TMS image layer to JOSM or iD)</small>
+|-
+| OGF-Carto || 5.9.0 || <code>tiles05.opengeofiction.net</code> || UK || <code>5</code> || <pre>https://tiles05.opengeofiction.net/ogf-carto/{zoom}/{x}/{y}.png</pre>
+|-
+| OGF-Carto (old) || 5.3.0 || <code>tiles04.rent-a-planet.com</code>, aliased as <code>tile.opengeofiction.net</code> || US West Coast || <code>B</code> || <pre>https://tile.opengeofiction.net/ogf-carto/{zoom}/{x}/{y}.png</pre>
+|}
-=The OGF carto layer isn't showing something I added/deleted correctly. Why?=
+Maximum zoom is the same as for OpenStreetMap: <code>zoom=19</code>
-We have had problems since the migration to the new platform with occasions where the render data seems to get "out of sync" with the apidb (the map database, AKA rails port). This can result in the persistence of deleted objects in the render, or the failure of newly added object to appear in a timely fashion. We are aware of this problem, and even working to solve it, but currently it is an open, unsolved problem.
+[[Category:Community information hubs]]