Databases
StackOverflow2013
Postsdbo
PORequest-URI Too Large (Fusion table layers Google Maps)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORequest-URI Too Large (Fusion table layers Google Maps)
    primarykey
    data
    text
    <p>I am trying to put the fusion table layer data on my <code>Google Map</code> but I am getting an error <strong>Request-URI Too Large</strong>. I searched a lot but couldn't find how can I make it work either by POST method or something else. The problem is the <code>where clause</code> but I can't shorten the where clause. Is there anyone who can help me or guide me?</p> <p>Thanks in advance for any help.</p> <pre class="lang-js prettyprint-override"><code>layer = new google.maps.FusionTablesLayer({ map: googleMap, heatmap: {enabled: false}, query: { select: "col4", from: "tableID", where: "", }, styles: [{ polygonOptions: { fillOpacity: 0.3 } }, { where: "col0 in ('Jefferson','Pulaski','Los Angeles','Denver','Middlesex','New Castle','Duval','Pinellas','Lee','Broward','Fulton','Cobb','Ada','Tazewell','Cook','Marion','Hendricks','Putnam','Adams','Boone','Orleans','Plymouth','Baltimore','Washington','Macomb','Genesee','Oakland','Hennepin','Jackson','Shelby','Granite','Forsyth','Mecklenburg','Wake','Douglas','Gloucester','Passaic','Bernalillo','Sandoval','Clark','New York','Montgomery','Hamilton','Tulsa','Oklahoma','Multnomah','Lane','Chester','Philadelphia','York','Lehigh','Kent','Horry','Davidson','Travis','Harris','Dallas','Fairfax','Chesterfield','King','Brown','Laramie','Kalamazoo','Cabarrus','San Diego','Pennington','Richland','Weber','Ramsey','Hartford') AND col3 in ('AL','AR','CA','CO','CT','DC','DE','FL','GA','ID','IL','IN','WV','OH','KY','LA','MA','MD','MI','MN','MO','TN','MT','NC','NE','NJ','NM','NV','NY','OK','OR','PA','RI','SC','TX','VA','VT','WA','WI','WY','SD')", polygonOptions: { fillColor: '#ffffff', strokeColor: '#ff0000', fillOpacity: 0.3 } }], options: { styleId: 1, templateId: 2 } }); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpbaris
    1. USDead Man
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORequest-URI Too Large (Fusion table layers Google Maps)
      1. USDead Man
      1. VTFavorite
    2. VO
      singulars
      1. PORequest-URI Too Large (Fusion table layers Google Maps)
      1. This table or related slice is empty.
      1. VTUndeletion
    3. VO
      singulars
      1. PORequest-URI Too Large (Fusion table layers Google Maps)
      1. USDead Man
      1. VTBountyStart
    1. COWhy do you say you can't shorten the where clause? Can't you add a new column with a 2 or 3 character/digit unique code and replace col0 (county?)? Or use a [FIPS](http://en.wikipedia.org/wiki/FIPS_county_code) or other defined number?
      singulars
      1. PORequest-URI Too Large (Fusion table layers Google Maps)
      1. USgeocodezip
    2. COA solution for this could be to create a view based on the above query. Then you just have to query the view.
      singulars
      1. PORequest-URI Too Large (Fusion table layers Google Maps)
      1. USdavidkonrad
    3. COThat query is dynamic so i can't create view based on any query.
      singulars
      1. PORequest-URI Too Large (Fusion table layers Google Maps)
      1. USDead Man
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload