[gdal-dev] Change resolution tiff image

2016-02-05 Thread Paulo Pires
Hello,

I tried to change resolution (dpi) from a raster cmyk file without soccess

Is it possible? Change for example 508 to 254 dpi and mantein cmyk mode

Thanks



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Change-resolution-tiff-image-tp5249156.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] NetCDF+HDF5 and threadsafety

2016-02-05 Thread Even Rouault
Le vendredi 05 février 2016 01:41:14, William Kyngesburye a écrit :
> On Feb 4, 2016, at 5:09 PM, Even Rouault  wrote:
> > Le jeudi 04 février 2016 23:55:57, William Kyngesburye a écrit :
> >> I'm updating my HDF5 library and ran into a catch-22: I build my HDF5
> >> with threadsafety (threadsafe is good, right?), and NetCDF4 requires
> >> HDF5 with the high-level library.  At HDF5 1.8.12 I could do this
> >> combination, but HDF5 1.8.16 (I think it started with 1.8.13) says
> >> threadsafe and high-level options are not compatible.
> >> 
> >> Is threadsafety in HDF5 important for GDAL?
> > 
> > Hum, likely if people use the HDF5 driver in a multi-threaded context.
> > GDAL has explicit mutex around calls to the netCDF and HDF4 lib in the
> > netCDF and HDF4 drivers (since at least the versions of those lib I use
> > are not thread- safe), but not from the HDF5 driver. So if the HDF5 lib
> > is not re-entrant, there might be issues.
> > 
> > There's an optionnaly compiled app you can use to test threadsafety :
> > 
> > cd apps
> > make multireadtest
> > ./multireadtest -nlo [-oi number_of_iterations] file_to_test
> > 
> > Increase number_of_iterations so that it runs for a few seconds.
> 
> How do I trigger building that? 

Just like the above mentionned lines :-) After you've initially built GDAL 
from the top directory

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] PDF and EXTRA_STREAM

2016-02-05 Thread Even Rouault
Le vendredi 05 février 2016 04:22:55, Brent Fraser a écrit :
> I've been experimenting with generating Geospatial PDFs with GDAL and
> would like to wrtie some extra text and lines to the PDF file. The PDF
> drive has a Create Option of EXTRA_STREAM which looks pretty good.  I
> can add text, lines and rectangles by doing:
> 
>-co EXTRA_STREAM="BT 0 0 255 rg /FTimesRoman 50 Tf 1 0 0 1 1 1 Tm 100
> 200 Td (Hello World!) Tj ET 80 260 m 80 50 l h S 0.9 0.5 0.0 rg 400 50
> 300 200 re f"
> 
> But I think the length of the stream could get very long.  Any interest
> in adding another Create Option like
> 
> EXTRA_STREAM_FILE=my_stuff.txt
> 
> so I could put all the extra in a separate file?

