Hello,
I just noticed that layers on JB Maps module doesn't work anymore.

I have not edited this module since the last time when everything was working properly. The original map on Google Maps is correct, it's JB Maps which no longer displays the layers.
Here is how the map was displayed on the website and on Google Maps:
www.google.com/maps/d/edit?mid=zGTe-QOCrITg.kdIIymRzoaWc&usp=sharing

... and here how it appears at the moment on the website:
www.scorrendoconilliri.it/percorso/altimetria-cartografia

I tried to activate other layers as weather layer, cloud layer and traffic layer, but I've the same problem, layers are not displayed. Same results also with a kml or kmz file.

Thank you

Hi

I'll need to check regarding some of your question but I think some elements have been depreciated by Google so don't display

Do you have the latest version of the module installed?

Cheers
Paul

To clarify I'm talking about weather and other effects

I will check with Rob in the morning (UK time)

Cheers
Paul

... I've just upgraded the module to 1.0.3 version to 1.2.0, emptied the cache, but the problem is still there
thank you

Hi Lorenzo,

Yes I'm pretty certain that was deprecated by Google and is no longer available.
Thanks

Hello Anthony,
… deprecated? All them? ...then why the map is displayed correctly when I share it? … and what is the benefit to display a map without informations? …display a map with just a path?
I can understand that some layers have been deprecated, such as the weather layer (even if it sounds strange to me), but that all layers have been deprecated this seems unlikely
Then how to display informations on a path? When I say "informations" I'm referring to markers.

Thank you

With the layers

Can you check out our documentation -

docs.joomlabamboo.com/joomla-extensions/jb-maps2-documentation#markers

"Note: The weather, cloud and panoramio layers have been discontinued by Google and will no longer work. These options have been removed from the module. More information: Google Developers Blog"

developers.google.com/maps/documentation/javascript/layers?hl=en

You can a marker by clicking in the map and entering text for it

Cheers
Paul

Hello,

I just need to restore markers which have been configured in Google Maps and exported in KMZ format, they are gone in JB Maps and I don't know why...
... so if I understand the KMZ and KML files are no longer valid in JB Maps?

Hello again
... can you answering me about this KMZ file that is no longer taken into account?

Thank you

Sorry I don't know the answer to this so I was waiting to ask the developers on monday

Cheers
Paul

Once I've spoken to them I will get back to you

Cheers

Hi,

I can see that the kmz file is loading on the map.

As the markers are embedded into the kmz file then it must be an issue between the kmz file and the maps api.

They may have made changes around the same time as they removed the other layers.

How did you create the file?

Can you try exporting it again after any updated in the program you use to see if that fixes the issue?

Are you able to export as a kml file so it's readable?

Regards,

Rob

Hello,
as I explained in my first message I have not edited this module since the last time when everything was working properly, marker have suddenly stopped to be displayed
Just exported the map from the Google Maps menu via the export KML option

I've tried several times to exporting the file in KML and KMZ format, but I've always the same result -> just a path without markers.
If I upload these same files on another service online (eg. www.gpsvisualizer.com/) the markers are visible, so I guess that the issue is in JB Maps...

Thank you

Hi,

I am not talking about any changes to the module.

The issue is between your kmz file and Google's api.

All the module does is add a link to the file for the map to add as an overlay.
It is clearly being loaded as you can see the path on the map.

Have you tried adding the kmz file to the main domain rather than loading it from a subdomain?

test-scorrendo.scorrendoconilliri.it/images/scorrendo-files/scorrendo.kmz

Can you please attach the kml version so we can test it with a human readable version?

Thanks,

Rob

Hello Rob and sorry for the late reply but I was traveling.
Yes I tried on the primary domain and the result is the same...

Thank you again

... here are the Google Maps files...

Hi,

When I open the kml file it only contains a link which results in a 404 not found error.

When I try and import the kmz file into Google's 'My Maps' I get the message

A network link in the KML file is not accessible or it is not formatted as a KML file.

So I think the issue is with the link in the kmz file not being web accessible and the kml file being invalid.

I have just recreated the map as a valid kml file and tested it with markers and it is working correctly.

You need to go through the file and replace each styleUrl tag with a link to a marker icon eg

Regards,

Rob

The forum didn't like the file...

Thank you for the support, but I don't quite understand what I need to do ...
Which is the file that I need to edit? KML file or KMZ file?
I think KML file is updated with my Google Maps account each 10 minutes, but if I upload your file I guess it will no longer synchronized with my map?

Another thing: I can open KML files with a text editor, but what is the application to open the KMZ file?

This behaviour is very strange because if I import the problematic file to eg. www.gpsvisualizer.com, markers are visible, why are not visibles on JB Maps module?
Am I to understand that saving KML/KMZ files from Google Maps doesn't work anymore?

Thank you again for these clarifications

EDIT:

ok, I replaced each tag and it works but if you could answer to my questions it would help me to understand what happened with my old map...

Thank you

Hi,

A kmz file is compiled and you cannot edit it manually.

It's hard to see the exact reason for this happening as it's not possible to see the contents of either of the original files. One is compiled and the other links to a 404 page.

At some point, Google must have made a change to either the maps api, or the way the km* files are exported from the my maps application.

I have seen some bug reports about this so it is hopefully something they will fix soon.

I would assume that it happened when they made the changes to the api regarding the other layers, but that's really just a guess.

It's not something that can be fixed with a change to the module code as the issue is between the maps api and the files that their own map application outputs.