could you quickly name the plugin that generates a bounding box and (probably again) what has to be taken into accout wrt. to the order of the coordinates? then i could have a look if i could quiclky hack that within the next days.
..ede On 23.11.2017 13:03, Rahkonen Jukka (MML) wrote: > We have been living without bounding box so it could be empty. On the other > hand, we have a function that computes the envelope and it could be also an > enhancement to have correct boundedBy. For example GDAL wants to know the > bounds of the layer and now it is reading all the features from JML for > getting the aggregated extents. > > -Jukka- > > -----Alkuperäinen viesti----- > Lähettäjä: [email protected] [mailto:[email protected]] > Lähetetty: 23. marraskuuta 2017 13:20 > Vastaanottaja: jump devel <[email protected]> > Aihe: Re: [JPP-Devel] SRID support in JML > > :) nice catch, > > looks like they standardized it that way, so i'd say let's do it accordingly. > do we really need to calculate a bounding box or is it valid to leave it > empty? > > ..ede > > On 23.11.2017 12:14, Rahkonen Jukka (MML) wrote: >> Hi, >> >> Workaround or convenience as OGC writes in the WFS 2.0 standard: >> >> 11.3.6 Inheritance rules for srsName values For convenience in >> constructing feature collection instances, the value of the srsName >> attribute on the gml:Envelope which is the value of the wfs:boundedBy >> property of a response feature collection shall be inherited by all >> directly expressed geometries in all properties of the members of the >> collection, unless overruled by the presence of a local srsName. Thus >> it is not necessary for a geometry to carry a srsName attribute, if it >> uses the same coordinate reference system as given on the >> wfs:boundedBy property of the envelope. Inheritance of the coordinate >> reference system continues to any depth of nesting, but if overruled >> by a local srsName declaration, then the new coordinate reference >> system is inherited by all its children in turn >> >> -Jukka- >> >> -----Alkuperäinen viesti----- >> Lähettäjä: [email protected] [mailto:[email protected]] >> Lähetetty: 23. marraskuuta 2017 12:27 >> Vastaanottaja: [email protected] >> Aihe: Re: [JPP-Devel] SRID support in JML >> >> Jukka, >> >> this looks more like a workaround, misusing a bounding box definition's >> saved srs although it of course should match the data's. >> >> the clean gml way would probably be (as you mentioned) to srs tag every >> feature as the standard expects, but that of course would blow up the >> dataset exponentially unnecessarily. >> >> ..ede >> >> On 23.11.2017 11:05, Rahkonen Jukka (MML) wrote: >>> Or we could add a CRS element into GML Input Template section and >>> boundedBy like in GML2 into the data section: >>> >>> <?xml version='1.0' encoding='UTF-8'?> <JCSDataFile >>> xmlns:gml="http://www.opengis.net/gml" >>> xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" > >>> <JCSGMLInputTemplate> >>> <CollectionElement>featureCollection</CollectionElement> >>> <CRSElement>boundedBy</CRSElement> >>> <FeatureElement>feature</FeatureElement> >>> <GeometryElement>geometry</GeometryElement> >>> <ColumnDefinitions> >>> </ColumnDefinitions> >>> </JCSGMLInputTemplate> >>> >>> <featureCollection> >>> <gml:boundedBy> >>> <gml:Box srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> >>> <gml:coordinates decimal="." cs="," ts=" ">474.0,280.0 >>> 620.0,380.0</gml:coordinates> >>> </gml:Box> >>> </gml:boundedBy> >>> <feature> >>> ... >>> >>> -Jukka- >>> >>> >>> -----Alkuperäinen viesti----- >>> Lähettäjä: Rahkonen Jukka (MML) >>> Lähetetty: 23. marraskuuta 2017 11:36 >>> Vastaanottaja: [email protected] >>> Aihe: Re: [JPP-Devel] SRID support in JML >>> >>> Hi, >>> >>> So could it work simply by adding srsName as an attribute into >>> featureCollection: >>> >>> <?xml version='1.0' encoding='UTF-8'?> <JCSDataFile >>> xmlns:gml="http://www.opengis.net/gml" >>> xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" > >>> <JCSGMLInputTemplate> >>> <CollectionElement>featureCollection</CollectionElement> >>> <FeatureElement>feature</FeatureElement> >>> <GeometryElement>geometry</GeometryElement> >>> <ColumnDefinitions> >>> </ColumnDefinitions> >>> </JCSGMLInputTemplate> >>> >>> <featureCollection srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"> >>> <feature> >>> <geometry> >>> <gml:Polygon> >>> <gml:outerBoundaryIs> >>> <gml:LinearRing> >>> <gml:coordinates>474.0,371.0 >>> 620.0,380.0 >>> 520.0,280.0 >>> 474.0,371.0 </gml:coordinates> >>> </gml:LinearRing> >>> </gml:outerBoundaryIs> >>> </gml:Polygon> >>> </geometry> >>> </feature> >>> >>> </featureCollection> >>> </JCSDataFile> >>> >>> >>> -----Alkuperäinen viesti----- >>> Lähettäjä: [email protected] [mailto:[email protected]] >>> Lähetetty: 22. marraskuuta 2017 23:35 >>> Vastaanottaja: [email protected] >>> Aihe: Re: [JPP-Devel] SRID support in JML >>> >>> Jukka, >>> >>> adding to the XML structure will be ignored by current readers. changing >>> the structure would break things. >>> >>> ..ede >>> >>> On 11/22/2017 21:41, Rahkonen Jukka (MML) wrote: >>>> Hi, >>>> >>>> In GML srsName is set for each feature. See the GML2 response from >>>> http://demo.geo-solutions.it/geoserver/wfs?service=wfs&version=1.0.0 >>>> & >>>> r >>>> equest=getfeature&typename=topp:states&maxfeatures=5 >>>> We have the same SRID for the whole layer so one occurrance per file would >>>> be enough. But I wonder if changing the JML format would break backwards >>>> interoperability? I don't like the sidecar files but they would not make >>>> harm for old OJ versions. >>>> >>>> -Jukka- >>>> >>>> ________________________________________ >>>> Lähettäjä: [email protected] <[email protected]> >>>> Lähetetty: 22. marraskuuta 2017 18:42 >>>> Vastaanottaja: [email protected] >>>> Aihe: Re: [JPP-Devel] SRID support in JML >>>> >>>> as jml is essentially gml, how is srid support defined in the gml specs? >>>> >>>> ..ede >>>> >>>> On 22.11.2017 17:40, Giuseppe Aruta wrote: >>>>> we should investigate o JML documentation (if any) if this format support >>>>> embedded projection info. Another alternative could be that those infos >>>>> can be stored in any external extra file, like .prj or .aux, in this case >>>>> OpenJUMP is already able to read srid from any <file name>.<file >>>>> format>.aux.xml file stored with the dataset. >>>>> Peppe >>>>> >>>>> >>>>> 2017-11-22 16:47 GMT+01:00 <[email protected] >>>>> <mailto:[email protected]>>: >>>>> >>>>> Jukka, >>>>> >>>>> you are right. just checked! as SRID is held in a style object and >>>>> styles are only saved in projects, a saved JML file currently lacks this >>>>> information. >>>>> >>>>> .ede >>>>> >>>>> On 22.11.2017 16:19, Rahkonen Jukka (MML) wrote: >>>>> > Hi, >>>>> > >>>>> > >>>>> > >>>>> > Am I right that we have an enhanced SRID support in OpenJUMP and >>>>> shapefiles via .prj files, but nothing at all for JML format? >>>>> > >>>>> > >>>>> > >>>>> > -Jukka Rahkonen- >>>>> > >>>>> > >>>>> > >>>>> > >>>>> ------------------------------------------------------------------------------ >>>>> > Check out the vibrant tech community on one of the world's most >>>>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>>> > >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > Jump-pilot-devel mailing list >>>>> > [email protected] >>>>> <mailto:[email protected]> >>>>> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> <https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel> >>>>> > >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Check out the vibrant tech community on one of the world's most >>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>>> _______________________________________________ >>>>> Jump-pilot-devel mailing list >>>>> [email protected] >>>>> <mailto:[email protected]> >>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> <https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------- >>>>> - >>>>> - >>>>> --------- Check out the vibrant tech community on one of the >>>>> world's most engaging tech sites, Slashdot.org! >>>>> http://sdm.link/slashdot >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Jump-pilot-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> >>>> >>>> >>>> -------------------------------------------------------------------- >>>> - >>>> - >>>> -------- Check out the vibrant tech community on one of the world's >>>> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>> _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>> >>>> -------------------------------------------------------------------- >>>> - >>>> - >>>> -------- Check out the vibrant tech community on one of the world's >>>> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>> _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>> >>> >>> >>> --------------------------------------------------------------------- >>> - >>> -------- Check out the vibrant tech community on one of the world's >>> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> --------------------------------------------------------------------- >>> - >>> -------- Check out the vibrant tech community on one of the world's >>> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >> >> >> ---------------------------------------------------------------------- >> -------- Check out the vibrant tech community on one of the world's >> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jump-pilot-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> ---------------------------------------------------------------------- >> -------- Check out the vibrant tech community on one of the world's >> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jump-pilot-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most engaging tech > sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
