This is how QGIS writes the proj-string and WKT with +towgs84-parameter:
+proj=longlat +ellps=bessel +towgs84=598.1,73.7,418.2,0.202,0.045,-2.455,6.7 +no_defs
GEOGCS["DHDN",DATUM["Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel 1841",6377397.155,299.1528128,AUTHORITY["EPSG","7004"]],TOWGS84[598.1,73.7,418.2,0.202,0.045,-2.455,6.7],AUTHORITY["EPSG","6314"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4314"]]
But keep in mind that there is no overall value for converting any Bessel-1841-Data to WGS84.
For Germany, there were a lot of parametres published, until a NADgrid for the whole country was created. This applies the correct shift for every point inside Germany.
Other surveying authorities have done similar conversions, but with other values.
EDIT
There is a forum entry in Russian http://gis-lab.info/forum/viewtopic.php?t=9386
giving the following proj parameters:
+proj=tmerc +lat_0=55.6666666667 +lon_0=37.5 +x_0=0 +y_0=0 +k_0=1. +a=6377397 +rf=299.15 +towgs84=396,165,557.7,-0.05,0.04,0.01,0 +no_defs
Maybe you get lucky with those values.
From your above additional code, it looks like you are loading Leaflet.markercluster script before Leaflet script:
<script src="leaflet.markercluster-src.js">
<script src="http://code.jquery.com/jquery-1.12.0.min.js">
<script src="http://cdn.leafletjs.com/leaflet-0.7.3/leaflet.js">
You should rather load it after:
<script src="http://code.jquery.com/jquery-1.12.0.min.js">
<script src="http://cdn.leafletjs.com/leaflet-0.7.3/leaflet.js">
<script src="leaflet.markercluster-src.js">
You should learn to use your browser console (on Windows / Linux browsers, press F12; on Mac OS browsers, press Command ⌘+Option ⌥+i) to look for potential errors.
In your case, I suspect there should be something like "ReferenceError: L is not defined
" due to Leaflet.markercluster trying to attach some code to Leaflet's L
namespace, but could not find it because it is not loaded yet.
Best Answer
I know this is an old post but here's the solution anyway:
GeoServer's tilematrix has Y-up as per GIS convention. The Mapbox style of tilematrix has Y-down as per computer graphics convention. The basic TMS protocol assumes Y-down, so Leaflet needs to know to reverse the Y coordinates of the tile matrix (remember this is the Y of the tilematrix and not the actual real world coordinates).
There is a way of calculating the reversed y value mathematically but in Leaflet 0.7 there is a
tms: true
option and in v 1.0 you can simply use{-y}
for servers like GeoServer that follow the GIS convention. See here and scroll to the bottom for more detail.