Dear All,
For quite sometimes now, I have been trying to figure out how to get
pictures to display in Geoserver but still not working. I got someone to
help me configure the IP address but still does not work.
The question I have is how do I create the qualified url that I should call
in the content ftl as suggested by Mark?
After creating the working url, does the individual pictures in the
attribute table also needs to be qualified url? how do I create this?
because I would like each point to have its picture showing together with
the attribute information.
My pictures are stored in normal folders and I created paths in the
attribute table. I did a QGIS to web app and I manage to get the pictures
to show without so much struggle only a few configuration but I now I also
need it it to work on the other application using Geoserver.
Thank you so much for the hints/recommendation.
Regards
Amelia
On Sun, Apr 22, 2018 at 1:20 PM, Mark Prins <mc.pr...@gmail.com> wrote:
>
>
> 2018-04-21 16:31 GMT+02:00 Nauwanga Nauwanga <amellynicode...@gmail.com>:
>
>>
>> <img src=" picturepath.value \ ${feature.NAME.value} .jpg">
>>
>> </li>
>> </#list>
>>
>>
>> The tutorial suggested that I should refer to my Internet visible
>> server address instead of localhost, or its IP if I have fixed IPs, I do
>> not understand this very very well,
>>
>>
> the img src should end up to be a fully qualified url to the image in the
> featureinfo response so the browser knows where to get it; it cannot be a
> file path. It can be localhost, but the the url will only resolve if the
> webbrowser and the webserver hosting the image are on the same machine, it
> can be a relative link to the geoserver url if you are hosting the image on
> the same webserver as geoserver, I'm assuming you aren't.
>
> Mark
>
> --
> Disclaimer;
> This message is just a reflection of what I thought at the time of
> sending. The message may contain information that is not intended for you
> or that you don't understand.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-req
> uesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
