Re: [Geoserver-users] Geoserver create coverage via rest api

[Brad Hards]

On Wed, 18 Nov 2015 08:26:50 AM David Haynes II wrote: 
> > What is the data type you are trying to upload?
> > 
> > What user are you trying to upload as?
Please provide all the information requested. Its easier to help you if you 
help us...

Brad


--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] App-Schema and mapping / filtering of time series

[Stefano Costa]

Hi all,
I have a table containing point time observations for several parameters:

TIME PARAMETER_1  PARAMETER_2  PARAMETER_3
 TIME_SERIES_ID
2015-10-26 01:00:00+01   9.70 326  1.30 1
2015-10-26 02:00:00+01   8.90 348  0.90 1
2015-10-26 03:00:00+01   8.40 345  2.30 1
2015-10-26 04:00:00+01   8.00 192  0.50 1

I would like to map these values to a swe:DataArray element, nested in a
OM_Observation feature:




2015-10-26T01:00:00+01:00
2015-10-26T04:00:00+01:00




2015-10-26T04:00:00+01:00


...




4





http://www.opengis.net/def/property/OGC/0/SamplingTime;>
http://www.opengis.net/def/uom/ISO-8601/0/Gregorian; />




PARAMETER_1
http://codes.wmo.int/common/unit/Cel; />




PARAMETER_2
http://codes.wmo.int/common/unit/degree_(angle)" />




PARAMETER_3
http://codes.wmo.int/common/unit/m_s-1; />







2015-10-26T01:00:00+01:00,9.70,326,1.30@@
2015-10-26T02:00:00+01:00,8.90,348,0.90@@
2015-10-26T03:00:00+01:00,8.40,345,2.30@@
2015-10-26T04:00:00+01:00,8.00,192,0.50





To achieve this, I created a view in the database where I aggregate the
records by TIME_SERIES_ID, calculate min(TIME) and max(TIME), to be mapped
to beginPosition and endPosition/resultTime respectively, and text encode
the array values as shown above.

I have two questions:

1) Would it be possible to achieve the same result without creating a view?
I guess for the array values, I could concatenate fields using the
strConcat CQL function and blocks leveraging the isList mapping directive

(blocks would have to be separated by a blank space)... but how could I
calculate min and max values for the TIME column? To my knowledge, there is
no CQL equivalent to SQL's MIN() and MAX() aggregation functions, so I
would have to add two columns to the table (e.g., BEGIN_POS and END_POS),
pre-calculate the min and max time values for each time series and store
them there... which sounds worse than the view-based approach. Any better
ideas?

2) I would like to be able to filter the values that end up in the
DataArray via a WFS query, e.g. I would like to specify a time frame: is
this possible at all? I don't seem to be able to come up with a mapping
strategy / XPath filter to achieve this...


Any hint is highly appreciated.


-- 

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts!
Visithttp://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal 

Re: [Geoserver-users] GeoServer's spatial filter preventing SQL view layer from working

[Martin Davis]

+1 - agreed that this seems like the "simplest" way forward.



On Thu, Nov 19, 2015 at 10:08 AM, cheesybiscuits 
wrote:

> Wow, that is a long thread!
>
> I read / skimmed through the full conversation and what I take from it is
> there are numerous ways this could be done that would increase complexity,
> deviate from GeoServer's UI philosophy, and consume lots of developer time,
> but that Andrea's original suggestion - to not append an SDO_FILTER clause
> if a spatial index doesn't exist for the geometry column - is the most
> suitable. It can simply be the Oracle function / procedure writer's
> responsibility to ensure their code filters output features to the queried
> bbox.
>
> Ideally GeoServer would make minx, miny, maxx, and maxy of the query
> available by default (e.g. accessible in your SQL View via %%minx%%) so
> that
> these would not have to be provided by viewparams.
>
> There is a lot of documentation on starting GeoServer development but I
> have
> previously been confused about how to get involved in extension
> development.
> Any pointers for the best way to get started in this?
>
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/GeoServer-s-spatial-filter-preventing-SQL-view-layer-from-working-tp5237269p5237488.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
>
>
> --
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GeoServer's spatial filter preventing SQL view layer from working

[cheesybiscuits]

Wow, that is a long thread!

