Re: [Geoserver-users] Creating a buffer of a transformed geometry leads to inconsistent geometry
Sorry, wrong mailing list. Moved to geotools users list.
Regards,
Robin
-Ursprüngliche Nachricht-
Von: Robin Pradel
Gesendet: Dienstag, 4. November 2014 16:52
An: geoserver-users@lists.sourceforge.net
Betreff: [Geoserver-users] Creating a buffer of a transformed geometry leads to
inconsistent geometry
Hi,
I try to create a buffer of a transformed input geometry. Already the result of
the transformation of the input geometry leads to a strange geometry that
contains the right coordinate but the wrong SRID. The reason seems to be the
GeometryFactory, which is (in my case) specialized to create geometries with a
special SRID. I thought this is the best way to create geometries (no need to
manually set SRID at the geometry) but now I am not sure about it.
What would be the right way to create a correct geometry (correct SRID and
GeometryFactory) as input?
The sample below shows my problem.
public class TransformationTest {
static {
System.setProperty(GeoTools.FORCE_LONGITUDE_FIRST_AXIS_ORDER,
Boolean.TRUE.toString());
}
@Test
public void transform() throws Exception {
int sourceSrid = 4326;
int targetSrid = 25832;
GeometryFactory gf = new GeometryFactory(new
PrecisionModel(PrecisionModel.FLOATING), sourceSrid);
Point sourceGeometry = gf.createPoint(new Coordinate(13, 52));
CoordinateReferenceSystem sourceCRS = CRS.decode(EPSG: + sourceSrid);
CoordinateReferenceSystem targetCRS = CRS.decode(EPSG: + targetSrid);
MathTransform transform = CRS.findMathTransform(sourceCRS, targetCRS);
Geometry targetGeometry = JTS.transform(sourceGeometry, transform);
assertEquals(targetGeometry SRID not as expected, targetSrid,
targetGeometry.getSRID()); // fail
// assertEquals(targetGeometry factory SRID not as expected,
targetSrid, targetGeometry.getFactory()
// .getSRID());
Geometry targetBuffer = targetGeometry.buffer(100);
assertEquals(Buffer SRID not as expected, targetSrid,
targetBuffer.getSRID()); // fail
}
}
Thanks in advance.
Yours sincerely.
M.Sc. Robin Pradel
Senior Systems Engineer
IVU Traffic Technologies AG
Bundesallee 88, D-12161 Berlin
http://www.ivu.de
--
___
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
[Geoserver-users] WFS GetFeature Post Request
Dear community,
I have a received a message from an engineers office on a faulty wfs
filter request to get features from our GeoServer (Version 2.4.4):
The Request was:
POST http://www.list.smwa.sachsen.de/baustelleninfo/wfs
http://www.list.smwa.sachsen.de/baustelleninfo/wfs ? HTTP/1.1
Content-Type: text/xml;charset=UTF-8
User-Agent: Iwan WebMapServer (info:http://www.webmapserver.de/)
IDUGeolib/6.2.0 Build 145
Connection: Keep-Alive
Content-Length: 889
Host: www.list.smwa.sachsen.de http://www.list.smwa.sachsen.de
Authorization: Basic U1BFUlJfU046IVNwM3IxNE4h
?xml version='1.0' encoding='UTF-8'?wfs:GetFeature version='1.1.0'
service='WFS'
xmlns:services='www.list.smwa.sachsen.de/baustelleninfo/services/'
xmlns='http://www.opengis.net/ogc'
xmlns:ogc='http://www.opengis.net/ogc'
xmlns:wfs='http://www.opengis.net/wfs'
xmlns:gml='http://www.opengis.net/gml'
wfs:Query typeName='services:Strassensperrungen_Aktuell'
wfs:PropertyNameservices:geom/wfs:PropertyName
Filter
And
BBOXogc:PropertyNameservices:geom/ogc:PropertyNamegml:Envelope
xmlns:gml='http://www.opengis.net/gml' srsName='EPSG:31468'
gml:lowerCorner5674610.89993951 4623372.64610281/gml:lowerCorner
gml:upperCorner5675455.82080778 4624530.12384099/gml:upperCorner
/gml:Envelope/BBOX
PropertyIsEqualTo
ogc:PropertyNameservices:Verwaltungskennziffer/ogc:PropertyName
Literal0014627/Literal
/PropertyIsEqualTo
/And
/Filter
/wfs:Query
/wfs:GetFeature
and the answer:
ows:ExceptionReport xmlns:ows=http://www.opengis.net/ows
http://www.opengis.net/ows
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
http://www.w3.org/2001/XMLSchema-instance version=1.0.0
xsi:schemaLocation=http://www.opengis.net/ows
http://www.list.smwa.sachsen.de:80/baustelleninfo/schemas/ows/1.0.0/owsE
xceptionReport.xsd
http://www.opengis.net/ows%20http:/www.list.smwa.sachsen.de:80/baustell
eninfo/schemas/ows/1.0.0/owsExceptionReport.xsd
ows:Exception exceptionCode=InvalidParameterValue
ows:ExceptionTextInvalid request
cvc-pattern-valid: Value 'services:Strassensperrungen_Aktuell' is not
facet-valid with respect to pattern '((\w:)?\w(=\w)?){1,}' for type
'TypeNameListType'.
cvc-attribute.3: The value 'services:Strassensperrungen_Aktuell' of
attribute 'typeName' on element 'wfs:Query' is not valid with respect to
its type,
'TypeNameListType'./ows:ExceptionTextows:ExceptionTextcvc-pattern-va
lid: Value 'services:Strassensperrungen_Aktuell' is not facet-valid with
respect to pattern '((\w:)?\w(=\w)?){1,}' for type
'TypeNameListType'./ows:ExceptionTextows:ExceptionTextcvc-attribute.
3: The value 'services:Strassensperrungen_Aktuell' of attribute
'typeName' on element 'wfs:Query' is not valid with respect to its type,
'TypeNameListType'./ows:ExceptionText/ows:Exception/ows:ExceptionRe
port
Does anyone know why this Post-request fails?
Thanks in advance!
Stephan
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WFS GetFeature Post Request
On Wed, Nov 5, 2014 at 10:26 AM, Klemm, Stephan - LIST stephan.kl...@list.smwa.sachsen.de wrote: Does anyone know why this Post-request fails? Because the underscore, _ , is not an allowed character in WFS 1.1 typenames Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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. --- -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WFS GetFeature Post Request
Hi, Where does the requirement not to accept underscore come from? I have been thinking that the WFS 1.1.0 schema presents QName leads to NCName with a possible prefix xsd:complexType name=FeatureTypeType xsd:annotation xsd:documentation An element of this type that describes a feature in an application namespace shall have an xml xmlns specifier, e.g. xmlns:bo=http://www.BlueOx.org/BlueOx;http://www.blueox.org/BlueOx%22; /xsd:documentation /xsd:annotation xsd:sequence xsd:element name=Name type=xsd:QName And NCName according to this document does allow underscores everywhere: http://www.datypic.com/sc/xsd/t-xsd_NCName.html -Jukka Rahkonen- Andrea Aime wrote: On Wed, Nov 5, 2014 at 10:26 AM, Klemm, Stephan - LIST stephan.kl...@list.smwa.sachsen.demailto:stephan.kl...@list.smwa.sachsen.de wrote: Does anyone know why this Post-request fails? Because the underscore, _ , is not an allowed character in WFS 1.1 typenames Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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.ithttp://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. --- -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WFS GetFeature Post Request
On Wed, Nov 5, 2014 at 1:30 PM, Rahkonen Jukka (Tike)
jukka.rahko...@mmmtike.fi wrote:
Hi,
Where does the requirement not to accept underscore come from? I have
been thinking that the WFS 1.1.0 schema presents QName leads to NCName with
a possible prefix
In the Query typeName is not defined as NCName, but as TypeNameListType:
xsd:attribute name=typeName type=wfs:TypeNameListType use=required
xsd:annotation
xsd:documentation
The typeName attribute is a list of one or more feature type names that
indicate which types of feature instances should be included in the reponse
set. Specifying more than one typename indicates that a join operation is
being performed. All the names in the typeName list must be valid types
that belong to this query's feature content as defined by the GML
Application Schema.
/xsd:documentation
/xsd:annotation
/xsd:attribute
...
xsd:simpleType name=TypeNameListType
xsd:restriction base=wfs:Base_TypeNameListType
xsd:pattern value=((\w:)?\w(=\w)?){1,}
xsd:annotation
xsd:documentation
Example typeName attribute value might be: typeName=ns1:Inwatera_1m=A,
ns2:CoastL_1M=B In this example, A is an alias for ns1:Inwatera_1m and B
is an alias for ns2:CoastL_1M.
/xsd:documentation
/xsd:annotation
/xsd:pattern
/xsd:restriction
/xsd:simpleType
The funny thing is that the documentation uses _, but then again the XML
validators do not accept it,
and the moment I removed it, the validation of the document passed.
So, I have to assume that \w does not include _ as a valid char.
According to some docs I've found on the internet \w is defined as:
Any character that might appear in a word. A shortcut for
'[#X-#x10]-[\p{P}\p{Z}\p{C}]' (all characters except the set of
punctuation, separator, and other characters).
I guess _ might be seen as a separator?
I've also tried to use ns1:Inwatera_1m=A, ns2:CoastL_1M=B in a
GetFeature, and I cannot find a way to fix it,
which is not surprising, since WFS 1.1 does not support joining to start
with...
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.
---
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] is Layer not getting from MongoDb in geoserver MongoDb store?
Hi, I found this thread while searching for a solution to the same problem. Were you able to proceed? if so, could you please share the details? Thanks -- View this message in context: http://osgeo-org.1560.x6.nabble.com/is-Layer-not-getting-from-MongoDb-in-geoserver-MongoDb-store-tp5135581p5171366.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
Re: [Geoserver-users] WFS GetFeature Post Request
Hi both,
thanks for your help!
Well, then the engineering office must take up the version 1.0.0! J Nope,
we'll just adjust the layer name and wait…
Best Regards
Stephan
Von: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] Im Auftrag von Andrea
Aime
Gesendet: Mittwoch, 5. November 2014 14:12
An: Rahkonen Jukka (Tike)
Cc: Klemm, Stephan - LIST; GeoServer Mailing List List
Betreff: Re: [Geoserver-users] WFS GetFeature Post Request
On Wed, Nov 5, 2014 at 1:30 PM, Rahkonen Jukka (Tike)
jukka.rahko...@mmmtike.fi wrote:
Hi,
Where does the requirement not to accept underscore come from? I have been
thinking that the WFS 1.1.0 schema presents QName leads to NCName with a
possible prefix
In the Query typeName is not defined as NCName, but as TypeNameListType:
xsd:attribute name=typeName type=wfs:TypeNameListType use=required
xsd:annotation
xsd:documentation
The typeName attribute is a list of one or more feature type names that
indicate which types of feature instances should be included in the reponse
set. Specifying more than one typename indicates that a join operation is being
performed. All the names in the typeName list must be valid types that belong
to this query's feature content as defined by the GML Application Schema.
/xsd:documentation
/xsd:annotation
/xsd:attribute
...
xsd:simpleType name=TypeNameListType
xsd:restriction base=wfs:Base_TypeNameListType
xsd:pattern value=((\w:)?\w(=\w)?){1,}
xsd:annotation
xsd:documentation
Example typeName attribute value might be: typeName=ns1:Inwatera_1m=A,
ns2:CoastL_1M=B In this example, A is an alias for ns1:Inwatera_1m and B is an
alias for ns2:CoastL_1M.
/xsd:documentation
/xsd:annotation
/xsd:pattern
/xsd:restriction
/xsd:simpleType
The funny thing is that the documentation uses _, but then again the XML
validators do not accept it,
and the moment I removed it, the validation of the document passed.
So, I have to assume that \w does not include _ as a valid char.
According to some docs I've found on the internet \w is defined as:
Any character that might appear in a word. A shortcut for
'[#X-#x10]-[\p{P}\p{Z}\p{C}]' (all characters except the set of
punctuation, separator, and other characters).
I guess _ might be seen as a separator?
I've also tried to use ns1:Inwatera_1m=A, ns2:CoastL_1M=B in a GetFeature,
and I cannot find a way to fix it,
which is not surprising, since WFS 1.1 does not support joining to start with...
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.
---
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] GeoServer username in SQL view
Hello List,
is there a way to get geoserver_user_name (something like ${GSUSER}) and to
use in SQL view where clause:
select gid, geom, username from line where username = ${GSUSER}
Maybe where is a secret trick?
Sincerely,
Paulius
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] GeoServer username in SQL view
On Wed, Nov 5, 2014 at 2:47 PM, Paulius Litvinas paul...@infoera.lt wrote:
Hello List,
is there a way to get geoserver_user_name (something like ${GSUSER}) and
to use in SQL view where clause:
select gid, geom, username from line where username = ${GSUSER}
Maybe where is a secret trick?
No, to my knowledge, there is no such support. It could be added with some
coding.
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.
---
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] GeoServer username in SQL view
Andrea,
Thanks for the info.
I found interesting behaviuor: column user in geoserver SQL view is changed to
current_user by geoserver and it returns username of postgis conection, instead
of user column value.
Should it act like this?
Whats why I thougth about the trick with GSUSER J
Pagarbiai,
Paulius Litvinas
GIS konsultantas
line
map
S. Žukausko g. 17,
LT-08234 Vilnius, Lietuva
telephone
Tel. + 370 5 278 8456
Mob. +370 656 10 089
mail_and_earth
mailto:paul...@infoera.lt paul...@infoera.lt
http://www.infoera.lt www.infoera.lt
info_era_autodesk
From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea
Aime
Sent: Wednesday, November 05, 2014 4:31 PM
To: Paulius Litvinas
Cc: GeoServer Mailing List List
Subject: Re: [Geoserver-users] GeoServer username in SQL view
On Wed, Nov 5, 2014 at 2:47 PM, Paulius Litvinas paul...@infoera.lt wrote:
Hello List,
is there a way to get geoserver_user_name (something like ${GSUSER}) and to use
in SQL view where clause:
select gid, geom, username from line where username = ${GSUSER}
Maybe where is a secret trick?
No, to my knowledge, there is no such support. It could be added with some
coding.
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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.
---
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] (no subject)
Hi,
I have some problems with Geoserver CQL filter that I can't solve now for a
week of reading and trying everything out.
Geoserver is 2.5.2 and I am trying to use BBOX CQL filter, but get a
strange result like this:
loadFeatures({type:FeatureCollection,totalFeatures:15640,features:[]})
It showing a total 15640 features in that bbox, but why there are no list
of them and features are just empty list?
This is my CQL filter:
http://loom-gis.geo.ut.ee:8080/geoserver/ermas/ows?service=WFSversion=1.1.0request=GetFeaturetypeName=ermas:testdata_geopntoutputFormat=text/javascriptformat_options=callback:loadFeaturesmaxFeatures=50srsname=EPSG:3301EPSG:3301CQL_FILTER=%28BBOX%28geometry,494981.10875,%206437855.3625,%20684824.858749,%206569105.3625%29%29
Any suggestions?
Thanks in advance.
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] (no subject)
Hi Olga,
Did you already checked the log ?
Are you observing the same behaviour with different output formats?
Cheers,
Stefano
---
41.95581N 12.52854E
http://www.linkedin.com/in/stefanoiacovella
http://twitter.com/#!/Iacovellas
2014-11-05 15:44 GMT+01:00 Olga Troškina olga.trosk...@gmail.com:
Hi,
I have some problems with Geoserver CQL filter that I can't solve now for
a week of reading and trying everything out.
Geoserver is 2.5.2 and I am trying to use BBOX CQL filter, but get a
strange result like this:
loadFeatures({type:FeatureCollection,totalFeatures:15640,features:[]})
It showing a total 15640 features in that bbox, but why there are no list
of them and features are just empty list?
This is my CQL filter:
http://loom-gis.geo.ut.ee:8080/geoserver/ermas/ows?service=WFSversion=1.1.0request=GetFeaturetypeName=ermas:testdata_geopntoutputFormat=text/javascriptformat_options=callback:loadFeaturesmaxFeatures=50srsname=EPSG:3301EPSG:3301CQL_FILTER=%28BBOX%28geometry,494981.10875,%206437855.3625,%20684824.858749,%206569105.3625%29%29
Any suggestions?
Thanks in advance.
--
___
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] (no subject)
Hi!
Just now I tried with different formats and I am now so confused. Havent
trried this before, but it works with other formats and with GeoJSOn also,
but my link does not.
http://loom-gis.geo.ut.ee:8080/geoserver/ermas/ows?service=WFSversion=1.0.0request=GetFeatureformat_options=callback:loadFeaturessrsname=EPSG:3301EPSG:3301typeName=ermas:testdata_geopntoutputFormat=text/javascriptmaxFeatures=50CQL_FILTER=%28BBOX%28geometry,494981.10875,%206437855.3625,%20684824.858749,%206569105.3625%29%29
http://loom-gis.geo.ut.ee:8080/geoserver/ermas/ows?service=WFSversion=1.1.0request=GetFeatureformat_options=callback:loadFeaturessrsname=EPSG:3301EPSG:3301typeName=ermas:testdata_geopntoutputFormat=text/javascriptmaxFeatures=30CQL_FILTER=%28BBOX%28geometry,494981.10875,%206437855.3625,%20684824.858749,%206569105.3625%29%29
And now I see that there are different WFS versions. So is this correct
that with 1.1.0 it doesn't work?
2014-11-05 17:16 GMT+02:00 Stefano Iacovella stefano.iacove...@gmail.com:
Hi Olga,
Did you already checked the log ?
Are you observing the same behaviour with different output formats?
Cheers,
Stefano
---
41.95581N 12.52854E
http://www.linkedin.com/in/stefanoiacovella
http://twitter.com/#!/Iacovellas
2014-11-05 15:44 GMT+01:00 Olga Troškina olga.trosk...@gmail.com:
Hi,
I have some problems with Geoserver CQL filter that I can't solve now for
a week of reading and trying everything out.
Geoserver is 2.5.2 and I am trying to use BBOX CQL filter, but get a
strange result like this:
loadFeatures({type:FeatureCollection,totalFeatures:15640,features:[]})
It showing a total 15640 features in that bbox, but why there are no list
of them and features are just empty list?
This is my CQL filter:
http://loom-gis.geo.ut.ee:8080/geoserver/ermas/ows?service=WFSversion=1.1.0request=GetFeaturetypeName=ermas:testdata_geopntoutputFormat=text/javascriptformat_options=callback:loadFeaturesmaxFeatures=50srsname=EPSG:3301EPSG:3301CQL_FILTER=%28BBOX%28geometry,494981.10875,%206437855.3625,%20684824.858749,%206569105.3625%29%29
Any suggestions?
Thanks in advance.
--
___
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
[Geoserver-users] Monitor: RemoteUser empty
I installed the Monitor extension of Gesoerver 2.5.x. and the log file send
RemoteUser empty.
I have secured layers.
My monitor.properties:
*# the storage mode, one of: memory, hibernate*
*# Note: hibernate mode requires the hibernate extension*
*storage=memory*
*# the monitor mode, one of: live, history*
*mode=history*
*# synchronization mode, one of: sync, async, async_update*
*#*
*# WARNING: this is an advanced configuration option. You probably do not
want*
*# to change this unless instructed to by a developer*
*sync=async*
*# The maximum allowable length for a request body (in bytes). Longer
bodies will be trimmed to *
*# this length.*
*maxBodySize=1024*
*# Disable logging of bodies entirely*
*# maxBodySize=0*
*# Allow unlimited body lengths. This could take up a lot of space quite
rapidly.*
*# maxBodySize=-1*
*# If you increase or unbound the maximum body length, you must also change
the hibernate mappings*
*# file. *
*# The CRS to log bounding boxes in*
*bboxLogCrs=EPSG:4326*
*# Bounding Box Log Level: controls when to record bounding boxes.*
*# 'none': Don't record bounding boxes*
*# 'no_wfs': Record bounding boxes for WMS and WCS requests, but not WFS.
This is the default*
*# 'full': Record a bounding box for all requests for which one can be
produced. WFS is not amenable*
*# to being logged this way so the boxes produced will be
approximate at best.*
*bboxLogLevel=no_wfs*
*audit.enabled=true*
*audit.path=/tmp*
*audit.roll_limit=1000*
My content.ftl:
*#escape x as x?xml*
*Request id=${id!}*
* Service${service!}/Service*
* Version${owsVersion!}/Version*
* Operation${operation!}/Operation*
* SubOperation${subOperation!}/SubOperation*
* Resources${resourcesList!}/Resources*
* Path${path!}/Path*
* QueryString${queryString!}/QueryString*
* #if bodyAsString??*
* Body*
* ${bodyAsString}*
* /Body*
* /#if*
* HttpMethod${httpMethod!}/HttpMethod*
* StartTime${startTime?datetime?iso_utc_ms}/StartTime*
* EndTime${endTime?datetime?iso_utc_ms}/EndTime*
* TotalTime${totalTime}/TotalTime*
* RemoteAddr${remoteAddr!}/RemoteAddr*
* RemoteHost${remoteHost!}/RemoteHost*
* Host${host}/Host*
* RemoteUser${remoteUser!}/RemoteUser*
* ResponseStatus${responseStatus!}/ResponseStatus*
* ResponseLength${responseLength?c}/ResponseLength*
* ResponseContentType${responseContentType!}/ResponseContentType*
* #if error??*
* Failedtrue/Failed*
* ErrorMessage${errorMessage!}/ErrorMessage*
* #else*
* Failedfalse/Failed*
* /#if*
*/Request*
*/#escape*
My log file:
*Request id=2,852*
* ServiceWFS/Service*
* Version1.1.0/Version*
* OperationGetFeature/Operation*
* SubOperation/SubOperation*
* Resourcestopp:states/Resources*
* Path/wfs/Path*
* QueryString/QueryString*
* Body*
* lt;wfs:GetFeature xmlns:wfs=quot;http://www.opengis.net/wfsquot
http://www.opengis.net/wfsquot; service=quot;WFSquot;
version=quot;1.1.0quot; maxFeatures=quot;20quot;
xmlns:xsi=quot;http://www.w3.org/2001/XMLSchema-instancequot
http://www.w3.org/2001/XMLSchema-instancequot;
xsi:schemaLocation=quot;http://www.opengis.net/wfs
http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/wfs.xsdquot;gt;lt;wfs:Query
http://schemas.opengis.net/wfs/1.1.0/wfs.xsdquot;gt;lt;wfs:Query
typeName=quot;feature:statesquot; srsName=quot;EPSG:102113quot;
xmlns:feature=quot;http://www.openplans.org/toppquot;gt;lt;ogc:Filter
http://www.openplans.org/toppquot;gt;lt;ogc:Filter
xmlns:ogc=quot;http://www.opengis.net/ogcquot;gt;lt;ogc:FeatureId
http://www.opengis.net/ogcquot;gt;lt;ogc:FeatureId
fid=quot;states.44quot;/gt;lt;/ogc:Filtergt;lt;/wfs:Querygt;lt;/wfs:GetFeaturegt;*
* /Body*
* HttpMethodPOST/HttpMethod*
* StartTime2014-11-06T03:34:49.785Z/StartTime*
* EndTime2014-11-06T03:34:49.805Z/EndTime*
* TotalTime20/TotalTime*
* RemoteAddr127.0.0.1/RemoteAddr*
* RemoteHostlocalhost/RemoteHost*
* Hostlocalhost/Host*
* RemoteUser/RemoteUser*
* ResponseStatus200/ResponseStatus*
* ResponseLength11900/ResponseLength*
* ResponseContentTypetext/xml; subtype=gml/3.1.1/ResponseContentType*
* Failedfalse/Failed*
*/Request*
The topp workspace is secured.
The client application is Geoexplorer and/or Layer Preview of Geoserver.
--
Servicios Computacionales y Asesoría en Sistemas de Información Geográfica
Francisco Javier Avalos Zapata
Ciudad Victoria, Tamaulipas
java...@asesoriaensig.com.mx
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Non-numeric elevations
OGC has published a BP for serving time/elevation dependent data (https://portal.opengeospatial.org/files/?artifact_id=56394) I am working on a project that is required to use GeoServer and also conform to this BP which, according to the document, operates within the confines of the WMS 1.3.0 spec. We have some custom coverage plugins to handle our coverage needs (and are looking at moving to gs-netcdf for some of our data), but one problem we are running into is the assumption throughout the GeoServer WMS and possibly the WCS that elevation values are always numeric. This makes it difficult for 'computed surface' elevations (i.e 'tropopause','surface') to even make it to a coverage plugin where it can be handled appropriately. The WMS 1.3.0 spec does not appear to explicitly limit the elevation dimension to numeric values, and the publication of the BP linked above further indicates that non-numeric values should be possible (see section 6.4.2 in the document linked above). So my question is: What is the position of the core GeoServer developers on non-numeric elevations and the best practice linked above (is this even on your radar?) Would there be interest in accepting patches/pull requests to allow non numeric elevations or are you guys directly opposed to this? Thanks in advance. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Non-numeric-elevations-tp5171521.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
Re: [Geoserver-users] Non-numeric elevations
On Thu, Nov 6, 2014 at 5:01 AM, clifford.harms clifford.ha...@gmail.com wrote: So my question is: What is the position of the core GeoServer developers on non-numeric elevations and the best practice linked above (is this even on your radar?) Would there be interest in accepting patches/pull requests to allow non numeric elevations or are you guys directly opposed to this? Willing to accept for sure I believe? The current design is done as is because we haven't seen examples of non numeric elevations yet, or have not needed them. See the contribution guidelines about what we need in order to accept a pull request: https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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. --- -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
