# \[SOLVED\] OSM-WMS Compliant Maps & Precision
**URL:** https://discuss.elastic.co/t/solved-osm-wms-compliant-maps-precision/57034
**Category:** Elasticsearch
**Created:** [August 2, 2016, 4:12pm UTC](https://discuss.elastic.co/t/solved-osm-wms-compliant-maps-precision/57034 "2016-08-02T16:12:44Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@seth.yes](https://discuss.elastic.co/u/seth.yes)
#### Post date: [August 2, 2016, 4:12pm UTC](https://discuss.elastic.co/t/solved-osm-wms-compliant-maps-precision/57034/1 "2016-08-02T16:12:44Z")
With the recent decommission of Mapquest functionality with Kibana, I have been researching other WMS compliant maps. Leading me to a few questions;
1. Is there a list of maps that are compliant with Kibana 4.5? I want to try a few and see which best-fits our business needs.
2. If there currently no list of maps, what do I need to verify for a map to be compatible with Kibana?
3. We have our own internal mapping system, that is OMS compliant, are there any good resources for a how-to with regards to making it work with Kibana?
4. The precision appears to be a bit off, is there anything I can do to fine-tune this? In screenshot provided below, the circle should be on an intersection and not off to the side.. it appears as though this map is using a best-fit function to fit the circle to a grid.. is there anything I can do to increase precision?
The current map I'm using is: [http://ows-tile.terrestris.de/osm-basemap/service](http://ows-tile.terrestris.de/osm-basemap/service)?
Thanks for all the community support! ELK is pretty powerful.
---
### Author:  [@seth.yes](https://discuss.elastic.co/u/seth.yes)
#### Post date: [August 3, 2016, 4:02pm UTC](https://discuss.elastic.co/t/solved-osm-wms-compliant-maps-precision/57034/2 "2016-08-03T16:02:56Z")
I found what I believe to be the reasoning for (4.) the precision..
The coordinates are as precise as we need, however a geohash is manifested from this data. The geohash appears to be as precise as what is defined in the map. A comparison from a precise map ([geohash.gofreerange.com](http://geohash.gofreerange.com)) is compared with my current map in Kibana ([http://ows-tile.terrestris.de/osm-basemap/service?)](http://ows-tile.terrestris.de/osm-basemap/service?)) below, showing tiles that exactly match. However the precise map will allow for more characters (and thus more precision, as seen with the nested boxes).
[[http://geohash.gofreerange.com/](http://geohash.gofreerange.com/)]
[[http://ows-tile.terrestris.de/osm-basemap/service?]](http://ows-tile.terrestris.de/osm-basemap/service?%5D)
If I find a more-precise map I can use with Kibana, I'll update this thread.
---
### Author:  [@seth.yes](https://discuss.elastic.co/u/seth.yes)
#### Post date: [August 9, 2016, 3:53pm UTC](https://discuss.elastic.co/t/solved-osm-wms-compliant-maps-precision/57034/3 "2016-08-09T15:53:11Z")
[Solved] -- it turns out the map precision wasn't the issue.. I was able to increase precision by adding to mapping for this object:
`"geohash_precision": 9, "type": "geo_point", "geohash_prefix": true`
That increases precision for Elasticsearch, however Kibana also needs precision updated in the advanced settings. Updating the precision for both of these services has increased precision as expected.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:29pm UTC](https://discuss.elastic.co/t/solved-osm-wms-compliant-maps-precision/57034/4 "2017-07-05T22:29:03Z")