I read / skimmed through the full conversation and what I take from it is
there are numerous ways this could be done that would increase complexity,
deviate from GeoServer's UI philosophy, and consume lots of developer time,
but that Andrea's original suggestion - to not append an SDO_FILTER clause
if a spatial index doesn't exist for the geometry column - is the most
suitable. It can simply be the Oracle function / procedure writer's
responsibility to ensure their code filters output features to the queried
bbox.

Ideally GeoServer would make minx, miny, maxx, and maxy of the query
available by default (e.g. accessible in your SQL View via %%minx%%) so that
these would not have to be provided by viewparams.

There is a lot of documentation on starting GeoServer development but I have
previously been confused about how to get involved in extension development.
Any pointers for the best way to get started in this?




--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GeoServer-s-spatial-filter-preventing-SQL-view-layer-from-working-tp5237269p5237488.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Simple Polygon style

[Jair Santos]

Hello,

 

I've been trying to style a polygon to symbolize a reservoir. First I tried
a very simple polygon such as:

 





  #d63985



  

 

It worked but it is a tiny polygon which cannot be visualized with the map
starting zoom level.

 

So, I've tried an external graphic such as:

 





  



  



image/png

  

45



  





 

 

This time it doesn't show up at some zoom levels, and the initial size is
not acceptable as well.

 

Here are my questions:

 

1-   Is there a way to change the size of the polygon in the first
example?

2-   What's the proper way to define the external graphic so it will
have the proper size at all zoom levels?

Needless to say that I've tried several different configurations but none
works as required.

 

Thank you for any help.

 

JJ.

 

 

 

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GetFeature (WFS1.1.0) returns MultiCurve instead of MultiLineString

[Dominik Gärner]

Thanks for your responses, I raised a Jira ticket for it here: 
https://osgeo-org.atlassian.net/browse/GEOS-7320
GML 3.2 seems to be not affected, but I haven’t checked other requests. 
Possible that it concerns other requests/schemas also.

Best Regards
Dominik

Von: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Gesendet: Mittwoch, 18. November 2015 12:43
An: Rahkonen Jukka (MML)
Cc: geoserver-users@lists.sourceforge.net; Dominik Gärner
Betreff: Re: [Geoserver-users] GetFeature (WFS1.1.0) returns MultiCurve instead 
of MultiLineString

On Wed, Nov 18, 2015 at 11:07 AM, Rahkonen Jukka (MML) 
>
 wrote:
Hi,

I would read this 
http://docs.geoserver.org/stable/en/user/services/wfs/schemamapping.html
and then try something like


MultiSurface is what GML 3 most often uses and I suggest to file a feature 
request for your application about that. However, mismatch between 
DescribeFeatureType and GetFeature may be a bug in Geoserver 2.8 but I am not 
sure. MultiCurve with just linear members is the same as MultiLineString but I 
can’t say if client that is prepared to receive MultiLineStrings but is getting 
those enclosed inside MultiCurves has good enough reason for throwing an error.

MultLineString in WFS 1.1 schemas is deprecated and meant to be replaced with 
MultiCurve, but yeah, I've verified that the DescribeFeatureType does not
match on a 2.8.x I have handy (somewhat surprised the CITE tests we run nightly 
are not failing because of it)
Dominik, can you open a report at https://osgeo-org.atlassian.net/projects/GEOS 
?

Cheers
Andrea

--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne 
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di 
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro 
sistema. Conservare il messaggio stesso, divulgarlo anche in parte, 
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, 
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for the 
attention and use of the named addressee(s) and may be confidential or 
proprietary in nature or covered by the provisions of privacy act (Legislative 
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in 
accord with its purpose, any disclosure, reproduction, copying, distribution, 
or either dissemination, either whole or partial, is strictly forbidden except 
previous formal approval of the named addressee(s). If you are not the intended 
recipient, please contact immediately the sender by telephone, fax or e-mail 
and delete the information in this message that has been received in error. The 
sender does not give any warranty or accept liability as the content, accuracy 
or completeness of sent messages and accepts no responsibility  for changes 
made after they were sent or for other risks which arise as a result of e-mail 
transmission, viruses, etc.

---

--

Dominik Gärner
GRINTEC GmbH
Anzengrubergasse 6, 8010 Graz, Austria
Tel: +43(316)383706-0
mailto:dominik.gaer...@grintec.com
http://www.grintec.com

FN 47845k Handelsgericht Graz
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GeoServer's spatial filter preventing SQL view layer from working

[Martin Davis]

Actually after some more thought I think this situation is slightly
different (although the technical solution might end up being the same).
Here's the two cases as I understand them:

1) In my original case the need was to run a query against an Oracle
spatial table and return a geometry value computed from the base geometry.
So the SDO_FILTER clause for the query bounding box was still required, it
just needed to be run against the base geometry, not the geometry returned
by the query.