You could also use the "--optfile filename" option available in all GDAL/OGR 
utilities (bottom of http://gdal.org/gdal_utilities.html ) that appends the 
content of filename to the command line.


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

[gdal-dev] RFC 61: Call for vote on adoption

2016-02-05 Thread Ari Jolma
I'd like to ask the PSC and others to vote on adopting RFC 61: Support 
for measured geometries.


The draft RFC is at

https://trac.osgeo.org/gdal/wiki/rfc61_support_for_measured_geometries

and a draft implementation is at

https://github.com/ajolma/GDAL-XYZM

which is tested at

https://travis-ci.org/ajolma/GDAL-XYZM

(the test #34, which passed, was the so far last one after core changes 
with unchanged autotests and a rather comprehensive set of WKT tests in 
the Perl tests directory)


This is seemingly a small change but it is at the heart of OGR so it has 
some important implications. The only backwards incompatibilities that 
have appeared so far are with some drivers, for example shapefile, which 
can be lessened with, e.g., open options.


Best,

Ari

___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-05 Thread Even Rouault
Le vendredi 05 février 2016 09:04:00, Ari Jolma a écrit :
> I'd like to ask the PSC and others to vote on adopting RFC 61: Support
> for measured geometries.

+1

> 
> The draft RFC is at
> 
> https://trac.osgeo.org/gdal/wiki/rfc61_support_for_measured_geometries
> 
> and a draft implementation is at
> 
> https://github.com/ajolma/GDAL-XYZM
> 
> which is tested at
> 
> https://travis-ci.org/ajolma/GDAL-XYZM
> 
> (the test #34, 

What is test #34 ?

> which passed, was the so far last one after core changes
> with unchanged autotests and a rather comprehensive set of WKT tests in
> the Perl tests directory)
> 

I see some failures in latest build, apparently related to -nlt POLYGON25D / -
lco SHPT=POLYGONZ in the shapefile driver

https://s3.amazonaws.com/archive.travis-ci.org/jobs/107177078/log.txt

  Failures 
Script: utilities/test_ogr2ogr_lib.py
  TEST: test_ogr2ogr_lib_7 ... fail
Script: utilities/test_gdal_grid_lib.py
  TEST: test_gdal_grid_lib_1 ... fail
Script: utilities/test_ogr2ogr.py
  TEST: test_ogr2ogr_11 ... fail
  TEST: test_ogr2ogr_12 ... fail
  TEST: test_ogr2ogr_43 ... fail
Script: pyscripts/test_ogr2ogr_py.py
  TEST: test_ogr2ogr_py_11 ... fail
  TEST: test_ogr2ogr_py_12 ... fail
  TEST: test_ogr2ogr_py_43 ... fail
 --

> This is seemingly a small change but it is at the heart of OGR so it has
> some important implications. The only backwards incompatibilities that
> have appeared so far are with some drivers, for example shapefile, which
> can be lessened with, e.g., open options.
> 
> Best,
> 
> Ari

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-05 Thread Tamas Szekeres
+1

I'll update the mssql spatial driver accordingly.

Best regards,

Tamas


2016-02-05 9:04 GMT+01:00 Ari Jolma :

> I'd like to ask the PSC and others to vote on adopting RFC 61:  Support
> for measured geometries.
>
> The draft RFC is at
>
> https://trac.osgeo.org/gdal/wiki/rfc61_support_for_measured_geometries
>
> and a draft implementation is at
>
> https://github.com/ajolma/GDAL-XYZM
>
> which is tested at
>
> https://travis-ci.org/ajolma/GDAL-XYZM
>
> (the test #34, which passed, was the so far last one after core changes
> with unchanged autotests and a rather comprehensive set of WKT tests in the
> Perl tests directory)
>
> This is seemingly a small change but it is at the heart of OGR so it has
> some important implications. The only backwards incompatibilities that have
> appeared so far are with some drivers, for example shapefile, which can be
> lessened with, e.g., open options.
>
> Best,
>
> Ari
>
>
> ___
> gdal-dev mailing list
> gdal-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-05 Thread Ari Jolma



05.02.2016, 10:49, Even Rouault kirjoitti:

Le vendredi 05 février 2016 09:04:00, Ari Jolma a écrit :

I'd like to ask the PSC and others to vote on adopting RFC 61: Support
for measured geometries.

+1


The draft RFC is at

https://trac.osgeo.org/gdal/wiki/rfc61_support_for_measured_geometries

and a draft implementation is at

https://github.com/ajolma/GDAL-XYZM

which is tested at

https://travis-ci.org/ajolma/GDAL-XYZM

(the test #34,

What is test #34 ?


https://travis-ci.org/ajolma/GDAL-XYZM/builds/106980691

...it has #34





which passed, was the so far last one after core changes
with unchanged autotests and a rather comprehensive set of WKT tests in
the Perl tests directory)


I see some failures in latest build, apparently related to -nlt POLYGON25D / -
lco SHPT=POLYGONZ in the shapefile driver


Yes, it fails now since the shapefile driver is partially implemented - 
only points and linestrings so far.


I made it skip one test in ogr_shape.py, which relied on the M to Z hacks.




https://s3.amazonaws.com/archive.travis-ci.org/jobs/107177078/log.txt

   Failures 
Script: utilities/test_ogr2ogr_lib.py
   TEST: test_ogr2ogr_lib_7 ... fail
Script: utilities/test_gdal_grid_lib.py
   TEST: test_gdal_grid_lib_1 ... fail
Script: utilities/test_ogr2ogr.py
   TEST: test_ogr2ogr_11 ... fail
   TEST: test_ogr2ogr_12 ... fail
   TEST: test_ogr2ogr_43 ... fail
Script: pyscripts/test_ogr2ogr_py.py
   TEST: test_ogr2ogr_py_11 ... fail
   TEST: test_ogr2ogr_py_12 ... fail
   TEST: test_ogr2ogr_py_43 ... fail
  --


This is seemingly a small change but it is at the heart of OGR so it has
some important implications. The only backwards incompatibilities that
have appeared so far are with some drivers, for example shapefile, which
can be lessened with, e.g., open options.

Best,

Ari


___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-05 Thread Jukka Rahkonen
Ari Jolma  gmail.com> writes:

> 
> 
> I'd like to ask the PSC and others to vote on adopting RFC 61: 
> 
> Support for measured geometries.

+1

-Jukka Rahkonen-
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev