Re: [mapserver-users] TinyOWS: Axis order fix wanted
On Sat, Jun 28, 2014 at 11:38 PM, Even Rouault even.roua...@mines-paris.org wrote: The following pull request should fix Jukka's issue : https://github.com/mapserver/tinyows/pull/65 I've just commited the pull request. Thanks for this one Even, Jukka could you check on your own that everything is fine for you ? -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS: Axis order fix wanted
Jukka, Even, I've not looked at TinyOWS code recently, but I guess that reusing the database of EPSG codes used by MapServer to determine where axis swapping is necessary should be doable. If i remember well it's more than that. As axis swapping is already handled. I may be able to help with making it to happen. Do you mean funding ? I think I've commit rights in TinyOWS since it is hosted at https://github.com/mapserver/ and I've commit rights in mapserver repositories, but I should perhaps check with Olivier Courtin/Oslandia if they're OK with me touching the code. As long as we communicate before commits, you're very welcome Even ! Potentially they could also be interested in funded work too. We could indeed, I send you an email Jukka. O. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Status of TinyOWS and support for paging
On Sat, Feb 1, 2014 at 1:34 PM, Rahkonen Jukka (Tike) jukka.rahko...@mmmtike.fi wrote: Hi Jukka, Last commit to TinyOWS was over one year ago. Does it mean that the status of the project is DONE or DEAD?. Not at all :) It just means that no other contributors send patches that no organization were ready to fund new feature last months and so i guess that somehow every one else are happy with current features, and also that i had other projects to care about last months. Adding support for WFS paging is in the issue list list https://github.com/mapserver/tinyows/issues/45 That feature would be really nice to have as vendor parameter in WFS 1.0.0 and 1.1.0. Because the only supported backend is PostGIS this does not feel like extra hard work even probably just adding LIMIT 'maxFeatures' OFFSET 'startIndex-1' won't be enough because requests should also be made to pass the schema validation. Yeap you're right it will be something to put on the top of the list. Because it will be helpfull and don't need a lot of time to implement. Cheers, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] xslt transfofmr on getcapabilites of tinyows
Hi Andrea, First i could not reproduce your problem with TinyOWS. I use trunk version (so really close to 1.1.0). Could you provide tinyows -h output ? Could you provide tinyows config file ? Second, i could not reproduce your problem with XPath either ^^ as following works for me: xsltproc foo.xsl capa.xml With foo.xsl: ?xml version=1.0? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:template xsl:value-of select=//FeatureTypeList/FeatureType[1]/Name / /xsl:template /xsl:stylesheet HTH, O. On Tue, Jul 16, 2013 at 11:53 PM, Andrea Peri aperi2...@gmail.com wrote: I open a ticket for this issue on keyword. https://github.com/mapserver/tinyows/issues/61 Regards. 2013/7/16 Andrea Peri aperi2...@gmail.com Hi, I test it with a validate tool, Effectively there was an error. Element Keywords is not allowed under element FeatureType. So I remove the keywords definition from my tiny config.xml, After this the xml was valid, but always the xsl:value-of select=//FeatureTypeList/FeatureType/Name / don't return the right value. 2013/7/16 Olivier Courtin olivier.cour...@gmail.com If you have a doubt on a XML provided by a WFS server, there's OGC XSD you could use to validate against. (look in tinyows/schema dir) O. On Tue, Jul 16, 2013 at 5:39 PM, Andrea Peri aperi2...@gmail.com wrote: Hi, I'm try.ing to trasform an xml from tinyows. But it seem don't work. Perhaps there a problem with the xml of tiny ? On this call: http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?SERVICE=WFSREQUEST=GetCapabilitiesversion=1.1.0 I'm trying to apply this trasformation: xsl:value-of select=//FeatureTypeList/FeatureType[1]/Name / to retrieve the name of first FeatureType. But the xsltproc always return null. I'm not sure of my xpath, but it seem ok, Any help is welcome. -- - Andrea Peri . . . . . . . . . qwerty àèìòù - ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users -- Olivier -- - Andrea Peri . . . . . . . . . qwerty àèìòù - -- - Andrea Peri . . . . . . . . . qwerty àèìòù - -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] xslt transfofmr on getcapabilites of tinyows
If you have a doubt on a XML provided by a WFS server, there's OGC XSD you could use to validate against. (look in tinyows/schema dir) O. On Tue, Jul 16, 2013 at 5:39 PM, Andrea Peri aperi2...@gmail.com wrote: Hi, I'm try.ing to trasform an xml from tinyows. But it seem don't work. Perhaps there a problem with the xml of tiny ? On this call: http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?SERVICE=WFSREQUEST=GetCapabilitiesversion=1.1.0 I'm trying to apply this trasformation: xsl:value-of select=//FeatureTypeList/FeatureType[1]/Name / to retrieve the name of first FeatureType. But the xsltproc always return null. I'm not sure of my xpath, but it seem ok, Any help is welcome. -- - Andrea Peri . . . . . . . . . qwerty àèìòù - ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] MapServer Support for WFS 2.0.0
2013/3/11 Astrid Emde astrid.e...@wheregroup.com Hi Astrid, are there any plans to implement WFS 2.0.0 in MapServer TinyOWS and if yes is there a timeline? WFS 2.0.0 and especially the INSPIRE Download service part, are clearly identified as a need for future. Right now, Oslandia is ready to participate to sponsor this feature. But not ready to sponsor it alone. We already launched some discussions with some French agencies. The aim is to gather 3/5 organisations able to fund it together. So right now it's a bit early to talk about timeline. Help/contact/partial funding on this subjet is so very welcome. Regards, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order trouble
On Mon, Dec 17, 2012 at 11:16 AM, Rahkonen Jukka jukka.rahko...@mmmtike.fiwrote: Hi Jukka, Nice to see you again here :) I have been running TinyOWS r558 for quite a long time because it is dealing almost right with the axis order of the projections I am commonly using. Now I had a fast try with the current TinyOWS 1.1.0 version but unfortunately I realized that it is doing wrong thing by flipping the axis with urn:ogc:def:crs:EPSG::3067. On this topic we will not make any progress, without a regression test. (OGC CITE don't cover this issue) Could you provide from a single point stored in the database, requests and answers awaited ? I could also try to write it by myself too, but will definitly need you to read it back, for all eastern stuff... What is the logic that TinyOWS is using when it decides whether the axis should be flipped or not for WFS 1.1.0? Mainly 2 factors, as i recall: - if it's SRS or CRS (meaning EPSG: or urn:ogc:def:crs:EPSG::) - if SRTEXT contain both AXIS[X,NORTH]] and AXIS[Easting,EAST]] -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Propertyname list does not work with Json
On Mon, Dec 17, 2012 at 3:34 PM, Rahkonen Jukka jukka.rahko...@mmmtike.fiwrote: Jukka, Tested with TinyOWS 1.1.0 on Linux Ubuntu, PostgreSQL 9.0 and PostGIS 1.5. I fixed a GeoJSON issue, just after 1.1.0 release, could you give a try with current trunk to be sure, it's not already fixed ? Thanks ! -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Problem with ANGLE FOLLOW
Hi, For same kind of need (i.e hydrologic line to label), i've found that: - Your lines must be long enough to allow the label to fit on (seems already your case, as it works for you without ANGLE FOLLOW) - You have to increase MAXOVERLAPANGLE property - Your lines have to be as smooth as possible Below a sample of such a thing with two layers, one with the data itself and one another using a generalization trought PostGIS ST_Simplify to help the geometry to be smoother enough LAYER NAME label METADATA ows_title Label des cours d'eau Carthage AERMC ows_extent 573401 6050407 1242369 6811885 ows_featureid gid END PROJECTION init=epsg:2154 END TYPE line STATUS on DATA geom from (SELECT gid, ST_simplify(geom, 200) As geom , toponyme, classe::integer FROM aermc.cours_eau WHERE toponyme IS NOT NULL) AS foo using unique gid using srid=2154 CONNECTIONTYPE postgis CONNECTION host= port=5432 dbname= user= LABELITEM toponyme CLASSITEM classe CLASS EXPRESSION ([classe] = 2) LABEL COLOR 0 0 0 OUTLINECOLOR 210 210 210 TYPE TRUETYPE FONT vera SIZE 10 ANTIALIAS TRUE POSITION UC ANGLE FOLLOW PARTIALS FALSE MINFEATURESIZE auto REPEATDISTANCE 500 MAXOVERLAPANGLE 45 END END CLASS EXPRESSION ([classe] = 4) LABEL COLOR 30 30 30 OUTLINECOLOR 210 210 210 TYPE TRUETYPE FONT vera SIZE 8 ANTIALIAS TRUE POSITION UC ANGLE FOLLOW PARTIALS FALSE MINFEATURESIZE auto MAXOVERLAPANGLE 40 END END CLASS LABEL COLOR 60 60 60 OUTLINECOLOR 210 210 210 TYPE TRUETYPE FONT vera SIZE 8 ANTIALIAS TRUE POSITION UC ANGLE FOLLOW PARTIALS FALSE MINFEATURESIZE auto MAXOVERLAPANGLE 40 END END END LAYER NAME cours_eau METADATA ows_title Cours d'eau Carthage ows_extent 573401 6050407 1242369 6811885 ows_featureid gid END PROJECTION init=epsg:2154 END TYPE line STATUS on DATA geom from (SELECT gid, geom , classe::integer FROM aermc.cours_eau WHERE toponyme IS NOT NULL) AS foo using unique gid using srid=2154 CONNECTIONTYPE postgis CONNECTION host= port=5432 dbname= user= CLASSITEM classe CLASS EXPRESSION ([classe] = 2) STYLE COLOR 33 33 210 WIDTH 5 END END CLASS EXPRESSION ([classe] = 4) STYLE COLOR 66 66 210 WIDTH 3 END END CLASS STYLE COLOR 99 99 210 WIDTH 1 END END END HTH, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation
On Mon, Nov 19, 2012 at 2:46 PM, Тимур Галиаскарович Суфиев t.suf...@acti.ru wrote: Timur, ** I got the point: this is exactly the same fragment I've committed on Nov 01, string src/wfs_get_feature.c:825: buffer_copy(id_name, ll-value); Previously (before commits from #19) ll-value contained layer's name, and now it contains ns-uri:layer-name. Should return from ns-uri:layer-name to layer-name somehow... Thanks for the report and your code patch provided throught GitHub (and commited) For the record, this issue is relevant for GeoJSON id (GML one is safe) -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation
Hi Timur,
XML validation is such issue-rich subject, so I have another question
considering it :).
You noticed also this one ^^
Recent TinyOWS commits (from 1st Nov till 13th, I don't know which one
exactly is responsible) introduced some changes to feature ids naming, now
I have the following error on features update/delete from OpenLayers:
#19 introduced that namespaces are also to be checked from Typename
parameter.
(prior (wrong) behaviour was just to ignore namespace prefix)
[Mon Nov 19 16:03:30 2012] [ERROR] Element '{
http://www.opengis.net/ogc}FeatureId', attribute 'fid': '
http://www.tinyows.org/:cities.719' is not a valid value of the atomic
type 'xs:ID'.
Is 'ns-uri:layer-name.entity-integer-id' a new feature-id by design
or something went wrong?
Should be only layer.name.entity-integer-id (as ever)
Could you confirm that you are using current trunk version or 1.1.0 ?
--
Olivier
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation
On Fri, Nov 16, 2012 at 12:32 PM, Тимур Галиаскарович Суфиев t.suf...@acti.ru wrote: ** I found the problem (just in case it may be useful for someone): wfs layers in Javascript were using featureNS: http://www.tinyows.org; while all layers in tinyows.xml used ns_uri=http://www.tinyows.org/; Every symbol matters in deciding whether xml namespaces are the same, so adding trailing slash to Javascript solved my issue. Thanks Timur to post, for the record, your own answer ! And yes as it's an URI (and not a URL) every symbol matters... Cheers, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] TinyOWS 1.1.0 release
Hi all, The 1.1.0 TinyOWS version is out. Source code: http://www.tinyows.org/release/tinyows-1.1.0.tar.bz2 From 1.0.0 release the key point was to bugfixe, to improve again performances and strict OGC standard implementation, and few userland improvements on config file. 1.1.0 Changelog: - Add include_items and exclude_items config handling. To choose exactly which columns to retrieve (Serge Dikiy) - XSD max length and enumeration constraint handling (Serge Dikiy Alan Boudreault) - First real support of typename namespace provided in request (Olivier Courtin) - Generate PK value using PostgresSQL DEFAULT value if present (Serge Dikiy) - Add pkey configuration in layer config. Usefull for instance when retrieving data from a VIEW. (Serge Dikiy) - Buffer copy performance improve (Serge Dikiy) - Rewrite/fix max features handling (Olivier Courtin) - Extent layer's properties allowed to inherit (Olivier Courtin) - Several bugfixes as usual (special thanks to Andreas Peri, Serge Dikiy and Jukka Rahkonen for detailled reports) Documentation was also refresh, including the OpenLayers HowTo. http://ci.mapserver.org/job/docsmaster/lastSuccessfulBuild/artifact/build/html/en/tinyows/index.html#tinyows Enjoy, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation
On Wed, Nov 7, 2012 at 5:13 PM, Тимур Галиаскарович Суфиев t.suf...@acti.ru
wrote:
Hi Timur,
This isn't the first question here about inserting features in TinyOWS,
but I haven't found solution to my problem in archives.
and this xsd should make tinyows use element '{http://www.tinyows.org}cities'
like '{http://www.opengis.net/gml}_Feature'
Where am I wrong and what should be changed in my setup?
Thanks for your detailled report,
first naive question, what about the tinyows.xml config file,
and online_resource property ?
Next question, what happen, if you bypass schema validation,
with: check_schema = 0 (in tinyows element)
--
Olivier
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] One question of tinyows SELECT in postgis
On Sun, Nov 4, 2012 at 1:58 AM, Lucio Estacio lu...@cismid-uni.org wrote: Hi Lucio, I install and testing tinyows and OpenLayers client .. I work all ok. Great to hear it ! But I see in the log tinyows …and that for each transaction from client javascript is performed scanned all aggregate tables in the file /etc/tinyows.xml ... this is necessary? I guess that you're using TinyOWS as CGI rather than in Fast-CGI. (with Fast-CGI a lot of stuff are kept in memory from one request to an another, as config file informations, database structure, or GML Schema) HTH, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid
On Wed, Oct 24, 2012 at 11:52 AM, Riccardo Gaeta riccardo...@gmail.comwrote: Riccardo, I get this message, seems GeoJSON is not accepted as output, maybe I need some more .dll library in my Win7? You don't need any extra lib, it's plain vanillia. I didn't check my previous URL before posting, so OUTPUTFORMAT parameter expect application/json HTH, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS 12.10rc1
Hi Peter, I was happily trying to build it on CentOS 6, but it seems that my libxml2 is simply too old: checking for libxml2 version... 2.7.6 configure: error: You need at least libxml 2.8.0 Is there a real reason to require 2.8.0 or could this be relaxed? The reason is related to a libxml2 bug on schema handling, been fixed in 2.8.0. cf http://mapserver.org/trunk/fr/tinyows/libxmlschemagmlbug.html, If you really don't want to upgrade (even if it's not a big deal to compile libxml2) you could either choose: - to slightly modified OGC XSD Schema as describted: http://mapserver.org/trunk/fr/tinyows/libxmlschemagmlbug.html - or be sure to never use GML 3.1.1 (as the bug only impact this schema) HTH, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid
On Mon, Oct 22, 2012 at 4:55 PM, Riccardo Gaeta riccardo...@gmail.comwrote: HI Riccardo, I have quite solved the problem. Great to hear it ! P.S.: As GeoJSON I get the following error message (from FireBug of Mozilla): JSON.parse: unexpected character Uncaught SyntaxError: Unexpected token ] I don't know why. Anyway, for now is enough GML. Or if you know the reasons I get this error could be interesting to know... Could you provide GeoJson output from TinyOWS for a single feature i.e something like http://your_server/cgi-bin/tinyows.fcgi?SERVICE=WFSREQUEST=GetFeatureOUTPUTFORMAT=application/geojsonTYPENAME=ns:your_layerMAXFEATURES=1 -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid
0.9 version is that old, and should not be used anymore, for any reasons... 1.0.0rc3, well was an rc, and several fixes was corrected before launching 1.0.0 You could give a look at OSGeo4W as they provide a 1.0.0rc4 (yeap still an rc) http://trac.osgeo.org/osgeo4w/wiki/pkg-tinyows But a real solution would be that someone take Win32 packaging in charge, Also for information: http://gis-lab.info/qa/tinyows-compile-vce-eng.html -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid
Hi Riccardo, Well if everything work's fine except OpenLayers, maybe it's an OpenLayers configuration issue... TinyOWS debug tools are really unix based, so could be a bit painfull under Win32... I suggest you to begin to follow step by step this tutorial, to check that everything work as expected: http://mapserver.org/trunk/tinyows/openlayershowtobasic.html Nota: With OpenLayers client retrieving data as GeoJson is a better idea than as GML. HTH, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS and the logical operators
On Sun, Oct 14, 2012 at 1:46 AM, Andrea Peri aperi2...@gmail.com wrote: Hi Andrea, reading the getcapabilities, I see the TinyOWS has not any LogicalOperator capability like AND , OR, etc.. Is this correct for wfs 1.1.0 or is a lack of feature ? LogicalOperators are supported in TinyOWS, and it appears it the capabilities as LogicalOperators tags. Indeed you're right there's no detail on what is exactly supported at capabilities level (indeed it means 'all'), but it's related to OGC Filter XSD itself: see schema/filter/1.1.0/filterCapabilities.xsd Thanks for asking, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS and the logical operators
On Sun, Oct 14, 2012 at 12:04 PM, Andrea Peri aperi2...@gmail.com wrote:
Andrea,
If the AND operator is supported from TinyOWS, this mean that I'm wrong
something else.
Any hint is welcome
If i check with WFS 1.1 CITE:
$ sudo make install-test110
There 3 tests related to And Logical Operator with GetFeature - 0210 to
0212:
So take one:
$ test/unit_test test/wfs_110/cite/0211 4
Input query:
?xml version=1.0 encoding=UTF-8?wfs:GetFeature xmlns:wfs=
http://www.opengis.net/wfs; xmlns:ogc=http://www.opengis.net/ogc; xmlns:p=
http://teamengine.sourceforge.net/parsers; xmlns:xi=
http://www.w3.org/2001/XInclude; xmlns:saxon=http://saxon.sf.net/;
xmlns:xlink=http://www.w3.org/1999/xlink; xmlns=
http://www.occamlab.com/ctl; xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ows=http://www.opengis.net/ows; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
http://www.w3.org/2001/XMLSchema; xmlns:ctl=http://www.occamlab.com/ctl;
xmlns:sf=http://cite.opengeospatial.org/gmlsf;
xmlns:tec=java:com.occamlab.te.TECore xmlns:te=http://www.occamlab.com/te;
xmlns:parsers=http://www.occamlab.com/te/parsers; xmlns:gml=
http://www.opengis.net/gml; xmlns:myparsers=
http://teamengine.sourceforge.net/parsers; version=1.1.0
service=WFSwfs:Query
typeName=sf:AggregateGeoFeatureogc:Filterogc:Andogc:PropertyIsGreaterThanOrEqualToogc:PropertyNamesf:doubleProperty/ogc:PropertyNameogc:Literal24510/ogc:Literal/ogc:PropertyIsGreaterThanOrEqualToogc:PropertyIsEqualTo
matchCase=falseogc:PropertyNamesf:featureCode/ogc:PropertyNameogc:Literalak020/ogc:Literal/ogc:PropertyIsEqualTo/ogc:And/ogc:Filter/wfs:Query/wfs:GetFeature
SQL Request produced:
SELECT description,name,ST_AsGML(3,
ST_Transform(multiPointProperty::geometry,4326),6, 23) AS
multiPointProperty ,ST_AsGML(3,
ST_Transform(multiCurveProperty::geometry,4326),6, 23) AS
multiCurveProperty ,ST_AsGML(3,
ST_Transform(multiSurfaceProperty::geometry,4326),6, 23) AS
multiSurfaceProperty
,doubleProperty,intRangeProperty,strProperty,featureCode,id FROM
public.AggregateGeoFeature WHERE (doubleProperty = 24510 AND
lower(featureCode) = lower('ak020'))
I didn't look in detail to you query for now,
let me know it this sample is enough to you (or not),
--
Olivier
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS and the logical operators
On Sun, Oct 14, 2012 at 2:19 PM, Andrea Peri aperi2...@gmail.com wrote: Andrea, I resolved it. Perfect, The and operator is named using the first letter uppercase. So And is recognized, meanwhile AND was not recognized. I guest perhaps there is some bugs, but not really sure. Nope that's the way it is defined in filter.xsd schema (so maybe a bit uncommon as SQL itself is not case sensitive, but surely not a bug) Many thx, Your're wecome, -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] TinyOWS 12.10rc1
Hi all, TinyOWS 12.10rc1 is yet available: http://www.tinyows.org/release/mapserver-tinyows-12.10rc1.tar.bz2 Thanks in advance in advance to test, and report any bug or regression on this list 12.10 NEWS: - Generate PK value using PostgresSQL DEFAULT value if present (Serge Dikiy) - XSD max length and enumeration constraint handling (Serge Dikiy Alan Boudreault) - include_items and exclude_items config handling. To choose exactly which columns to retrieve (Serge Dikiy) - Add pkey configuration in layer config. Usefull for instance when retrieving data from a VIEW. (Serge Dikiy) - Buffer copy performance improve (Serge Dikiy) - Rewrite/fix max features handling (Olivier Courtin) - Several bugfixes as usual (special thanks to Andreas Peri, Serge Dikiy and Jukka Rahkonen for detailled reports) -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] TinyOWS 12.10rc1
On Mon, Oct 15, 2012 at 12:44 AM, Even Rouault even.roua...@mines-paris.org wrote: Compiling with clang raises 2 interesting warnings, the 2nd one being clearly a bug : src/mapfile/mapfile.l:412:18: warning: implicit conversion from enumeration type 'enum map_lmd_state' to different enumeration type 'enum map_md_state' [- Wconversion] map_md_state = MAP_LMD_TOWS_GEOBBOX; ~ ^~~~ src/ows/ows_geobbox.c:62:23: warning: argument to 'sizeof' in 'memcpy' call is the same pointer type 'ows_geobbox *' (aka 'struct Ows_geobbox *') as the destination; expected 'ows_geobbox' (aka 'struct Ows_geobbox') or an explicit length [- Wsizeof-pointer-memaccess] return memcpy(c, g, sizeof(g)); ~ ^ -- should be memcpy(c, g, sizeof(*g)); Thanks Even for these report ! fixed and commited Did'nt yet play with clang, could change soon... -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Problem with attribute names with dots
Jukka, But i need to check against CITE, that the fix don't introduce new regression, before commiting. CITE Checked and so commited, (#17). -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Problem with attribute names with dots
On Mon, Oct 8, 2012 at 11:14 PM, Rahkonen Jukka jukka.rahko...@mmmtike.fiwrote: Hi Jukka, I made a test layer with dots in feature type name and in an attribute name. The following request leads to an error. [...] I am not totally sure but probably this request is valid and it should work. I am using a little bit old TinyOWS version from April 2012 so the problem is perhaps solved already. Thanks for the detailled report, i can reproduce it with trunk version, for attribute name containing a dot, and using PropertyName query. (all others use cases are fine) I've created a ticket, including a patch: https://github.com/mapserver/tinyows/issues/17 But i need to check against CITE, that the fix don't introduce new regression, before commiting. -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Broken config using a MAPFILE?
On Wed, Sep 19, 2012 at 9:43 AM, Richard Turner richard.tur...@mediatelgroup.co.uk wrote: Hi Richard I've since set-up a new server and installed the trunk version of tinyows on it and found that instead of working fine tinyows returns the following error: ows:ExceptionTextFilter parameter doesn't validate WFS Schema/ows:ExceptionText I've slightly changed the request you provided, to make it works with a TinyOWS trunk (i use TinyOWS XML config file here): wfs:GetFeature xmlns:wfs=http://www.opengis.net/wfs; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; service=WFS version=1.0.0 xsi:schemaLocation=http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd; wfs:Query xmlns:tows=http://www.tinyows.org/; typeName=tows:france ogc:Filter xmlns:ogc=http://www.opengis.net/ogc; ogc:BBOX ogc:PropertyNamegeom/ogc:PropertyName gml:Box xmlns:gml=http://www.opengis.net/gml; srsName=EPSG:3857 gml:coordinates decimal=. cs=, ts= -417651.92249206,6609322.2049643 417651.92249206,685.9596091/gml:coordinates /gml:Box /ogc:BBOX /ogc:Filter /wfs:Query /wfs:GetFeature To go further in debug, could you activate log (or recompile tinyows with --enable-debug option) and send the whole log here. Thanks. -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Broken config using a MAPFILE?
On Wed, Sep 19, 2012 at 4:47 PM, Rahkonen Jukka jukka.rahko...@mmmtike.fiwrote: Hi Jukka I wonder why OpenLayers is sending request for wfs:Query typeName=feature:areas while I suppose that the typeName is actually mtl:areas. Dunno either, but request is valid as they define namespace: xmlns:feature=http://gis.mediatel.co.uk; in the Query. However, it looks like TinyOWS does not care about featuretype namespace at all. Well TinyOWS care about namespace with POST request This request works as it should http://188.64.1.61/cgi-bin/tinyows?service=WFSversion=1.1.0request=GetFeaturetypeName=lv:mml_paikannimet20maxFeatures=20 ** ** However, query finds also a non-existing featuretype foo:mml_paikannimet20 http://188.64.1.61/cgi-bin/tinyows?service=WFSversion=1.1.0request=GetFeaturetypeName=foo:mml_paikannimet20maxFeatures=20 But as you could seen, a bit less with GET request ! Somehow I feel this is a bug. Could worth to open a ticket, to be more strict on GET Namespace. But i don't think this behaviour is related to Richard issue. And the only way to help Richard further is to have a TinyOWS log from his issue... -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [TinyOWS] Broken config using a MAPFILE?
Hi Jukka, But as you could seen, a bit less with GET request ! Somehow I feel this is a bug. Could worth to open a ticket, to be more strict on GET Namespace. But how strict it should be? Should we learn users to include the correct namespace always in the typeName? It is correct but most users do not care about namespaces and they could feel that frustrating. And I suppose that the colon character needs to be escaped at least inside filters for making the GET requests to work and that makes things more complicated. However, it is possible that the same TinyOWS service has both foo:parcels and bar:parcels. NAMESPACE parameter is not Mandatory with GET request, (and very few clients use it) so as you said not the right way to handle it. But on the other side we have the ns_prefix value associated with every layer, so we could at least check if it match yes or no. -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [tinyOWS] libxml2 2.8.0 not released on debian
On Thu, Aug 23, 2012 at 11:06 PM, Stephen Woodbridge wood...@swoodbridge.com wrote: Hi Stephen I'm trying to build tinyOWS on Debian, but the requirement for libxml2-2.8.0 is not released on stable (squeeze) and not in the backports either. It is in testing (wheezy) but mixing versions is a recipe for problems. It would be nice if you limited library versions to what is generally release on stable OSs. A really annoying libxml2 bug was finally fixed and released with 2.8. cf http://mapserver.org/trunk/fr/tinyows/libxmlschemagmlbug.html Prior versions need workaround to make GML 3 works who could be IMHO more tricky than to compile manually libxml2. -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] [ANN] TinyOWS 1.0.0 release
Hi alls, TinyOWS 1.0.0 official release is (finally) out ! You could download it from: http://tinyows.org/tracdocs/release/tinyows-1.0.0.tar.bz2 (checksum 25c9567848b97a3ad9a111c0053e4248) ChangeLog: - Configuration change with broken backward compatibility: * default config file is now /etc/tinyows.xml * default schema dir is now $PREFIX/share/tinyows/schema * rename server and prefix to ns_uri ans ns_prefix * rename wfs_display_bbox to display_bbox - Encoding support, written by Carlos Ruiz: crui...@gmail.com - Estimated_bbox option for GetCapabilities response (default is false) - Schema cache for fast-cgi mode (huge performance improvement on transaction operations) - Improve drasticaly GetCapabilities performance on huge layer (Thanks to Nicklas Aven for report) - Add ability to use different names for layer and storage table (table property) - Mapfile config file support (use related TINYOWS_MAPFILE env. var) - Debug option available from configure step (--enable-debug) - Improve result from --check option - Add wfs_default_version config file option, to set server default WFS Version - Add gml_ns config file option, to set if any, layers properties using GML namespace - Add log_level config file option, to allow more granularity in log output - PostGIS version init check (support 1.5 and coming 2.0) - Update XSD schema (WFS, FE, GML), so need a new 'make install' step if you upgrade - CITE WFS-T 1.0.0 SF-0 full compliant (require PostGIS 2.0) - CITE WFS-T 1.1.0 SF-0 full compliant (require PostGIS 2.0) - Lot of debug stuff (a special thanks to Boris Leukert, Jukka Rahkonen and Even Rouault for detailled reports) - Security fixes (SQL Injection vulnerability - Reported by Even Rouault) Thanks again to all folks who contributed on it ! -- Olivier ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