2) In the cluster case (if I understand it) no SDO_FILTER clause is
required, but instead the bounding box values need to be passed to a custom
Oracle function.

It seems like #1 might be simpler to implement than #2.  For instance, in
#1 GeoServer can still run an "empty query" to determine the geometry
column(s), whereas that doesn't seem feasible in #2.


On Wed, Nov 18, 2015 at 11:22 PM, Andrea Aime 
wrote:

> Hi Martin,
> it certainly looks similar, most likely same.
>
> No new development, still not possible, people still welcome to chip in
> with resources/funds:
>
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
> Cheers
> Andrea
>
> On Thu, Nov 19, 2015 at 6:32 AM, Martin Davis  wrote:
>
>> I think this is the same issue discussed in this (lengthy) thread:
>>
>>
>> http://osgeo-org.1560.x6.nabble.com/Reducing-query-data-size-in-Oracle-td5192620.html
>>
>> TLDR: not possible right now, apparently requires clever development to
>> make it work.
>>
>> If there has been improvement on this front it would be great to know
>> about it.  Or would be great to have someone implement a workaround!
>>
>> On Wed, Nov 18, 2015 at 12:08 PM, cheesybiscuits <
>> thomaschrist...@gmail.com> wrote:
>>
>>> I've created a function within Oracle for on-the-fly clustering that I
>>> hoped
>>> to query via GeoServer using an SQL view layer.
>>>
>>> The function takes as its arguments the bounding box and the number of
>>> grid
>>> cells to use in a basic gridded clustering process (i.e. find the centre
>>> of
>>> mass for points within each grid cell). Please note I've tried the Point
>>> Stacker extension and it isn't adequate for my needs. Executing the
>>> following query within Oracle gives the list of sdo_geometry objects
>>> that I
>>> expect:
>>>
>>> select * from table(package_name.function_name(-180, -90, 180, 90, 3);
>>>
>>> My intention is to make WMS requests to GeoServer with the viewparams
>>> parameter included that provides all required arguments. Because of the
>>> way
>>> the function works the returned sdo_geometry objects will only ever be
>>> within the provided bounding box.
>>>
>>> I can successfully create an SQL view layer within GeoServer using this
>>> syntax and everything seems OK while publishing. However when I access
>>> the
>>> layer everything falls apart. GeoServer takes my query and wraps it as
>>> follows:
>>>
>>> SELECT GEOMETRY as GEOMETRY FROM (select * from
>>> table(package_name.function_name(-180, -90, 180, 90, 3))) VTABLE WHERE
>>> SDO_FILTER(GEOMETRY, ?, 'mask=anyinteract querytype=WINDOW') = 'TRUE'
>>>
>>> Oracle then errors because the function's table return type doesn't have
>>> a
>>> spatial index to use with SDO_FILTER. Although I did find a  somewhat
>>> similar problem on GIS.SE
>>> <
>>> http://gis.stackexchange.com/questions/92554/can-i-create-an-oracle-spatial-view-from-a-non-spatial-table
>>> >
>>> the same solution does not apply as my function returns a table, not a
>>> single object, and Oracle doesn't permit indexes on named table types.
>>>
>>> As things currently stand I don't think I can make this work, and the
>>> only
>>> thing that could potentially help is to prevent GeoServer from appending
>>> its
>>> SDO_FILTER mask. However I'm guessing this just isn't possible without
>>> digging into the source and creating a custom build (totally not an
>>> option).
>>>
>>> Can anyone tell me if there's something I've missed here, or suggest a
>>> different approach for solving the same problem? Any thoughts would be
>>> very
>>> much appreciated.
>>>
>>>
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users