Uncaught SyntaxError: Unexpected token < (Geoserver popup in leaflet using ajax) Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Wrong data with FEATURE_COUNT=1 for GetFeatureInfoLat/long Values in the geoserver's WMS GetFeatureInfo RequestIs it possible to get GeoJSON geometry from GetFeatureInfo WMS request from ArcGIS Server 10.xGetFeatureInfo in WMS using a box?How to highlight a feature in wms map imageDisplay a map using leaflet APIBrowser display nothing when debugging leaflet api file to connect to geoserverOpenlayers 3 getGetFeatureInfoUrl geoserver problemWMS returns but WFS does not return same SRS and BBOX valuesGeoserver WMS - CORS enabled in web.xml - still error
The test team as an enemy of development? And how can this be avoided?
Relating to the President and obstruction, were Mueller's conclusions preordained?
Tips to organize LaTeX presentations for a semester
Connecting Mac Book Pro 2017 to 2 Projectors via USB C
I can't produce songs
Why do early math courses focus on the cross sections of a cone and not on other 3D objects?
Did Mueller's report provide an evidentiary basis for the claim of Russian govt election interference via social media?
What adaptations would allow standard fantasy dwarves to survive in the desert?
What are the main differences between Stargate SG-1 cuts?
What is the chair depicted in Cesare Maccari's 1889 painting "Cicerone denuncia Catilina"?
Tannaka duality for semisimple groups
Project Euler #1 in C++
Should a wizard buy fine inks every time he want to copy spells into his spellbook?
Asymptotics question
Why is it faster to reheat something than it is to cook it?
Omitting the following parentheses
Getting out of while loop on console
Select every other edge (they share a common vertex)
Nose gear failure in single prop aircraft: belly landing or nose-gear up landing?
Short story about a child who is a miniature, living Earth
Co-worker has annoying ringtone
Is there public access to the Meteor Crater in Arizona?
Why does electrolysis of aqueous concentrated sodium bromide produce bromine at the anode?
How much damage would a cupful of neutron star matter do to the Earth?
Uncaught SyntaxError: Unexpected token
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Wrong data with FEATURE_COUNT=1 for GetFeatureInfoLat/long Values in the geoserver's WMS GetFeatureInfo RequestIs it possible to get GeoJSON geometry from GetFeatureInfo WMS request from ArcGIS Server 10.xGetFeatureInfo in WMS using a box?How to highlight a feature in wms map imageDisplay a map using leaflet APIBrowser display nothing when debugging leaflet api file to connect to geoserverOpenlayers 3 getGetFeatureInfoUrl geoserver problemWMS returns but WFS does not return same SRS and BBOX valuesGeoserver WMS - CORS enabled in web.xml - still error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
1
I am trying to show attribute information of features in a popup from my postGIS db tables via Geoserver WMS.
I have successfully been able to add these layers to the map. However, when I try to grab the attribute information for the same layers via Ajax, console prints an error message stating Uncaught SyntaxError: Unexpected token <
On the other hand, the status for URL is 200 i.e. ok as can be seen here:
Still, the preview of this query is
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1" >
<ServiceException code="LayerNotDefined" locator="layers">
Could not find layer workspace:
</ServiceException>
</ServiceExceptionReport>
Below are my query string parameters
1. Query String Parameters (17)
2. SERVICE: WMS
3. version: 1.1.0
4. request: GetFeatureInfo
5. layers: workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
6. styles:
7. bbox: 74.22517776489258,31.487235582017444,74.4019889831543,31.559668260234595
8. feature_count: 1
9. width: 1030
10. height: 495
11. format: image/png
12. srs: EPSG:4326
13. (empty)
14. x: 247
15. y: 30
16. info_format: text/javascript
17. callback: jQuery20309529768737157973_1547708903539_:1547708903542
Everything seems to be working fine here except that it is unable to find the specified layers. I have cross checked in my geoserver’s web.xml file that jsonp is enabled as can be seen below
I just can’t understand what possibly could go wrong here when I’m successfully calling the same layers in a different function with the same URL and here it doesn’t work.
For further reefrence I’m pasting the code snippet here:
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
geoserver getfeatureinfo ajax
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
|
show 1 more comment
1
I am trying to show attribute information of features in a popup from my postGIS db tables via Geoserver WMS.
I have successfully been able to add these layers to the map. However, when I try to grab the attribute information for the same layers via Ajax, console prints an error message stating Uncaught SyntaxError: Unexpected token <
On the other hand, the status for URL is 200 i.e. ok as can be seen here:
Still, the preview of this query is
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1" >
<ServiceException code="LayerNotDefined" locator="layers">
Could not find layer workspace:
</ServiceException>
</ServiceExceptionReport>
Below are my query string parameters
1. Query String Parameters (17)
2. SERVICE: WMS
3. version: 1.1.0
4. request: GetFeatureInfo
5. layers: workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
6. styles:
7. bbox: 74.22517776489258,31.487235582017444,74.4019889831543,31.559668260234595
8. feature_count: 1
9. width: 1030
10. height: 495
11. format: image/png
12. srs: EPSG:4326
13. (empty)
14. x: 247
15. y: 30
16. info_format: text/javascript
17. callback: jQuery20309529768737157973_1547708903539_:1547708903542
Everything seems to be working fine here except that it is unable to find the specified layers. I have cross checked in my geoserver’s web.xml file that jsonp is enabled as can be seen below
I just can’t understand what possibly could go wrong here when I’m successfully calling the same layers in a different function with the same URL and here it doesn’t work.
For further reefrence I’m pasting the code snippet here:
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
geoserver getfeatureinfo ajax
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
"Syntax error" means that you have a typo somewhere. In the console you can see, where the syntax error occurs. The file and line number are noted on the right side of the console. Click on it and the console will directly lead you to the file and line.
– Stefan
Jan 17 at 8:52
@Stefan This is exactly the issue, when I click on it, it takes me to<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined" locator="layers"> Could not find layer wasa_assert: </ServiceException></ServiceExceptionReport>I have pasted the code snippet above and seemingly there seems to be no error in it.
– DigitalPatwari
Jan 17 at 9:44
Could it be that there is one comma too much at the end here?&layers=wasa_assert%3Atbl_water_supply_network,wasa_assert%3Atbl_tubewells,wasa_assert%3Atbl_ohr,wasa_assert%3Atbl_filtration_plant,wasa_assert%3Atbl_sewer_lines,wasa_assert%3Atbl_lift_station,wasa_assert%3Atbl_disposal_station,
– Stefan
Jan 17 at 10:15
And as you can see in the syntax highlighting in your question, the string cannot be formed like this. Try this jsfiddle.net/newluck77/tz7xefas and if it solves your issue, let me post it as an answer, please. 😉
– Stefan
Jan 17 at 10:40
I tried it didn't solve the issue.
– DigitalPatwari
Jan 17 at 11:01
|
show 1 more comment
1
1
1
I am trying to show attribute information of features in a popup from my postGIS db tables via Geoserver WMS.
I have successfully been able to add these layers to the map. However, when I try to grab the attribute information for the same layers via Ajax, console prints an error message stating Uncaught SyntaxError: Unexpected token <
On the other hand, the status for URL is 200 i.e. ok as can be seen here:
Still, the preview of this query is
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1" >
<ServiceException code="LayerNotDefined" locator="layers">
Could not find layer workspace:
</ServiceException>
</ServiceExceptionReport>
Below are my query string parameters
1. Query String Parameters (17)
2. SERVICE: WMS
3. version: 1.1.0
4. request: GetFeatureInfo
5. layers: workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
6. styles:
7. bbox: 74.22517776489258,31.487235582017444,74.4019889831543,31.559668260234595
8. feature_count: 1
9. width: 1030
10. height: 495
11. format: image/png
12. srs: EPSG:4326
13. (empty)
14. x: 247
15. y: 30
16. info_format: text/javascript
17. callback: jQuery20309529768737157973_1547708903539_:1547708903542
Everything seems to be working fine here except that it is unable to find the specified layers. I have cross checked in my geoserver’s web.xml file that jsonp is enabled as can be seen below
I just can’t understand what possibly could go wrong here when I’m successfully calling the same layers in a different function with the same URL and here it doesn’t work.
For further reefrence I’m pasting the code snippet here:
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
geoserver getfeatureinfo ajax
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
I am trying to show attribute information of features in a popup from my postGIS db tables via Geoserver WMS.
I have successfully been able to add these layers to the map. However, when I try to grab the attribute information for the same layers via Ajax, console prints an error message stating Uncaught SyntaxError: Unexpected token <
On the other hand, the status for URL is 200 i.e. ok as can be seen here:
Still, the preview of this query is
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1" >
<ServiceException code="LayerNotDefined" locator="layers">
Could not find layer workspace:
</ServiceException>
</ServiceExceptionReport>
Below are my query string parameters
1. Query String Parameters (17)
2. SERVICE: WMS
3. version: 1.1.0
4. request: GetFeatureInfo
5. layers: workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
6. styles:
7. bbox: 74.22517776489258,31.487235582017444,74.4019889831543,31.559668260234595
8. feature_count: 1
9. width: 1030
10. height: 495
11. format: image/png
12. srs: EPSG:4326
13. (empty)
14. x: 247
15. y: 30
16. info_format: text/javascript
17. callback: jQuery20309529768737157973_1547708903539_:1547708903542
Everything seems to be working fine here except that it is unable to find the specified layers. I have cross checked in my geoserver’s web.xml file that jsonp is enabled as can be seen below
I just can’t understand what possibly could go wrong here when I’m successfully calling the same layers in a different function with the same URL and here it doesn’t work.
For further reefrence I’m pasting the code snippet here:
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE,
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
geoserver getfeatureinfo ajax
geoserver getfeatureinfo ajax
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
edited Jan 17 at 11:40
DigitalPatwari
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
asked Jan 17 at 7:53
DigitalPatwariDigitalPatwari
398
398
"Syntax error" means that you have a typo somewhere. In the console you can see, where the syntax error occurs. The file and line number are noted on the right side of the console. Click on it and the console will directly lead you to the file and line.
– Stefan
Jan 17 at 8:52
@Stefan This is exactly the issue, when I click on it, it takes me to<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined" locator="layers"> Could not find layer wasa_assert: </ServiceException></ServiceExceptionReport>I have pasted the code snippet above and seemingly there seems to be no error in it.
– DigitalPatwari
Jan 17 at 9:44
Could it be that there is one comma too much at the end here?&layers=wasa_assert%3Atbl_water_supply_network,wasa_assert%3Atbl_tubewells,wasa_assert%3Atbl_ohr,wasa_assert%3Atbl_filtration_plant,wasa_assert%3Atbl_sewer_lines,wasa_assert%3Atbl_lift_station,wasa_assert%3Atbl_disposal_station,
– Stefan
Jan 17 at 10:15
And as you can see in the syntax highlighting in your question, the string cannot be formed like this. Try this jsfiddle.net/newluck77/tz7xefas and if it solves your issue, let me post it as an answer, please. 😉
– Stefan
Jan 17 at 10:40
I tried it didn't solve the issue.
– DigitalPatwari
Jan 17 at 11:01
|
show 1 more comment
"Syntax error" means that you have a typo somewhere. In the console you can see, where the syntax error occurs. The file and line number are noted on the right side of the console. Click on it and the console will directly lead you to the file and line.
– Stefan
Jan 17 at 8:52
@Stefan This is exactly the issue, when I click on it, it takes me to<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined" locator="layers"> Could not find layer wasa_assert: </ServiceException></ServiceExceptionReport>I have pasted the code snippet above and seemingly there seems to be no error in it.
– DigitalPatwari
Jan 17 at 9:44
Could it be that there is one comma too much at the end here?&layers=wasa_assert%3Atbl_water_supply_network,wasa_assert%3Atbl_tubewells,wasa_assert%3Atbl_ohr,wasa_assert%3Atbl_filtration_plant,wasa_assert%3Atbl_sewer_lines,wasa_assert%3Atbl_lift_station,wasa_assert%3Atbl_disposal_station,
– Stefan
Jan 17 at 10:15
And as you can see in the syntax highlighting in your question, the string cannot be formed like this. Try this jsfiddle.net/newluck77/tz7xefas and if it solves your issue, let me post it as an answer, please. 😉
– Stefan
Jan 17 at 10:40
I tried it didn't solve the issue.
– DigitalPatwari
Jan 17 at 11:01
"Syntax error" means that you have a typo somewhere. In the console you can see, where the syntax error occurs. The file and line number are noted on the right side of the console. Click on it and the console will directly lead you to the file and line.
– Stefan
Jan 17 at 8:52
"Syntax error" means that you have a typo somewhere. In the console you can see, where the syntax error occurs. The file and line number are noted on the right side of the console. Click on it and the console will directly lead you to the file and line.
– Stefan
Jan 17 at 8:52
@Stefan This is exactly the issue, when I click on it, it takes me to
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined" locator="layers"> Could not find layer wasa_assert: </ServiceException></ServiceExceptionReport> I have pasted the code snippet above and seemingly there seems to be no error in it.– DigitalPatwari
Jan 17 at 9:44
@Stefan This is exactly the issue, when I click on it, it takes me to
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined" locator="layers"> Could not find layer wasa_assert: </ServiceException></ServiceExceptionReport> I have pasted the code snippet above and seemingly there seems to be no error in it.– DigitalPatwari
Jan 17 at 9:44
Could it be that there is one comma too much at the end here?
&layers=wasa_assert%3Atbl_water_supply_network,wasa_assert%3Atbl_tubewells,wasa_assert%3Atbl_ohr,wasa_assert%3Atbl_filtration_plant,wasa_assert%3Atbl_sewer_lines,wasa_assert%3Atbl_lift_station,wasa_assert%3Atbl_disposal_station,– Stefan
Jan 17 at 10:15
Could it be that there is one comma too much at the end here?
&layers=wasa_assert%3Atbl_water_supply_network,wasa_assert%3Atbl_tubewells,wasa_assert%3Atbl_ohr,wasa_assert%3Atbl_filtration_plant,wasa_assert%3Atbl_sewer_lines,wasa_assert%3Atbl_lift_station,wasa_assert%3Atbl_disposal_station,– Stefan
Jan 17 at 10:15
And as you can see in the syntax highlighting in your question, the string cannot be formed like this. Try this jsfiddle.net/newluck77/tz7xefas and if it solves your issue, let me post it as an answer, please. 😉
– Stefan
Jan 17 at 10:40
And as you can see in the syntax highlighting in your question, the string cannot be formed like this. Try this jsfiddle.net/newluck77/tz7xefas and if it solves your issue, let me post it as an answer, please. 😉
– Stefan
Jan 17 at 10:40
I tried it didn't solve the issue.
– DigitalPatwari
Jan 17 at 11:01
I tried it didn't solve the issue.
– DigitalPatwari
Jan 17 at 11:01
|
show 1 more comment
2 Answers
2
active
oldest
votes
3
The problem is in the url string.
It had two problems:
- Additional comma at the end of layers parameter as suggest by @Stefan in comments
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE, - Main problem was the missing query_layers parameter as it is a must required parameter for GetFeatureInfo as can be seen below
Additional details can be found here.
I'm pasting the final working url string below
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&query_layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
add a comment |
-1
Try this code below at once :
dataType: 'json',
edited Apr 12 at 9:20
J. Monticolo
1,958320
answered Apr 12 at 7:25
user140377user140377
1
5
Could you explain why?
– BERA
Apr 12 at 9:20
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f308937%2funcaught-syntaxerror-unexpected-token-geoserver-popup-in-leaflet-using-ajax%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
3
The problem is in the url string.
It had two problems:
- Additional comma at the end of layers parameter as suggest by @Stefan in comments
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE, - Main problem was the missing query_layers parameter as it is a must required parameter for GetFeatureInfo as can be seen below
Additional details can be found here.
I'm pasting the final working url string below
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&query_layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
add a comment |
3
The problem is in the url string.
It had two problems:
- Additional comma at the end of layers parameter as suggest by @Stefan in comments
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE, - Main problem was the missing query_layers parameter as it is a must required parameter for GetFeatureInfo as can be seen below
Additional details can be found here.
I'm pasting the final working url string below
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&query_layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
add a comment |
3
3
3
The problem is in the url string.
It had two problems:
- Additional comma at the end of layers parameter as suggest by @Stefan in comments
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE, - Main problem was the missing query_layers parameter as it is a must required parameter for GetFeatureInfo as can be seen below
Additional details can be found here.
I'm pasting the final working url string below
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&query_layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
The problem is in the url string.
It had two problems:
- Additional comma at the end of layers parameter as suggest by @Stefan in comments
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE, - Main problem was the missing query_layers parameter as it is a must required parameter for GetFeatureInfo as can be seen below
Additional details can be found here.
I'm pasting the final working url string below
URL='http://localhost:8888/geoserver/wasa_assert/wms?SERVICE=WMS
&version=1.1.0
&request=GetFeatureInfo
&layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&query_layers=workspace%3AlayerA,workspace%3AlayerB,workspace%3AlayerC,workspace%3AlayerD,workspace%3AlayerE,workspace%3AlayerF,workspace%3AlayerE
&styles=
&bbox=' + BBOX + '
&feature_count=1
&width=' + WIDTH + '
&height=' + HEIGHT + '
&format=image%2Fpng
&srs=EPSG%3A4326&
&x=' + X + '
&y=' + Y + '
&info_format=text/javascript';
$.ajax(
url: URL,
crossDomain: true,
dataType: "jsonp",
success: parseResponse
);
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
edited Jan 17 at 11:42
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
answered Jan 17 at 11:37
DigitalPatwariDigitalPatwari
398
398
add a comment |
add a comment |
-1
Try this code below at once :
dataType: 'json',
edited Apr 12 at 9:20
J. Monticolo
1,958320
answered Apr 12 at 7:25
user140377user140377
1
5
Could you explain why?
– BERA
Apr 12 at 9:20
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
add a comment |
-1
Try this code below at once :
dataType: 'json',
edited Apr 12 at 9:20
J. Monticolo
1,958320
answered Apr 12 at 7:25
user140377user140377
1
5
Could you explain why?
– BERA
Apr 12 at 9:20
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
add a comment |
-1
-1
-1
Try this code below at once :
dataType: 'json',
edited Apr 12 at 9:20
J. Monticolo
1,958320
answered Apr 12 at 7:25
user140377user140377
1
Try this code below at once :
dataType: 'json',
edited Apr 12 at 9:20
J. Monticolo
1,958320
answered Apr 12 at 7:25
user140377user140377
1
edited Apr 12 at 9:20
J. Monticolo
1,958320
edited Apr 12 at 9:20
J. Monticolo
1,958320
edited Apr 12 at 9:20
J. Monticolo
1,958320
1,958320
answered Apr 12 at 7:25
user140377user140377
1
answered Apr 12 at 7:25
user140377user140377
1
answered Apr 12 at 7:25
user140377user140377
1
1
5
Could you explain why?
– BERA
Apr 12 at 9:20
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
add a comment |
5
Could you explain why?
– BERA
Apr 12 at 9:20
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
5
5
Could you explain why?
– BERA
Apr 12 at 9:20
Could you explain why?
– BERA
Apr 12 at 9:20
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
This is like a link-only answer, but it doesn't even have a link. If you review some of the top-voted answers, you'll see what we're looking for here. Having only two half sentence lines, this answer is vulnerable to being deleted for being "low quality".
– Vince
Apr 12 at 12:53
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f308937%2funcaught-syntaxerror-unexpected-token-geoserver-popup-in-leaflet-using-ajax%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"Syntax error" means that you have a typo somewhere. In the console you can see, where the syntax error occurs. The file and line number are noted on the right side of the console. Click on it and the console will directly lead you to the file and line.
– Stefan
Jan 17 at 8:52
@Stefan This is exactly the issue, when I click on it, it takes me to
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://localhost:8888/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined" locator="layers"> Could not find layer wasa_assert: </ServiceException></ServiceExceptionReport>I have pasted the code snippet above and seemingly there seems to be no error in it.– DigitalPatwari
Jan 17 at 9:44
Could it be that there is one comma too much at the end here?
&layers=wasa_assert%3Atbl_water_supply_network,wasa_assert%3Atbl_tubewells,wasa_assert%3Atbl_ohr,wasa_assert%3Atbl_filtration_plant,wasa_assert%3Atbl_sewer_lines,wasa_assert%3Atbl_lift_station,wasa_assert%3Atbl_disposal_station,– Stefan
Jan 17 at 10:15
And as you can see in the syntax highlighting in your question, the string cannot be formed like this. Try this jsfiddle.net/newluck77/tz7xefas and if it solves your issue, let me post it as an answer, please. 😉
– Stefan
Jan 17 at 10:40
I tried it didn't solve the issue.
– DigitalPatwari
Jan 17 at 11:01