KML markers have recently disappeared from Google Maps - google-maps-api-3

About half a year ago I created a Google Maps application (v3) which loads a number of placemarks from a KML file ( http://www.ioors.nl/projects.kml ). This used to work without any problems. Recently though, I have noticed that the markers are not visible anymore in the map. When I load the KML file in maps.google.com the placemarks are listed on the left, but the markers aren't visible there either.
After running a few tests this problem would seem the be caused by style element. Leaving it out makes the markers visible.
I have also tested this with some sample KML code from Google ( https://developers.google.com/kml/documentation/kmlreference#balloonstyle ) and the same problem seems to occur there.
Has Google Maps' support for KML changed recently (can't find anything on Google about that though) or is something else causing the problem?
Any help in this matter would be greatly appreciated.
Kind regards,
Wilco Kuyper

Something did change recently (about 1 week ago) related to Google Maps support for KML. Right near the end of last month, there were a number of developers here on Stack Overflow with questions about the number of KML layers being limited to 5. An issue was logged on the Google Maps Issues site and it was fixed very soon afterwards. You may have run into an additional issue.
Since the problem you are seeing is also present on the Google sample code, it sounds like there is an issue. I'd double-check everything, make sure you have a true issue, and then visit the link above to submit a new issue.

Make sure your scale element is correct. The Google Maps API KML parser is now honouring it (as well as hotSpot).

Related

How to check for live issues with google tag manager?

Previously working code that downloads a csv file from our site, now fails. Chrome, Safari and Edge don't display anything helpful except "Blob Blocked", but Firefox shows a stack trace;
Uncaught TypeError: Location.href setter: Access to 'blob:http://oursite.test/7e283bab-e48c-a942-928c-fae0907fdc82' from script denied.
Then a stack dump from googletagmanager
This appears to be a fault in the tagmanager code introduced in the last couple of weeks.
The fault appears in all browsers and is resolved immediately by commenting out the tag manager. The problem reported by a customer on the production system, and then found on both staging and locally. The customer advised they had used the export function successfully 2 weeks ago.
The question really is, do Google maintain a public facing issues log for things like the tag manager?
It's not about GTM as a library really, it's about poor user implementation. It's not up to Google to check for user-introduced conflicts with the rest of the site's functionality.
What you could do is go to GTM, and see what has been released in the past two weeks. Inspect things and look for anything that could interfere with the site's functionality. At the same time - do the opposite, see all the front-end changes introduced during this time frame by the web-dev team.
Things to watch for is mostly unclosured JS deployed in custom HTML tags. junior GTM implementation specialists like to use the global space, taking the global variables, often after the page is loaded, thus overwriting front-end's variables.
Sometimes, people would deploy minified unclosured code to the DOM, thus chaotically taking short var names. To the same end.
This is likely the easiest and most common way for GTM to break front-end. There definitely still are many ways to do so besides this though.
If this doesn't help, there's another easy way to debug it: make a new workspace from Default (or whatever is live), go into the preview mode and confirm that the issue still happens. Now start disabling newest created fired tags one by one and pinpoint which one causes the issue.
Let us know what it was.
Solution was to replace the previous tag manager code with the latest recommended snippet

Why is my Google streetview suddenly displaying only photo-spheres made by Google?

I'm working on an app that focuses on displaying Google Streetview photo-spheres. I'm using v=3.exp in my app. Until yesterday, about 90% of the photo-spheres I would routinely view by going to a random LatLng and finding the nearest photo-sphere were NOT photographed by Google Inc but by individuals. Which I like very much. Now, all of a sudden, I can't view any of such panoramas, only ones photographed by Google. What gives?
Google is working on adding new functionality (StreetViewSource) to the API, it is possible that things are not yet working correctly. That new functionality is not yet documented in the Developers' Guide (at least that I can find today) so it is hard to say how it is expected to work.
There was a request to not return indoor panorama's when not desired that has been recently marked as "fixed".
Not sure what version of the API you are requesting, but the "experimental" release (currently v=3.21) is just that, experimental, it may break at any time. If you don't see the same issue with the "release" version (currently v=3.20), you may want to file an bug report as v3.21 will eventually become the release version (according to this post, August 18th...).

Google Analytics multiple codes

Normally when I add a html piece to my site, it will create a box that lets me know it's there. It' finicky though and the box didnt show up. So I added the html again, and it didnt tell me it was there. So I published the website and then went to a few pages to see if it worked. It did, and now each page is being tracked multiple times. Then I had the bright idea to redo the tracking code and add that hoping the new code would only be seen once. Not only is it picking up the new code, but the old one as well. Each pageview is being seen as three.
And like I said, my html builder blocks are not showing up on my builder, so I cant get rid of them. Is there a way I can fix this, or do I have to delete my whole file and re-do my analytics? If so, can anyone help me do that?
Tracking code show the real time data or the data of past day.
So if anyone has the above mentioned issue, he need to wait at least 24 hours to get correct reporting through Google Analytic.

google map custom markers in kmlLayer

I have a problem loading the google map custom markers in kmlLayer.
The custom markers become very tiny recently.
http://apdrc.soest.hawaii.edu/gg/rainSD2.php
It was working before. Does anyone know the problem on that?
Is that the google map API server problem?
Does google map API change the setting for custom markers size?
Thanks for helping.
Google announced a change to KML rendering that was scheduled to take place in mid-July. It wouldn't surprise me if this included support of the scale tag. Are your icons not standard sized? Should they be scaled?
Looking at your KML, you are scaling your icons:
<scale>0.25</scale>
If you apply that to your icons which are 32x32, they end up being 8x8, and the dot is already a pretty small chunk of the real estate.
If you change the scale to 1.0, I think it will display as you expect (once the cache on google's servers updates).

Google maps api marker info in sidebar

I'm currently creating an interactive web map using Google Maps Javascript API version 3. I'm not sure if this is possible but I would like to create a series of map layers consisting of different kml files that could be toggled from the side bar. I would also like to be able to access the individual points within the kmls so that when the user clicks on a particular point, photos, text etc. can be loaded outside the map window...
Any ideas on how to accomplish this? I've been searching for a while and only found ways of configuring the infowindow which I personally find unattractive...
There is a way to load KML into a google maps application natively, there is actually a pretty good example of how this is done here:
http://gmaps-samples-v3.googlecode.com/svn/trunk/layers/layers.html
One trick I will mention is that since the KML is downloaded to Google's servers in order to be rendered on the map, it must exist on a public facing web server somewhere, Google won't be able to access it from your local machine.
I found this tutorial which seems like it'll do the trick!

Resources