If you use this service in your applications, make sure to include the copyright as stated here. The import of the planetfile of OpenStreetMap, which currently is about 43GB, is done through Imposm3 and takes about 30 hours to complete.Īs this service is based on the data of the OpenStreetMap-Project, you have to respect the corresponding copyright. Every day we deliver more than 22GB of map tiles. EPSG 3857 / EPSG 900913 (Google Mercator Projection)Įvery week we produce and recalculate approx.EPSG 31468 (DHDN / Gauss-Krüger Zone 4).EPSG 31467 (DHDN / Gauss-Krüger Zone 3).EPSG 31466 (DHDN / Gauss-Krüger Zone 2).The following coordinate system are available for the service: These additional scales deliver good and readable results for maps that use these typical scales. Even without understanding the format of a WMS request, you can look at that URL and get some information. We use the same mapscales like OpenStreetMap does, but we also added some useful cartographic scales to the range of cached zoomlevels: This looks a lot like a Google Maps tile. Our service is available in color and grayscale. Simply copy and paste the content of an custom map source. Note: For simple testing a custom XML map source you can also use MapEvaluator. Most of them are defined in an xml file in the mapsources directory. These on-the-fly served tiles will still be saved in the cache, so that reoccuring request to the same area will have quick response times. Custom map sources which uses a similar URL scheme as Google/OpenStreetMap can be added to MOBAC. All request which go lower this scale will be served on demand. Central europe gets cached up to zoomlevel 20, which corresponds to a scale of 1:25.000. The WMS is rendered with the help of GeoServer and is cached and accelerated with the help of MapProxy. The service is updated weekly and covers the whole world. This is the code I use for creating the layer layer = new service presents the data of the OpenStreetMap-Project in a clear and simple way. My question is: I am right to think that I should be querying for a 3857 projected wms layer or should I stick to 4326? and is it normal that I have a big shift in my 3857 tiles? 3857 the wms tiles are completely off, huge lat shift 4326, the tiles look OK acvtually, I can't notice much of a shift. I have the two running so I can compare them. I think the problem is with Google Maps Projection. When I open Geoserver and try to click on WMS featues I can get the feature info. I wanted to experiment by myself, I request the 3857 to the map server and do some reprojections for the BBOX coordinates. I am trying to render WMS layer on Google Maps and its working fine except getfeatureinfo event. I searched a bit for fellow implementation and I saw that most (if not all) use 4326 instead. ESRI RESTful/Google Maps Tiles, OSM (Open Street Map Tiles), TMS (Tile Map Service Tiles) WMS/ WCS / WFS / WMTS. As Google Maps projection is a web mercator, I thought it would be better to request wms layers with srs=3857 (or equivalent) instead of the 4326. I am adding wms layers to my google maps application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |