Thanks Even,
I’ll try that out
Andy
Andrew,
the GMLAS driver will fetch it as a string:
$ ogrinfo GMLAS:input.gml -oo remove_unused_layers=yes -al -q
Warning 1: Unhandled type: gMonthDay
Warning 1: Unhandled type: gMonthDay
Layer name: departedfeature
OGRFeature(departedfeature):1
ogr_pki
ukuuta 2022 15.08
*Vastaanottaja:* gdal-dev@lists.osgeo.org
*Aihe:* [gdal-dev] ogr gml Box handling
Hi,
Trying to pull in the bounding box / envelope “Box” when loading gml
with ogr2ogr
257023.700,620210.000
257023.700,620210.000
I’ve tried boundedBy in my
gfs file.
I’ve als
ntains also just one point but probably you want to deal with more generic
data.
-Jukka Rahkonen-
Lähettäjä: gdal-dev
mailto:gdal-dev-boun...@lists.osgeo.org>>
Puolesta Andrew Terry
Lähetetty: torstai 22. joulukuuta 2022 15.08
Vastaanottaja: gdal-dev@lists.osgeo.org<mailto:gdal-dev@li
but probably you want to deal with more generic
data.
-Jukka Rahkonen-
Lähettäjä: gdal-dev Puolesta Andrew Terry
Lähetetty: torstai 22. joulukuuta 2022 15.08
Vastaanottaja: gdal-dev@lists.osgeo.org
Aihe: [gdal-dev] ogr gml Box handling
Hi,
Trying to pull in the bounding box / envelope &quo
Hi,
Trying to pull in the bounding box / envelope "Box" when loading gml with
ogr2ogr
257023.700,620210.000 257023.700,620210.000
I've tried boundedBy in my gfs file.
I've also tried seeing if I can pull through as a string using:
bbox
boundedBy|Box|coordinates
Stri
Selon Matt Langley :
> I'm trying to convert some shapefiles to GML using both ogr2ogr and python
> code. In both cases I'm having trouble making the 'dataset creation options'
> work preoperly.
>
> Setting the XSISCHEMAURI seems to work. i.e
>
> /ogr2ogr -f GML test.gml shape_folder -dsco XSISCHE
I also should note, that when trying to apply mutliple -dsco options I have
used this syntax:
ogr2ogr -f GML test.gml shape_folder -dsco PREFIX=tst -dsco
TARGET_NAMESPACE=http://tst.com.au/
In the case above neither the PREFIX or TARGET_NAMESPACE seem to get set in
the output.
--
View this mes
I'm trying to convert some shapefiles to GML using both ogr2ogr and python
code. In both cases I'm having trouble making the 'dataset creation options'
work preoperly.
Setting the XSISCHEMAURI seems to work. i.e
/ogr2ogr -f GML test.gml shape_folder -dsco XSISCHEMAURI=http:\\mytest.com/
If I set
On 01/09/2011 00:28, Even Rouault wrote:
Le jeudi 01 septembre 2011 00:19:52, Elijah Robison a écrit :
ogr2ogr -f "GML" "/vsistdout/"
"C:\xData\CountyUpdate\GeoFix\feb16_polygons.shp" -sql "select * from
feb16_polygons where objectid= 2126"
ogr2ogr -f "KML" "/vsistdout/"
"C:\xData\CountyUpdate
That is a good news !
On Wed, Jan 5, 2011 at 5:02 PM, Ralf Suhr wrote:
> Hi Chris,
>
> if you have a newer gdal version (1.8). ogrinfo will produce:
>
> Layer name: AddressPoint
> Geometry: Point
> Feature Count: 1
> Extent: (405525.60, 628349.00) - (405525.60, 628349.00)
> Layer
Hi Chris,
if you have a newer gdal version (1.8). ogrinfo will produce:
Layer name: AddressPoint
Geometry: Point
Feature Count: 1
Extent: (405525.60, 628349.00) - (405525.60, 628349.00)
Layer SRS WKT:
(unknown)
version: Integer (0.0)
versionDate: String (10.0)
theme: String (7.0)
On Jan 5, 2011, at 11:13 AM, ext Sebastian E. Ovide wrote:
> Hi All,
>
> ogrinfo is skiping some fields my gml files
>
> for example the fields addressStatus, matchStatus, physicalStatus,
> positionalQuality and structureType are not read...
Those are complex fields, which OGR doesn't ha
Sebastian,
you didn't mention the GDAL version you are using. There has been a lot of
improvements done in the GML driver in GDAL trunk over the last few months and
theoritically you should now be able to see the fields that are not immediate
children of the Feature element. You can try GDAL 1.8.0
Hi All,
ogrinfo is skiping some fields my gml files
for example the
fields addressStatus, matchStatus, physicalStatus, positionalQuality
and structureType are not read...
11
2009-10-12
Address
Matched
Existing
Final
Permanent Building
AP6DJK8352W7DAUGJG
405525.600,628349.000
16
WEST
14 matches
Mail list logo
