This solution works also for Bing Maps, Google Maps, OSM Cycle e
Transportation...
I think it could work with other map types with a correct ol syntax
--
View this message in context:
Example for OSM Transportation:
$.extend(PM.OL.Theme.olNativeThemes,
{
create: function() {
this.themeList['vmapLayerWms2'] = this.createVmapWmsLayer2();
},
createVmapWmsLayer2: function() {
var vmapLayerWms2 = new
sorry, above I posted the wrong solution (I do a lot of tests...), this is
the right one:
$.extend(PM.OL.Theme.olNativeThemes,
{
create: function() {
this.themeList['vmapLayerWms2'] = this.createVmapWmsLayer2();
this.themeList['vmapLayerWms'] =
Hi Raffaele,
ok! I start writing my solutions or tips with pmapper5, I will let you
khow.
Giovanni
--
View this message in context:
http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Tilcache-in-pmapper5-tp4025488p4025679.html
Sent from the pmapper-users -- p.mapper users
On 12/11/14 at 11:32pm, Armin Burger wrote:
I added a basic support for native OL layer types. See changeset
http://svn.pmapper.net/trac/changeset/1359
should work when called the application with ?config=dev since all of
that new type is defined in the dev configuration.
The
According to Armin indications I tested the custom.js for multiple OL WMS
in this way and it works:
$.extend(PM.OL.Theme.olNativeThemes,
{
create: function() {
this.themeList['vmapLayerWms2'] = this.createVmapWmsLayer();
this.themeList['vmapLayerWms'] =
On 18/11/14 at 12:08am, gioza wrote:
According to Armin indications I tested the custom.js for multiple OL WMS
in this way and it works:
$.extend(PM.OL.Theme.olNativeThemes,
{
create: function() {
this.themeList['vmapLayerWms2'] = this.createVmapWmsLayer();
You are right, but in my tests I had bad experience with OL 2.13.1.
I realised poor performance of Zoom function/rendering with vector features
on google base layer.
I think this is a OL 2.13.1 issue
you're right, OL 2.13 seems to have some strange performance issues, or
sticky behaviours... Deactivating a layer for example took several
seconds with 2.13.1 which I noticed just recently, and didn't know
why... on 2.12 it was fine again and happened immediately as was with
2.11. So I changed
Some informations may help:
1) in my tests Openlayers 2.11 doesn't work with tilecache (by metacarta -
tilecache.org); version 2.11 is the one integrate in pmapper5;
2) changing it with OL 2.12 (single file) and change pm.ol.customized.js
with the one in the truck
The OL version currently used in p.mapper 5 is 2.13.1
I would recommend to just use an export from pmapper5 svn trunk, not any
old beta version...
On 11/15/2014 11:14 AM, gioza wrote:
Some informations may help:
1) in my tests Openlayers 2.11 doesn't work with tilecache (by metacarta -
It works! excellent work Armin!
If it could help I post my configuration:
Openlayers 2.12 (single file)
pm.ol.customized.js in the truck
My tilecache configuration:
[google-tiles]
type=WMS
url=http://localhost:8080/cgi-bin/mapserv.exe?map=C:\ms4w\apps\esempio\config\default\wms_google.map
I'm trying to make tilecache working with pmapper5.
My aim is to integrate a code that let openlayers render the wms
tile-service created by tilecache.
Great performance for raster rendering...
My first steps:
1) substitute openlayers single file with version 2.12 (only this version
work for me)
One small part regarding layers that was planned but never implemented
is a kind of OL native type. Meaning layer creation of whatever type
using only OL standard functions defined by users via customized code
that are then added to the map in the order how they are defined in the
config
Hi Armin,
I think it would be a great improvement. I am trying to get it with a
workaround as I described in the post above but it isn't a good way, i khow.
in my opinion to use tms or wmsc service directly from ol will make pmapper5
perfect.
Giovanni
--
View this message in context:
I added a basic support for native OL layer types. See changeset
http://svn.pmapper.net/trac/changeset/1359
should work when called the application with ?config=dev since all of
that new type is defined in the dev configuration.
The custom.js needs to create and reference the native layers
I am going to test it right now.
As far as the wiki page is concerned I am interested to update it...someone
may let me khow how to do it...sorry
--
View this message in context:
http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Tilcache-in-pmapper5-tp4025488p4025668.html
Hi all,
As Pmapper5 integrates openlayers, theoretically, I think, it's possible to
use WMS-C service like Tilecache (metacarta). Any ideas?
Thanks
--
View this message in context:
http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Tilcache-in-pmapper5-tp4025488.html
Sent
18 matches
Mail list logo
