Dear Dennis and Adam,
I followed these instructions to the letter, all very nice, thank you! I
did everything, there were no protests from geoserver, nor when I added the
layers etc. The map layer turned up in Arches, I could modify it as I
liked, but... The map does not actually turn up. What do I do wrong?
My geotiff is in EPSG:3857 and I did the following:
1. Uploaded the tiff to the geoserver directory.
2. Added the tiff through Add stores/GeoTiff
3. Went to /admin/ and added the tiff through "Map sources"
{"type": "raster", "tiles":
["https://pragmata2.sia.uu.se/geoserver/Pragmata/wms?bbox={bbox-epsg-3857}&format=image/png&service=WMS&version=1.1.1&request=GetMap&srs=EPSG:3857&width=256&height=256&layers=Pragmata:kalaureia-plan";],
"tileSize": 256}
Saved etc.
4. Added it as a map layer
[{"id": "kalaureia-plan", "type": "raster", "source": "kalaureia-plan"}]
5. Went to Arches and it is there among the overlays, and I activated it.
Still no show.
Hope you can help me!
Robin
Den onsdag 1 april 2020 kl. 01:41:06 UTC+3 skrev Dennis Wuthrich:
>
> Adam,
>
> Thanks for providing a summary of using Geoserver to serve Geotiffs,
> particularly the details of creating a layer group, supporting
> transparency, and the extra explanation of how to structure the URL
> properly. Very nice! I also really like the django fixture; it's a nice
> way to avoid the button clicks that my approach summarized.
>
> I very much appreciate the time you took to write this up and share it
> with the community!
>
> Cheers,
>
> Dennis
>
> On Tuesday, March 31, 2020 at 2:25:29 PM UTC-7, Adam Cox wrote:
>>
>> Hi Dennis, thanks for this detailed guide. I was just able to add a layer
>> from my existing Geoserver installation and it worked fine.
>>
>> One detail I wanted to mention: 3.2 - Instead of the "Geoserver store" in
>> the url, it's actually the name of the *workspace*.
>>
>> So I thought I would write up my working example in case it's helpful for
>> others. My geoserver instance is https://db.legiongis.com/geoserver. In
>> Dennis' example, he has it running locally on the default tomcat port:
>> http://localhost:8080/geoserver.
>>
>> My layer in Geoserver looks like this:
>>
>> Note the name of the workspace is *fpan *and the id of the layer
>> itself is *1919-coastal-map*, hence *fpan:**1919-coastal-map*. The layer
>> name "1919 Coastal Map" is not used at all in this process. (This is a
>> "group layer" in Geoserver, combining multiple map sheets, each one being
>> its own geotiff.)
>>
>> In Arches, my new Map Source looks like this:
>>
>> For copy/paste purposes:
>> {
>> "type": "raster",
>> "tiles": ["
>> https://db.legiongis.com/geoserver/fpan/wms?bbox={bbox-epsg-3857}&format=image/png&service=WMS&version=1.1.1&request=GetMap&srs=EPSG:3857&width=256&height=256&layers=fpan:1919-coastal-map&transparent=true
>> "],
>> "tileSize": 256
>> }
>>
>> I gave the Map Source a new name, and in the source configuration I did
>> the following: 1. swapped out my Geoserver location in the beginning of the
>> url 2. immediately following that, changed the workspace name and 3.
>> changed the layers= value to *fpan:1919-coastal-map *(<workspace>:<layer
>> name>), just as the layer is shown in Geoserver above. Finally, because my
>> layer (as with many historic map scans) has a transparent border, I added
>> transparent=true to the end of the url as well. Without that directive,
>> Geoserver served the transparent pixels in my raster as white instead of
>> transparent.
>>
>> My new Map Layer Looks like this:
>>
>>
>> I've set the name to something nice and readable; this is what will show
>> in the Arches map interface. In the layer definition, I set both *id *and
>> *source *to match the name of my Map Source defined above. Setting the
>> *source
>> *like this is *imperative*--it's what connects the Map Layer to the Map
>> Source. Setting the *id* with the same value is a *best practice*: layer
>> definition ids must be unique across all map layers and are used elsewhere
>> in the app.
>>
>> Finally, I didn't want an icon, so I just put in "noicon". This field
>> must be filled, but if its value is not "fa fa-<icon name>" matching the
>> Font
>> Awesome icon set <https://fontawesome.bootstrapcheatsheets.com/>, then
>> no icon will appear.
>>
>> Once the Map Source and Map Layer have been saved, the layer shows up
>> perfectly well in Arches.
>>
>>
>> Hope that helps anyone else working on this. I have also created a django
>> fixture <https://docs.djangoproject.com/en/2.2/howto/initial-data/>
>> which I will attach to this post that you can load if you want to create
>> the Map Source and Map Layer shown above. You can load fixtures (which are
>> json representations of an ORM object) with the following command. Please
>> note this is a Django database format and a core django management command,
>> i.e. not part of Arches proper:
>>
>> python manage.py loaddata 1919-coastal-map.json
>>
>> Adam
>>
>> On Sunday, March 29, 2020 at 11:24:15 AM UTC-5, Leonidas wrote:
>>>
>>> I need to add a geotiff Overlay as Tileserver Layer using (instructions
>>> for v4 <https://github.com/legiongis/arches4-geo-examples>):
>>>
>>> python manage.py packages -o add_tileserver_layer -m "hillshade.xml" -n
>>> "hillshade"
>>>
>>> but *add_tileserver_layer *is not an available option anymore (manage.py
>>> packages: error: argument -o/--operation: invalid choice:
>>> 'add_tileserver_layer')
>>>
>>> Is there any equivalent option for Arches v5?
>>> Is there an updated Documentation for version 5?
>>>
>>
--
-- To post, send email to [email protected]. To unsubscribe, send
email to [email protected]. For more information,
visit https://groups.google.com/d/forum/archesproject?hl=en
---
You received this message because you are subscribed to the Google Groups
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/archesproject/1da3180f-ca59-40d0-aa7d-22d192ef0286%40googlegroups.com.
