|
I'm looking for advice and recommendations. We want to create a web map that has client pan/zoom capabilities for around 10,000 clients. We want to use custom rendered OSM tiles served from our own server. On top of the OSM tiles we need to map point and line features that change color(state) every two minutes. How would you recommend we do this? Would Leaflet work? How should we store/serve the point/line features. Should we store them in a shapefile, csv file, sql server database, etc? We can't store them in the OSM tiles because they need to change colors. Also, we don't want to buy anything if possible. Any help, insights you can offer would be most appreciated. |
|
Generally, you have the option of transferring your overlay to the client either as raster data (ie an image) or as vector data (ie structured information that contains the coordinates and status of every feature and the client then draws them). If you can construct a mechanism whereby the client is only informed of changes of object state, so that initially you transmit youe 5000 objects but then regularly you only transmit a (supposedly much smaller) state change information, that could work well with vectors. Vectors will also have the advantage that the client knows about them, so you can do something like hovering over an object changes its colour or so. If you have to basically refresh all objects all the time, vector might be too resource intensive, and transmitting just a PNG with all the overlay stuff is preferable. Typically you could use simple WMS server in the backend for that, translating the data from a database into a PNG image for display by OpenLayers or Leaflet. Check out the OSM Inspector (tools.geofabrik.de/osmi) or an example of a web page that uses a tiled OSM base map and displays database-controlled WMS layers on top. Frederik Ramm, do you have any suggestions/guidance as to how to create database-controlled WMS layers? Free software that we can use to do this? Thanks so much for your help so far. :)
(30 Oct '19, 17:55)
SeattleHeather
1
MapServer (see mapserver.org) or GeoServer (see geoserver.org) are the obvious Open Source choices.
(30 Oct '19, 19:52)
Frederik Ramm ♦
|
