task #5733
Updated by Andreas Kohlbecker about 6 years ago
Es scheint vorteilhaft in Zukunft den Geoserver (oder eine alternative, CartoDB?) direkt zu nutzen. Die Pflege und Weiterentwicklung der REST-artigen API der EDIT Mapservices erzeugt regelmäßig einen Overhead der durch Umgehung der Map Services oder einen Technologiewechsel wegfallen würde. Allerdings sollte vorher geklärt werden ob und wie alle Funktionalitäten des EDIT map service ersetzt werden können. Special Features: * Map Service calculates the bounds of the reactangle enclosing the supplied data (areas, point locations) * Provides a legend image for the distribution states Futher requirements: * All labels must me visible and duplicate labels must be avoided. Geoserver is having problems here: A label may be shown two times in adjacent tiles. * Users should be enabled to modify the appearance of base layers. E.g.: Change labels, or other details Related email conversations: ~~~ From: Andreas Kohlbecker <a.kohlbecker@bgbm.org> (BGBM) To: THEETEN Franck <franck.theeten@africamuseum.be> CC: "a.mueller@bgbm.org" <a.mueller@bgbm.org> Date: 24.05.17 09:08 Hi Franck, > Another solution (but at server-side) would maybe be to enable the Tile caching of GeoServer? I guess that this would not help. As far as my knowledge on this problem goes, the reason for the erratic display of labels is the Geoserver trying to be smart. It calculates the appearance of label per tile. If a label overlaps the tile bounds too much it will be hidden. From the posts that I found in stackoverflow I got the impression that the label visibility strategy of geoserver has changed over time. In older version a common problem was that labels where duplicated. The same label were placed on each of two neighbouring labels, because it overlapped the bounds of both. Best wishes Andreas ~~~