--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
Chris--
Chris--
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
google.load('visualization', '1.1', {packages: ['geochart'], callback: getData(url) });
google.load('visualization', '1.1', {packages: ['geochart'], callback: function () {
getData(url);
}});
--
Awesome that worked, thanks. I thought about a sorting problem, or possibly allowing only US- provinces, which is why I created a US-ZZ, but the mapList problem still existed.My solution was I basically modified all of your files of your API and it was completely hosted on my domain, which would probably violate a few terms of services, but I wouldn't provide a link or information on how to do that on a general chat like this.
--
--
--
Okay, this is going to be extremely tricky. The GeoChart expects everything to be under a base URL, the maps source. By default, the maps source is set to "https://www.gstatic.com/charts/geochart/10/". You can set a new maps source by calling google.visualization.GeoChart.setMapsSource(newSourceUrl), where newSourceUrl is your new URL (for example, newSourceUrl = 'http://chrisdblumberg.com/maps/'). From this point on, you could figure out what resources the GeoChart is requesting yourself, and place them there one by one; but I'm going to help you a bit more.Your file isn't formatted correctly. It's not even valid javascript. You're missing braces around all your features and you're not closing a lot of the braces and brackets that you do have. Your lat/longs aren't supposed to be formatted as a single string, but as two separate strings, as they are in the example file. However, because I'm an unreasonably nice person, I've decided to help you with all of those problems. So here is the fixed map file, and here is a jsfiddle using it. But I'm sure you'll notice a few funny things happening. The first thing is that all the counties look off on the Y axis. This is because all the coordinates are supposed to be in projected Mercator space, like I mentioned in my last response. You can find the formula for converting your coordinates on the Mercator Projection Wikipedia page. For mercator, you only need to project the latitude, and not the longitude, so it's pretty easy. For simplicity sake, you can just use the formula below:projectedLatitude = (180 / PI) * log(tan(latitude / 180 * PI / 2 + PI / 4));The other thing that you may notice is that the regions in my example aren't being highlighted. This is a harder problem to solve. It's happening because the GeoChart tries to geocode the IDs without ever checking if the given IDs match the map IDs. This is a bug. Kind of. Until I figure out a permanent fix, you're going to have to hack around it. The trick here is to fit the format of a province code so that the GeoChart doesn't fall back on geocoding. The GeoChart will fall back on geocoding (in the case of a province) if the ID doesn't match the format of "two letters, followed by a dash, followed by two alphanumeric characters". One way to get around this problem is to encode your provinces as hex, and use AL as the 'country code' (I put it in quotes because it's not really the country code, and using US-AL-XX doesn't work). So, since everything is in the format of US-AL-1DDD (where D's are digits), and all the codes -1000 are under 255, we can encode them as hex. So US-AL-1001 becomes AL-01, US-AL-1005 becomes AL-05, US-AL-1010 becomes AL-0A, and so on. Here is a demo where that works. Note that I'm using a different path there and loading a different map, where all the counties are renamed.The other polygons in that file are the other states. Good call on leaving them alone, since now you can make sure that your counties match up to them, and you can have some context for what you're looking at.- SergeyOn Tue, Jul 9, 2013 at 2:48 PM, Bluestreak2k5 <Bluest...@yahoo.com> wrote:
Thanks so much Sergey!I have converted the KML to a JS file like you linked me to, it is here:I replaced the polygon id="US-AL" with all the polygons of the individual counties.Each county is represented by an ID using the FIPS code, such as US-AL-1001 would represent Autauga county in Alabama. This should allow for easy future expansion as this is a Unique identifier to each county.How would I go about testing this map now, and would this be the correct way of doing it? I wasn't sure about the other polygons that were in that file so I left them all alone and are located at the bottom.Chris
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/d/optout.
Ok so I know google Charts doesn't support viewing county data, but I would like to know if it would be possible to create my own custom Map that would.Another Google Team has created an experimental App called Fusion Tables. Not sure why these 2 aren't integrated, but irrelevant...They have a Map with all the US counties already mapped out in KML located here:Could I create a custom map to use this KML data to draw items in Google Charts, which from my understanding uses SVG images.Things I would like to start off with:Each state would have an option to load its counties (Loading all counties as a map would be a long term goal, but seems to be more difficult at the moment.)I could then use the GEO_ID or GEO_ID2 as the unique Identifiers for each county, allowing you to map data to each county the way you currently use State ISO codes to map to each state.It could alos look something like US-AL-1001 being the country-(State/Region)-(county FIP CODE) to allow for expandability into future countries.Chris
If I remember correctly (and it has been a while), it would be AL14. The way that this works is that we drop the initial "10" because it's redundant between all the counties, and just convert the second part to hex. So in your example, we would just want the hex value of 20. However, all of this is kind of moot at this point, since the GeoChart has been changed to not ignore invalid-looking region codes. So using AL-1010 should work now. However, if you're using Blue's maps, that's irrelevant to you because he has coded them to use the hex encoding already and you can't change that. I simply bring it up if you are making your own maps.
- Sergey
On Thu, Mar 20, 2014 at 3:14 PM, Peter Chon <peter...@gmail.com> wrote:
Hi Segey,I know this is quite old, but can you give me a few more example of how the hex encoding works?
for example: if 1010 = AL0A, then what would 1020 be?
On Tuesday, July 9, 2013 1:36:04 PM UTC-7, Sergey wrote:
Okay, this is going to be extremely tricky. The GeoChart expects everything to be under a base URL, the maps source. By default, the maps source is set to "https://www.gstatic.com/charts/geochart/10/". You can set a new maps source by calling google.visualization.GeoChart.setMapsSource(newSourceUrl), where newSourceUrl is your new URL (for example, newSourceUrl = 'http://chrisdblumberg.com/maps/'). From this point on, you could figure out what resources the GeoChart is requesting yourself, and place them there one by one; but I'm going to help you a bit more.Your file isn't formatted correctly. It's not even valid javascript. You're missing braces around all your features and you're not closing a lot of the braces and brackets that you do have. Your lat/longs aren't supposed to be formatted as a single string, but as two separate strings, as they are in the example file. However, because I'm an unreasonably nice person, I've decided to help you with all of those problems. So here is the fixed map file, and here is a jsfiddle using it. But I'm sure you'll notice a few funny things happening. The first thing is that all the counties look off on the Y axis. This is because all the coordinates are supposed to be in projected Mercator space, like I mentioned in my last response. You can find the formula for converting your coordinates on the Mercator Projection Wikipedia page. For mercator, you only need to project the latitude, and not the longitude, so it's pretty easy. For simplicity sake, you can just use the formula below:projectedLatitude = (180 / PI) * log(tan(latitude / 180 * PI / 2 + PI / 4));The other thing that you may notice is that the regions in my example aren't being highlighted. This is a harder problem to solve. It's happening because the GeoChart tries to geocode the IDs without ever checking if the given IDs match the map IDs. This is a bug. Kind of. Until I figure out a permanent fix, you're going to have to hack around it. The trick here is to fit the format of a province code so that the GeoChart doesn't fall back on geocoding. The GeoChart will fall back on geocoding (in the case of a province) if the ID doesn't match the format of "two letters, followed by a dash, followed by two alphanumeric characters". One way to get around this problem is to encode your provinces as hex, and use AL as the 'country code' (I put it in quotes because it's not really the country code, and using US-AL-XX doesn't work). So, since everything is in the format of US-AL-1DDD (where D's are digits), and all the codes -1000 are under 255, we can encode them as hex. So US-AL-1001 becomes AL-01, US-AL-1005 becomes AL-05, US-AL-1010 becomes AL-0A, and so on. Here is a demo where that works. Note that I'm using a different path there and loading a different map, where all the counties are renamed.The other polygons in that file are the other states. Good call on leaving them alone, since now you can make sure that your counties match up to them, and you can have some context for what you're looking at.
- Sergey
On Tue, Jul 9, 2013 at 2:48 PM, Bluestreak2k5 <Bluest...@yahoo.com> wrote:
Thanks so much Sergey!I have converted the KML to a JS file like you linked me to, it is here:I replaced the polygon id="US-AL" with all the polygons of the individual counties.Each county is represented by an ID using the FIPS code, such as US-AL-1001 would represent Autauga county in Alabama. This should allow for easy future expansion as this is a Unique identifier to each county.How would I go about testing this map now, and would this be the correct way of doing it? I wasn't sure about the other polygons that were in that file so I left them all alone and are located at the bottom.
Chris--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualizati...@googlegroups.com.
--
--
--
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
<html>
<head>
<script type='text/javascript' src='https://www.google.com/jsapi'></script>
<script type='text/javascript'>
google.load('visualization', '1', {'packages': ['geochart']});
google.setOnLoadCallback(drawMarkersMap);
function drawMarkersMap() {
var data = google.visualization.arrayToDataTable([
['Prov', 'Youth %', 'Overall %'],
['CA-PE', 51.6, 70.4],
['CA-NL', 29.6, 53.3],
['CA-NB', 41.6, 65.6],
['CA-NS', 37.6, 61.3],
['CA-QC', 45.0, 63.5],
['CA-ON', 38.2, 57.6],
['CA-MB', 31.9, 55.7],
['CA-SK', 30.1, 59.6],
['CA-AB', 33.7, 52.3],
['CA-BC', 39.9, 55.9],
['CA-YT', 40.2, 62.5],
['CA-NT', 25.2, 47.4],
['CA-NU', 14.6, 39.4],
]);
var options = {
region: 'CA',
displayMode: 'markers',
colorAxis: {colors: ['red', 'green', 'blue']}
};
var chart = new google.visualization.GeoChart(document.getElementById('chart_div'));
chart.draw(data, options);
};
</script>
</head>
<body>
<div id="chart_div" style="width: 900px; height: 500px;"></div>
</body>
</html>
Ok so I know google Charts doesn't support viewing county data, but I would like to know if it would be possible to create my own custom Map that would.Another Google Team has created an experimental App called Fusion Tables. Not sure why these 2 aren't integrated, but irrelevant...They have a Map with all the US counties already mapped out in KML located here:Could I create a custom map to use this KML data to draw items in Google Charts, which from my understanding uses SVG images.Things I would like to start off with:Each state would have an option to load its counties (Loading all counties as a map would be a long term goal, but seems to be more difficult at the moment.)I could then use the GEO_ID or GEO_ID2 as the unique Identifiers for each county, allowing you to map data to each county the way you currently use State ISO codes to map to each state.It could alos look something like US-AL-1001 being the country-(State/Region)-(county FIP CODE) to allow for expandability into future countries.Chris
--
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
...
Hi, I am trying to follow this instructions to create a map for states in Nigeria. However, the demo here "Here is a demo where that work" no longer works. Do you know why it no longer works?
On Tuesday, July 9, 2013 at 9:36:04 PM UTC+1, Sergey wrote:
Okay, this is going to be extremely tricky. The GeoChart expects everything to be under a base URL, the maps source. By default, the maps source is set to "https://www.gstatic.com/charts/geochart/10/". You can set a new maps source by calling google.visualization.GeoChart.setMapsSource(newSourceUrl), where newSourceUrl is your new URL (for example, newSourceUrl = 'http://chrisdblumberg.com/maps/'). From this point on, you could figure out what resources the GeoChart is requesting yourself, and place them there one by one; but I'm going to help you a bit more.Your file isn't formatted correctly. It's not even valid javascript. You're missing braces around all your features and you're not closing a lot of the braces and brackets that you do have. Your lat/longs aren't supposed to be formatted as a single string, but as two separate strings, as they are in the example file. However, because I'm an unreasonably nice person, I've decided to help you with all of those problems. So here is the fixed map file, and here is a jsfiddle using it. But I'm sure you'll notice a few funny things happening. The first thing is that all the counties look off on the Y axis. This is because all the coordinates are supposed to be in projected Mercator space, like I mentioned in my last response. You can find the formula for converting your coordinates on the Mercator Projection Wikipedia page. For mercator, you only need to project the latitude, and not the longitude, so it's pretty easy. For simplicity sake, you can just use the formula below:projectedLatitude = (180 / PI) * log(tan(latitude / 180 * PI / 2 + PI / 4));The other thing that you may notice is that the regions in my example aren't being highlighted. This is a harder problem to solve. It's happening because the GeoChart tries to geocode the IDs without ever checking if the given IDs match the map IDs. This is a bug. Kind of. Until I figure out a permanent fix, you're going to have to hack around it. The trick here is to fit the format of a province code so that the GeoChart doesn't fall back on geocoding. The GeoChart will fall back on geocoding (in the case of a province) if the ID doesn't match the format of "two letters, followed by a dash, followed by two alphanumeric characters". One way to get around this problem is to encode your provinces as hex, and use AL as the 'country code' (I put it in quotes because it's not really the country code, and using US-AL-XX doesn't work). So, since everything is in the format of US-AL-1DDD (where D's are digits), and all the codes -1000 are under 255, we can encode them as hex. So US-AL-1001 becomes AL-01, US-AL-1005 becomes AL-05, US-AL-1010 becomes AL-0A, and so on. Here is a demo where that works. Note that I'm using a different path there and loading a different map, where all the counties are renamed.The other polygons in that file are the other states. Good call on leaving them alone, since now you can make sure that your counties match up to them, and you can have some context for what you're looking at.
- Sergey
On Tue, Jul 9, 2013 at 2:48 PM, Bluestreak2k5 <Bluest...@yahoo.com> wrote:
Thanks so much Sergey!I have converted the KML to a JS file like you linked me to, it is here:I replaced the polygon id="US-AL" with all the polygons of the individual counties.Each county is represented by an ID using the FIPS code, such as US-AL-1001 would represent Autauga county in Alabama. This should allow for easy future expansion as this is a Unique identifier to each county.How would I go about testing this map now, and would this be the correct way of doing it? I wasn't sure about the other polygons that were in that file so I left them all alone and are located at the bottom.
Chris--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/de02f3f1-63e5-4ecf-bce0-2dc2551dff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/de02f3f1-63e5-4ecf-bce0-2dc2551dff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOFbNz4u%3DWvgm%2BNmH2Dex%3Dydzv-ohqOr6aqDW5gL_%2BW_Q%40mail.gmail.com.
To unsubscribe from this group and all its topics, send an email to google-visualizati...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CADvusYQtHkWKrn9dMghDbDPF8ynjLrO5TPOCj-m%2BYk%3DZ5MjqDA%40mail.gmail.com.
- Sergey
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/de02f3f1-63e5-4ecf-bce0-2dc2551dff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
- Sergey
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/de02f3f1-63e5-4ecf-bce0-2dc2551dff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOFbNz4u%3DWvgm%2BNmH2Dex%3Dydzv-ohqOr6aqDW5gL_%2BW_Q%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/facc5b9a-1914-4cd0-ac22-dd017d6da45f%40googlegroups.com.
- Sergey
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/de02f3f1-63e5-4ecf-bce0-2dc2551dff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOFbNz4u%3DWvgm%2BNmH2Dex%3Dydzv-ohqOr6aqDW5gL_%2BW_Q%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
"boundingBox": { "hi": ["77.0065", "-102.1900"], "lo": ["53.4563", "-131.1100"] },
https://www.gstatic.com/charts/geochart/10/mapfiles/world_COUNTRIES.js
"boundingBox": {"hi": ["165.1534", "186.8392"], "lo": ["-68.0595", "-186.8392"]}
- Sergey
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/de02f3f1-63e5-4ecf-bce0-2dc2551dff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOFbNz4u%3DWvgm%2BNmH2Dex%3Dydzv-ohqOr6aqDW5gL_%2BW_Q%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/facc5b9a-1914-4cd0-ac22-dd017d6da45f%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/998f5867-b7e6-49b6-a371-37224213b3d1%40googlegroups.com.
Ok so I know google Charts doesn't support viewing county data, but I would like to know if it would be possible to create my own custom Map that would.Another Google Team has created an experimental App called Fusion Tables. Not sure why these 2 aren't integrated, but irrelevant...They have a Map with all the US counties already mapped out in KML located here:Could I create a custom map to use this KML data to draw items in Google Charts, which from my understanding uses SVG images.Things I would like to start off with:Each state would have an option to load its counties (Loading all counties as a map would be a long term goal, but seems to be more difficult at the moment.)I could then use the GEO_ID or GEO_ID2 as the unique Identifiers for each county, allowing you to map data to each county the way you currently use State ISO codes to map to each state.It could alos look something like US-AL-1001 being the country-(State/Region)-(county FIP CODE) to allow for expandability into future countries.
Chris
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/KVGu--jjUpk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/160ea933-1335-4441-a334-9566c80fbeff%40googlegroups.com.
<html> <head> <script>Enter code here...
google.script.run.doSomething(); </script> </head> <body> </body></html>
function doGet(){ return HtmlService.createHtmlOutputFromFile('Index');}function doSomething(){ Logger.log("What");}
UrlFetchApp.fetch(theURL,{method:"Get", headers: {Authorization: "Bearer "+ScriptApp.getOAuthToken()}, muteHttpExceptions: true});
<script type='text/javascript' src='https://www.google.com/jsapi'></script>
<html>
function doGet(){ return HtmlService.createHtmlOutputFromFile('Index');}
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/d44172a8-6e07-4f0a-8c4f-f8c2210052c1o%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMzBEu0ut9DNwXeUpXwvMtdm9XBHXbgSWSbEGaQvR9CQg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CADsXKFVY9UhSm7Z3CP3qsLWM04WA96Dwb_r-5%3D8CsrdmPycZig%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMW_aVOw7HLf_%2ByY%2BEOMtCxR9jZg0R3armEm93MySO8iQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CADsXKFUXmKi5Bbri%2BRQAgyyj1K5%2BdU-quVeuv3MF_%3Dg49Gunvg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJObpLyw2%2BT%3D26dD%3DkQVKH4_Kx9fC-zVjU4YQR332pfgKA%40mail.gmail.com.
"Access to XMLHttpRequest at 'https://varsha2509.github.io/maps/info/mapList.js' from origin 'http://varshg.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."
< Access-Control-Allow-Origin: *< Access-Control-Allow-Origin: *
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/889d55e4-98df-45b8-857a-d55937182199n%40googlegroups.com.