Felix,
following your proposal would make Shapefiles cease to respect the
dBaseIV Standard and potentially seriously affect their interchangability.
There are a range of alternative formats supported by GDAL that achieve
your goal: for example, I use SQL as my base format and only convert wh
James,
in reality, are you not requesting an implementation of Tomlin's
'Grid Algebra' in GDAL? That defines the whole range of functions from
whole raster to pixel and has the distinct advantage of being both
published and extremely well known because of other implementations ...
which als
I am a humble geologist, rather than a Computer Scientist, and do not
pretend to understand all the ins-and-outs of this type of discussion - and
hence read, in the hopes of learning, but otherwise keep quiet!
I suspect that I am also something of a 'throw-back' in that I continue to
use Simula as
Jukka, Richard,
firstly, ESRI contracted the late John P Snyder, from USGS, to
design and initially implement their projection tools. The team now
maintaining and developing this code has a highly respected pedigree.
Whilst mistakes *do* happen, I think the ESRI code will most likely be
r
On 10 February 2016 at 12:31, Even Rouault
wrote:
> Le mercredi 10 février 2016 13:05:20, Peter Halls a écrit :
> > Ari, et al,
> >
> > ESRI handle this in a non-intuitive way: XYM is supported, but Z
> > always has a Measure, so is XYZM! The formal d
Ari, et al,
ESRI handle this in a non-intuitive way: XYM is supported, but Z
always has a Measure, so is XYZM! The formal definition is here:
https://www.*esri*.com/library/whitepapers/pdfs/*shapefile*.pdf (1998)
Shape Types having Z are defined on pp19ff where it states:
"Shape
.
Best wishes,
Peter
On 28 January 2016 at 09:04, Even Rouault
wrote:
> Le jeudi 28 janvier 2016 09:58:06, Peter Halls a écrit :
> > Ari, Even,
> >
> > one potential solution where M data are present but not supported
> by
> > the Geometry type would be to add M a
Ari, Even,
one potential solution where M data are present but not supported by
the Geometry type would be to add M as a user defined attribute, as is done
for Z values in some drivers / packages. This preserves both the geometry
integrity and the data. Should the user wish to 'upgrade' th
Ari,
I do not think that Z and M can ever be truly synonymous: whilst z is
partially defined in terms of, for example, a datum, there is no equivalent
for M. Also, by convention, X, Y and Z frequently employ the same units;
there is no equivalent convention for M (as yet).
There may be
Why would you want to map a Shapefile into a Geotiff file? They are
two fundamentally different types of spatial object. Shapefiles are
exclusively vector in nature, whilst Geotiffs are exclusively raster.
I suggest reading a text, such as Burrough and McDonnell, Principles
of Geographical Inform
Thanks, Even and Daniel. I see the logic behind the arguments.
The stand-alone utilities are probably the most heavility used
GDAL/OGR code. Once these have been subsumed into internal function
calls, do we continue to provides the stand-alone utilities?
Programming seems to be a cyclic requirem
Maybe I've missed the point (through over familiarity with GDAL/OGR?)
but these utilities were originally branded as 'worked examples'
of how to use the substantive libraries to perform well understood
operations from which usage of the libraries might be readily
understood. Each utility is i
Michael, Evan,
ArcGIS is dpocumented as not reporting values that do not occur.
In this instance, the minimum values are (R) 60 (G) 230 and (B) 208.
None of these sequences begins at zero, an important factor if
computing the range of values. I think this behaviour goes back to
the earlie
y be times when a submitted bug becomes an
enhancement request, perhaps due to the scale of the changes
necessary.
Best wishes,
Peter Halls
On 12 December 2014 at 14:48, Even Rouault wrote:
> Hi,
>
> Seeing Jukka's effort those last days to clean dust from GDAL Trac tickets
> (fo
Martin,
when working with Oracle, it is always worth looking up an ORA
message number at Oracle: you will find a full explanation and suggestions
for resolution.
For your error, look up http://ora-12154.ora-code.com/
In summary, the error means that the Oracle client is unable
David,
http://www.qgis.nl/2012/07/13/koppelen-van-data-uit-csv-bestand/?lang=endefines
the cvst file as a sequence of comma separated column definitions.
The examples are all 'dense', with no space between the comma and the next
value. It seems odd to define it in this way - perhaps there is a r
segments must be reversed when building the polygon.
Does that help?
Best wishes,
Peter
On 15 March 2013 12:50, Alisson Barbosa wrote:
> Thank you Chaitanya,
>
> I had read the explanation of Peter Halls. But that was *raster
> polygonization*. I am currently working with another
Nick,
you are asking questions about the inner workings of GDAL/OGR, rather
than the Java API. At the heart of GDAL/OGR is a library of C++ functions
that do the work. So, when you open a dataset, the low level routines
obtain memory for the data structures, populate them and pass, as a res
Alisson, Hugo,
I think a reason for the lack of response is that the operation
you need is a tad more involved than is supported by ogr2ogr - which
performs simple geometrical operations but is really designed to
perform format translations.
To go from a spaghetti of lines to polygons re
Thomas,
On 24 November 2012 01:09, cheesybiscuits wrote:
> Ivan, thanks for the suggestions.
>
> The Oracle client is 32 bit, and as you noted GDAL is also 32 bit.
I think you would get different errors if you were trying to run a
mixed 32bit / 64bit environment as this is not allowed by Windows
Alisson,
the advice I give my students in such a circumstance is to buffer the
boundary by either one half of the pixel size or by the pixel size. This
has the effect of increasing the mask to include all cells along the
boundary and gain a closer equivalent of a vector clip.
For another
As a programmer using GDAL/OGR, I do not think I mind if there are API
changes at major releases - especially, as with GDAL, where these are
infrequent - but might be annoyed during point releases. It is reasonable
to expect major new features and rationalisation at major releases, so the
burden o
Ari,
as a user (and teacher of users), I would urge you to keep to the model
where the output is always a new object (actually the same as ArcGIS),
rather than consider modifying an input for any of these spatial
operations. That automatically solves the read-only input issue.
Best wishes,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4326"]]
FID Column = OBJECTID
Geometry Column = SHAPE
TYPE: String (0.0)
NAME: String (0.0)
ONEWAY: String (0.0)
LANES: Real (0.0)
}}}
Has anyone else noticed this? (testing with OGR-created fgb seems to
-
I recall someone describing it as GML2.5 but cannot remember who or where.
I do not know whether this is liable to cause any problems for you.
Best wishes,
Peter
Warm regards,
Jez
-Original Message-
From: p...@york.ac.uk [mailto:p...@york.ac.uk] On Behalf Of Peter Halls
Sent: Tue
u
confirm I'm right that ogr2ogr does NOT support this?
Warm regards,
Jez
-Original Message-
From: p...@york.ac.uk [mailto:p...@york.ac.uk] On Behalf Of Peter Halls
Sent: Tuesday 17 August 2010 08:36
To: Jez Walters
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Handling Ordna
me! :-)
Warm regards,
Jez
--
------
Peter Halls, University of York GIS Advisor
Snail Mail: Computing Service, Heslington, York YO10 5DD, England
Telephone: 01904 433806 FAX: 01904 433740
This message has the status of a pr
o achieve this.But I did not find any
documentation or examples to guide. I would be thankful if anyone can
provide me suitable examples or guide me in locating suitable
documenation.
--
------
Peter Halls, University of Yo
to build newest gdal,
as well as OpenEV2 using GTK2.
Have tried CentOS. But it libraries seem too conservative.
Is Fedora 9 a better choice?
thanks,
Shawn
--
------
Peter Halls, University of York GIS Advisor
Snail Mail: Co
29 matches
Mail list logo
