Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error

[nkirlew]

Hello Folks,

Apologies if this is the wrong location to requests assistance.

We are running Omeka 1.5 with Neatline 1.0.1 and Neatline Maps 1.0.0
Huge learning curve but we have a AWS Ubuntu build geoserver running

I have loaded a geotiff via neatline but have not been able to get a map to show.
I noticed the error below when I loaded the following parameters to the wms fields:
http://geo.ripia.net:8080/geoserver/neatline/wms
neatline:DarwinHarbour

Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error : Opening and ending tag mismatch: HR line 1 and body in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): able.

Apache Tomcat/6.0.35
in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): ^ in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error : Opening and ending tag mismatch: HR line 1 and html in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): u>

Apache Tomcat/6.0.35
in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): ^ in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error : Premature end of data in tag body line 1 in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): u>

Apache Tomcat/6.0.35
in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): ^ in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error : Premature end of data in tag html line 1 in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): u>

Apache Tomcat/6.0.35
in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168 Warning: SimpleXMLElement::__construct(): ^ in /var/www/html/omeka-1.5/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 168

Thanks
Nick
Northern Territory Library

[davidmcclure]

Hm, that looks like either (a) NL Maps is having trouble reading the XML that's coming out of Geoserver or (b) Geoserver is spitting out malformed XML.

What version of Geoserver are you running? (Appears that the link you pasted in is down.)

[nkirlew]

Hello David,
OK, We are using Version 2.2-SNAPSHOT.
I see the Geoserver is falling over every so often So I will reviist that and come back to you when it is stable.
Thanks
Nick
Northern Territory Library

[nkirlew]

Hello David,
Ok, I have rebuilt the Geoserver
http://geo.ripia.net:8080/GeoServer

and I have a WMS layer neatline:neatline_tutorial

If I view the layer in Qantum GIS overlaying usa:states I reckon I am close

Still the same error from the Omeka

I will build a clean Omeka from scratch and see how that goes as there seems to be some inconsistencies, for example under the coverage field I can't get the option to locate on a map.

I'll leave the error server up, if you would like admin rights please email me nicholas.kirlew"at"nt.gov.au

http://ec2-175-41-170-53.ap-southeast-1.compute.amazonaws.com/neatline-exhibits/show/dh

Thanks
Nick
Northern Territory Library

[davidmcclure]

Hey Nick,

Ok, seems like Geoserver's fine - I just spun up a fresh install of Omeka 1.5.3, NL 1.1.0, and NL Maps 1.0 and was able to enter you server/layer into NL Maps and load the map in a NL exhibit.

But I also can't see the map, although I'm not getting that error. At what step of the process to you get the error? Is it after you save the item form, or when you try to hit one of the item show pages?

I have a hunch that NL Maps isn't playing well with the new version of GeoServer. Will investigate.

[nkirlew]

Hello David,
Great, thanks for this. It is on the save item, whether it is new or if you change something on the WMS fields.

I am halfway to a clean Omeka, NL and NL maps build.

Regards,
Nicholas Kirlew
Manager Library Technology
Northern Territory Library 'Celebrating 30 Years'
Dept of Natural Resources, Environment, The Arts and Sport
Ph: +61 (08) 8922 0843
[email protected]

If you are not the intended recipient, any use, disclosure or copying of this message or any attachments is unauthorised. If you have received this document in error, please advise the sender.

---

From: davidmcclure [[email protected]]
Sent: Monday, 22 October 2012 10:14 PM
To: scholarslab/NeatlineMaps
Cc: Nicholas Kirlew
Subject: Re: [NeatlineMaps] Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error (#55)

Hey Nick,

Ok, seems like Geoserver's fine - I just spun up a fresh install of Omeka 1.5.3, NL 1.1.0, and NL Maps 1.0 and was able to enter you server/layer into NL Maps and load the map in a NL exhibit.

But I also can't see the map, although I'm not getting that error. At what step of the process to you get the error? Is it after you save the item form, or when you try to hit one of the item show pages?

I have a hunch that NL Maps isn't playing well with the new version of GeoServer. Will investigate.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/55#issuecomment-9662201.

[nkirlew]

Hello David,
I have two new servers and software installed.
I now only get this error when I update the WMS, I note also that the Neatline-Maps plugin considers the geoserver to be offline:
Fatal error: Call to a member function attributes() on a non-object in /var/www/html/omeka-1.5.3/plugins/NeatlineMaps/lib/GeoserverMap_WMS.php on line 172
Regards,
Nicholas Kirlew
Manager Library Technology
Northern Territory Library 'Celebrating 30 Years'
Dept of Natural Resources, Environment, The Arts and Sport
Ph: +61 (08) 8922 0843
[email protected]

If you are not the intended recipient, any use, disclosure or copying of this message or any attachments is unauthorised. If you have received this document in error, please advise the sender.

---

From: davidmcclure [[email protected]]
Sent: Monday, 22 October 2012 10:14 PM
To: scholarslab/NeatlineMaps
Cc: Nicholas Kirlew
Subject: Re: [NeatlineMaps] Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error (#55)

Hey Nick,

Ok, seems like Geoserver's fine - I just spun up a fresh install of Omeka 1.5.3, NL 1.1.0, and NL Maps 1.0 and was able to enter you server/layer into NL Maps and load the map in a NL exhibit.

But I also can't see the map, although I'm not getting that error. At what step of the process to you get the error? Is it after you save the item form, or when you try to hit one of the item show pages?

I have a hunch that NL Maps isn't playing well with the new version of GeoServer. Will investigate.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/55#issuecomment-9662201.

[nkirlew]

PS, to me it looks like the map layer is overlaying the whole world, a reddish film gets loaded and you can see the geoserver name flashing in the botton left corner. i hope you are safe from the weather.

[davidmcclure]

Hi Nicholas,

Ok, I looked in to this, and I see two things that could be going on. At first, I thought that there could be some kind of difference in how GeoServer is forming the getCapabilities request in 2.2.1 (we originally developed against 2.2), but that turns out not to be the case. Instead, I see two possible problems:

1. First, the WMS/layer combination you originally posted (http://geo.ripia.net:8080/geoserver/neatline/wms | neatline:DarwinHarbour) won't work because you're basically duplicating the "neatline" part of the request in the two parts. By using the neatline-workspace-specific WMS address, as opposed to the top-level address (in your case, http://geo.ripia.net:8080/geoserver/wms), GeoServer is spitting out XML that does not include the workspace slug on the layer names - in your case, the layer would just be called DarwinHarbour, not neatline:DarwinHarbour. In other words, one of these two combinations should work:

   http://geo.ripia.net:8080/geoserver/neatline/wms
   DarwinHarbour

   http://geo.ripia.net:8080/geoserver/wms
   neatline:DarwinHarbour

   But not:

   http://geo.ripia.net:8080/geoserver/neatline/wms
   neatline:DarwinHarbour

   This is a confusing distinction that the code should handle. For the upcoming release of this plugin, I'm going to write a little GUI interface that makes it possible to enter in a WMS address and then select from an AJAX-ed list of layers.

2. The above change is necessary for things to work, but seems like the layer you're talking about it just totally absent. When I hit getCapabilities on your server (http://geo.ripia.net:8080/geoserver/wms?request=getCapabilities), I don't find any listing for DarwinHarbour. Are you sure the store/layer exists and is configured properly?

If you send me the original .tif file you're working with, I'll be happy to try to get it working locally and see if I can find the problem.

All best,
David

[nkirlew]

Hello David,
Ok, thanks for your update.
When I rebuilt the geoserver the new layer is neatline:neatline_tutorial

I threw the Darwin Harbour stuff away and worked with the example from your tutorial.

https://s3.amazonaws.com/ntl-nck/neatline_tutorial.tif is the tif I am using, to big to email.

Regards,
Nicholas Kirlew
Manager Library Technology
Northern Territory Library 'Celebrating 30 Years'
Dept of Natural Resources, Environment, The Arts and Sport
Ph: +61 (08) 8922 0843
[email protected]

If you are not the intended recipient, any use, disclosure or copying of this message or any attachments is unauthorised. If you have received this document in error, please advise the sender.

---

From: davidmcclure [[email protected]]
Sent: Sunday, 4 November 2012 6:32 AM
To: scholarslab/NeatlineMaps
Cc: Nicholas Kirlew
Subject: Re: [NeatlineMaps] Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error (#55)

Hi Nicholas,

Ok, I looked in to this, and I see two things that could be going on. At first, I thought that there could be some kind of difference in how GeoServer is forming the getCapabilities request in 2.2.1 (we originally developed against 2.2), but that turns out not to be the case. Instead, I see two possible problems:

1. First, the WMS/layer combination you originally posted (http://geo.ripia.net:8080/geoserver/neatline/wms | neatline:DarwinHarbour) won't work because you're basically duplicating the "neatline" part of the request in the two parts. By using the neatline-workspace-specific WMS address, as opposed to the top-level address (in your case, http://geo.ripia.net:8080/geoserver/wms), GeoServer is spitting out XML that does not include the workspace slug on the layer names - in your case, the layer would just be called DarwinHarbour, not neatline:DarwinHarbour. In other words, one of these two combinations should work:

http://geo.ripia.net:8080/geoserver/neatline/wms
DarwinHarbour

http://geo.ripia.net:8080/geoserver/wms
neatline:DarwinHarbour

But not:
http://geo.ripia.net:8080/geoserver/neatline/wms
neatline:DarwinHarbour

This is a confusing distinction that the code should handle. For the upcoming release of this plugin, I'm going to write a little GUI interface that makes it possible to enter in a WMS address and then select from an AJAX-ed list of layers.

1. The above change is necessary for things to work, but seems like the layer you're talking about it just totally absent. When I hit getCapabilities on your server (http://geo.ripia.net:8080/geoserver/wms?request=getCapabilities), I don't find any listing for DarwinHarbour. Are you sure the store/layer exists and is configured properly?

If you send me the original .tif file you're working with, I'll be happy to try to get it working locally and see if I can find the problem.

All best,
David

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/55#issuecomment-10044185.

[nkirlew]

Hello David,
Monday morning, I have reread your comment and the software is working as designed, thanks!

I had the syntax wrong as you had noted.

Regards,
Nicholas Kirlew

From: davidmcclure [mailto:[email protected]]
Sent: Sunday, 4 November 2012 6:33 AM
To: scholarslab/NeatlineMaps
Cc: Nicholas Kirlew
Subject: Re: [NeatlineMaps] Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error (#55)

Hi Nicholas,

Ok, I looked in to this, and I see two things that could be going on. At first, I thought that there could be some kind of difference in how GeoServer is forming the getCapabilities request in 2.2.1 (we originally developed against 2.2), but that turns out not to be the case. Instead, I see two possible problems:

1. First, the WMS/layer combination you originally posted (http://geo.ripia.net:8080/geoserver/neatline/wms | neatline:DarwinHarbour) won't work because you're basically duplicating the "neatline" part of the request in the two parts. By using the neatline-workspace-specific WMS address, as opposed to the top-level address (in your case, http://geo.ripia.net:8080/geoserver/wms), GeoServer is spitting out XML that does not include the workspace slug on the layer names - in your case, the layer would just be called DarwinHarbour, not neatline:DarwinHarbour. In other words, one of these two combinations should work:

http://geo.ripia.net:8080/geoserver/neatline/wms
DarwinHarbour

http://geo.ripia.net:8080/geoserver/wms
neatline:DarwinHarbour

But not:
http://geo.ripia.net:8080/geoserver/neatline/wms
neatline:DarwinHarbour

This is a confusing distinction that the code should handle. For the upcoming release of this plugin, I'm going to write a little GUI interface that makes it possible to enter in a WMS address and then select from an AJAX-ed list of layers.

1. The above change is necessary for things to work, but seems like the layer you're talking about it just totally absent. When I hit getCapabilities on your server (http://geo.ripia.net:8080/geoserver/wms?request=getCapabilities), I don't find any listing for DarwinHarbour. Are you sure the store/layer exists and is configured properly?

If you send me the original .tif file you're working with, I'll be happy to try to get it working locally and see if I can find the problem.

All best,
David

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/55#issuecomment-10044185.