Re: [GRASS-user] v.out.ogr and Date fields

Many thanks for fixing this issue; the export of Date fields using v.out.ogr is working perfectly with GRASS 7.9.dev cloned from github this morning. best regards, Daniel On 11/11/2019 21:12, Markus Neteler wrote: On Wed, Nov 6, 2019 at 8:30 PM Markus Metz wrote: On Wed, Nov 6, 2019 at

Re: [GRASS-user] v.out.ogr and Date fields

On Wed, Nov 6, 2019 at 8:30 PM Markus Metz wrote: > On Wed, Nov 6, 2019 at 4:52 PM Markus Metz > wrote: > > > > > > > > On Wed, Nov 6, 2019 at 3:01 PM Markus Neteler wrote: > > > > > > Hi Daniel, > > > > > > On Mon, Nov 4, 2019 at 12:23 PM Daniel McInerney > > > wrote: > > > > > > > > Hi

Re: [GRASS-user] v.out.ogr and Date fields

On Wed, Nov 6, 2019 at 4:52 PM Markus Metz wrote: > > > > On Wed, Nov 6, 2019 at 3:01 PM Markus Neteler wrote: > > > > Hi Daniel, > > > > On Mon, Nov 4, 2019 at 12:23 PM Daniel McInerney > > wrote: > > > > > > Hi List, > > > > > > As part of a workflow, we are importing ESRI Shapefiles into

Re: [GRASS-user] v.out.ogr and Date fields

On Wed, Nov 6, 2019 at 3:01 PM Markus Neteler wrote: > > Hi Daniel, > > On Mon, Nov 4, 2019 at 12:23 PM Daniel McInerney > wrote: > > > > Hi List, > > > > As part of a workflow, we are importing ESRI Shapefiles into GRASS so > > that we can manage the vector topology, before re-exporting the

Re: [GRASS-user] v.out.ogr and Date fields

On Wed, 6 Nov 2019, Markus Neteler wrote: AFAIK this is how SQLite handles it internally but the GRASS DBMI driver should take care of it to keep it in date format. SQLite stores all data types as strings. The names we assign are for our use, not the database's. This has been true for years.

Re: [GRASS-user] v.out.ogr and Date fields

Hi Daniel, On Mon, Nov 4, 2019 at 12:23 PM Daniel McInerney wrote: > > Hi List, > > As part of a workflow, we are importing ESRI Shapefiles into GRASS so > that we can manage the vector topology, before re-exporting the vectors > back to an ESRI Shapefile. However, we noticed that the date

[GRASS-user] v.out.ogr and Date fields

Hi List, As part of a workflow, we are importing ESRI Shapefiles into GRASS so that we can manage the vector topology, before re-exporting the vectors back to an ESRI Shapefile. However, we noticed that the date fields are being converted from a field of type Date to type String. Hopefully

[GRASS-user] v.out.ogr: properly identifying map/table

There is a postgres table named 'wrb_boundary' but grass knows it as 'wrb.' When I try to export it as a shapefile I fail: v.out.ogr in=wrb type=area format=ESRI_Shapefile out=basin_bnd.shp --o DBMI-PostgreSQL driver error: select * from wrb where 1 = 0 ERROR: relation "wrb" does not exist LINE

[GRASS-user] v.out.ogr warning when exporting to shapefile

Dear list, I need to export some vector data to ESRI shapefiles. I use v.out.ogr and get several times warnings like: "Warning 1: Value 15246.47989 of field areaArabA of feature 6 not successfully written. Possibly due to too larger number with respect to field width" However,

Re: [GRASS-user] v.out.ogr - layer name

On Fri, Jan 4, 2019 at 4:04 PM Moritz Lennert wrote: > > On 3/01/19 15:13, Daniel McInerney wrote: > > Hi List, > > > > When I export a vector using v.out.ogr, I'm unable to assign an output > > layer name when the output format is 'ESRI_Shapefile'. For example: > > > > v.out.ogr input=grid_clip

Re: [GRASS-user] v.out.ogr - layer name

On 3/01/19 15:13, Daniel McInerney wrote: Hi List, When I export a vector using v.out.ogr, I'm unable to assign an output layer name when the output format is 'ESRI_Shapefile'. For example: v.out.ogr input=grid_clip output=grid_clip.shp output_layer=sub_grid format='ESRI_Shapefile' Exporting

[GRASS-user] v.out.ogr - layer name

Hi List, When I export a vector using v.out.ogr, I'm unable to assign an output layer name when the output format is 'ESRI_Shapefile'. For example: v.out.ogr input=grid_clip output=grid_clip.shp output_layer=sub_grid format='ESRI_Shapefile' Exporting 4 areas (may take some time)...  100%

Re: [GRASS-user] v.out.ogr -n segfaults

On Tue, Dec 18, 2018 at 3:07 PM Robert Nuske wrote: > > Dear List(en)ers, > > trying to work around my previously reported issue (v.patch eating my > polygons) I run into a segfault: > > > v.out.ogr -n in=gaps_1 out=gaps_coll > Segmentation fault (core dumped) Fixed in G7.4, G7.6, and trunk,

[GRASS-user] v.out.ogr -n segfaults

Dear List(en)ers, trying to work around my previously reported issue (v.patch eating my polygons) I run into a segfault: > v.out.ogr -n in=gaps_1 out=gaps_coll Segmentation fault (core dumped) Can anyone reproduce this? thanks robert ___

Re: [GRASS-user] v.out.ogr not working

On Thu, Jan 11, 2018 at 9:02 PM, Markus Neteler wrote: > > On Thu, Jan 11, 2018 at 6:08 PM, alassane toure wrote: > > > > Markus & Mauricio, > > v.out.ogr now works under grass74. > > Excellent! It is a pity that the GUI does not report the actual error. >

Re: [GRASS-user] v.out.ogr not working

On Thu, Jan 11, 2018 at 6:08 PM, alassane toure wrote: > > Markus & Mauricio, > v.out.ogr now works under grass74. Excellent! > ESRI Shapefile is not a default and its specification is required. Yes, because we switched to GeoPackage vector as the default export vector

Re: [GRASS-user] v.out.ogr not working

Ok GRASS75 it will be. Will keep you posted! Again thanks guys for making time for this On Wed, Jan 10, 2018 at 5:14 PM, Markus Metz wrote: > > > On Wed, Jan 10, 2018 at 5:38 PM, alassane toure wrote: > > > > Markus, > > Here is the system

Re: [GRASS-user] v.out.ogr not working

On Wed, Jan 10, 2018 at 5:38 PM, alassane toure wrote: > > Markus, > Here is the system response. The code goes through the process but does not create the output file! The first two errors make sense, you would need to use the --overwrite flag. The last call of v.out.ogr is

Re: [GRASS-user] v.out.ogr not working

Thanks Markus, I will try your suggestion too! alassane On Wed, Jan 10, 2018 at 9:25 AM, alassane toure wrote: > Thanks for your response Mauricio. > > Ok I will try it but v.out.ogr in GUI and in python script works using > GRASS70 though! > > alassane > > > > On Tue, Jan

Re: [GRASS-user] v.out.ogr not working

Thanks for your response Mauricio. Ok I will try it but v.out.ogr in GUI and in python script works using GRASS70 though! alassane On Tue, Jan 9, 2018 at 10:13 PM, Maurício Vancine < mauricio.vanc...@gmail.com> wrote: > Hi Alassane, > > maybe the problem can be the name size of columns in

Re: [GRASS-user] v.out.ogr not working

On Wed, Jan 10, 2018 at 7:24 AM, Markus Neteler wrote: > > > > Am 10.01.2018 1:56 vorm. schrieb "alassane toure" : > > Group, > I have been spending a lot of time on this and I need help. I am using grass72/ gdal2.2 and both my python script and grass72 are

Re: [GRASS-user] v.out.ogr not working

Am 10.01.2018 1:56 vorm. schrieb "alassane toure" : Group, I have been spending a lot of time on this and I need help. I am using grass72/ gdal2.2 and both my python script and grass72 are not producing the expected output when i run v.out.ogr! v.in.ogr does work though!

Re: [GRASS-user] v.out.ogr not working

Hi Alassane, maybe the problem can be the name size of columns in the attribute table. Try with short name. Best. 2018-01-09 22:56 GMT-02:00 alassane toure : > Group, > I have been spending a lot of time on this and I need help. I am using > grass72/ gdal2.2 and both my

[GRASS-user] v.out.ogr not working

Group, I have been spending a lot of time on this and I need help. I am using grass72/ gdal2.2 and both my python script and grass72 are not producing the expected output when i run v.out.ogr! v.in.ogr does work though! v.out.ogr input=parcel type=area output=/home/atourej/Data/prcl.shp parcel

Re: [GRASS-user] v.out.ogr with -spat?

> On Aug 18, 2017, at 1:08 AM, Moritz Lennert > wrote: > > On 18/08/17 07:36, Jeshua Lacock wrote: >> Greetings, >> I have huge vector databases (~50 million records) that I need to export as >> many tens of thousands of tiles. >> Is it possible to use ogr2ogr’s

Re: [GRASS-user] v.out.ogr with -spat?

On 18/08/17 07:36, Jeshua Lacock wrote: Greetings, I have huge vector databases (~50 million records) that I need to export as many tens of thousands of tiles. Is it possible to use ogr2ogr’s spat argument when exporting with v.out.ogr, perhaps using its’ dsco or lco arguments? AFAIK, no.

[GRASS-user] v.out.ogr with -spat?

Greetings, I have huge vector databases (~50 million records) that I need to export as many tens of thousands of tiles. Is it possible to use ogr2ogr’s spat argument when exporting with v.out.ogr, perhaps using its’ dsco or lco arguments? Otherwise, is there a faster (more efficient) way

Re: [GRASS-user] v.out.ogr to GeoJSON + crs definition

On Wed, Feb 3, 2016 at 12:06 AM, Markus Neteler wrote: > Hi, > > On Mon, Feb 1, 2016 at 9:14 PM, Panagiotis Mavrogiorgos > wrote: > > Hi everybody, > > > > is it possible to make v.out.ogr specify the projection when exporting to > > GeoJSON? > > > > I.e. to

Re: [GRASS-user] v.out.ogr to GeoJSON + crs definition

Hi, On Mon, Feb 1, 2016 at 9:14 PM, Panagiotis Mavrogiorgos wrote: > Hi everybody, > > is it possible to make v.out.ogr specify the projection when exporting to > GeoJSON? > > I.e. to have a "crs" field: ... could you please check if OGR can do that (ogr2ogr)? I vaguely

[GRASS-user] v.out.ogr to GeoJSON + crs definition

Hi everybody, is it possible to make v.out.ogr specify the projection when exporting to GeoJSON? I.e. to have a "crs" field: { "type": "FeatureCollection", "crs": { "type": "name", "properties": { "name": "urn:ogc:def:crs:EPSG::3358" } }, "features": [ {

Re: [GRASS-user] v.out.ogr dialog ask for user to type entire output path

Hi, 2015-03-16 13:47 GMT+01:00 Daniel Victoria daniel.victo...@gmail.com: In the 'Name of output OGR datasource' field, the user has to type the entire path, which some times can be quite long. Of course I can copy/paste the output path but couldn't we have a directory or file chooser dialog

[GRASS-user] v.out.ogr dialog ask for user to type entire output path

Hi List, Just an observation and an improvement idea. I'm exporting some vector files with v.out.ogr (Grass 7.0 on Win7) In the 'Name of output OGR datasource' field, the user has to type the entire path, which some times can be quite long. Of course I can copy/paste the output path but couldn't

Re: [GRASS-user] v.out.ogr drops some columns with non informative error

On Wed, Dec 17, 2014 at 4:57 PM, Rich Shepard rshep...@appl-ecosys.com wrote: On Wed, 17 Dec 2014, Moritz Lennert wrote: AFAICT, the error message comes from OGR, not GRASS. So best would be to get OGR to provide a more helpful error message. I don't think it would be very practical for GRASS

[GRASS-user] v.out.ogr drops some columns with non informative error

Hi, I'm experiencing this problem, exporting a vector file with a table associated, several columns are exported but two of them are dropped, and the error is not informative: ERROR 6: Failed to add field named 'wetness_idx' ERROR 6: Failed to add field named 'elevabovestr' I'm struggling to

Re: [GRASS-user] v.out.ogr drops some columns with non informative error

On 17/12/14 14:59, Margherita Di Leo wrote: Hi, I'm experiencing this problem, exporting a vector file with a table associated, several columns are exported but two of them are dropped, and the error is not informative: ERROR 6: Failed to add field named 'wetness_idx' ERROR 6: Failed to add

Re: [GRASS-user] v.out.ogr drops some columns with non informative error

Hi Moritz, On Wed, Dec 17, 2014 at 3:59 PM, Moritz Lennert mlenn...@club.worldonline.be wrote: Are you exporting to shapefile ? There is a 10-letter limit to column names and apparently also a 255 columns limit: http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?

Re: [GRASS-user] v.out.ogr drops some columns with non informative error

On 17/12/14 16:26, Margherita Di Leo wrote: Hi Moritz, On Wed, Dec 17, 2014 at 3:59 PM, Moritz Lennert mlenn...@club.worldonline.be mailto:mlenn...@club.worldonline.be wrote: Are you exporting to shapefile ? There is a 10-letter limit to column names and apparently also a 255

Re: [GRASS-user] v.out.ogr drops some columns with non informative error

On Wed, 17 Dec 2014, Moritz Lennert wrote: AFAICT, the error message comes from OGR, not GRASS. So best would be to get OGR to provide a more helpful error message. I don't think it would be very practical for GRASS to check for OGR errors and then translate them to something more

[GRASS-user] v.out.ogr: Convert Attribute Database?

Trying to convert the attribute database of a vector (points) table from dbf to postgres, and I'm missing a critical step. Asked and answered: GRASS 6.5.svn (Washington-Kinross):~/grassdata v.db.connect map=surface_h2o -p Vector map surface_h2o@buckhorn is connected by: layer 1 table

[GRASS-user] v.out.ogr issue

Hi List, I'm having trouble exporting a GRASS vector file using v.out.ogr. The file contains 1 million areas and its attributes are stored in a postgresql table (view of joined tables and connected to geometry using v.db.connect). When I run the following command: v.out.ogr -c type=area

[GRASS-user] v.out.ogr and region

Greetings I'm exporting data from GRASS to Gtif and Shapefiles. While r.out.gdal obays my Region definition v.out.org no. It exports all extent not the specified region. Wasn't it suppose to export only for defined region? Thanks __ Information from ESET NOD32 Antivirus, version of

Re: [GRASS-user] v.out.ogr and region

António Rocha wrote: Greetings I'm exporting data from GRASS to Gtif and Shapefiles. While r.out.gdal obays my Region definition v.out.org no. It exports all extent not the specified region. Wasn't it suppose to export only for defined region? No, AFAIK, none of the v.in.* nor v.out.* are

[GRASS-user] v.out.ogr to Mysql

Hi, I'am trying to export (v.out.ogr) some vectors to Mysql but I got the following problem: ERROR 1: MySQL error message:Duplicate entry '1' for key 'OGR_FID' For every vector it try to use the same OGR_FID and at the end It exports only the first vector becouse the other has duplicated

Re: [GRASS-user] v.out.ogr kml error

Take a look at http://grass.itc.it/grass64/manuals/html64_user/v.generalize.html it may help you --- Στις Παρ., 08/01/10, ο/η henry83 heam...@gmail.com έγραψε: Από: henry83 heam...@gmail.com Θέμα: Re: [GRASS-user] v.out.ogr kml error Προς: grass-user@lists.osgeo.org Ημερομηνία: Παρασκευή, 8

Re: [GRASS-user] v.out.ogr kml error

Thank you guys you have been quite helpful, there are a few things I would like to comment. First of all the first time I used v.out.ogr to export the generated contours to kml I did it over contours build up over an overgeoreferenced raster, what I mean is that I had a georeference bigger than

Re: [GRASS-user] v.out.ogr kml error

Something I'm thinking by now, what is the unit of the step parameter of the r.contour command, I need meters and I think the step is not in meters. Am I right? And how do I change the colour of the generated contours in the kml file? Thanks. henry83 wrote: Hi everyone! I have created a

Re: [GRASS-user] v.out.ogr kml error

henry83 wrote: Something I'm thinking by now, what is the unit of the step parameter of the r.contour command, I need meters and I think the step is not in meters. Am I right? it is in whatever units the raster's elevation data is in. Unless you've explicitly set units with r.support, the GIS

Re: [GRASS-user] v.out.ogr kml error

Try to export your data to shapefile and then use ogr2ogr to convert the shp to kml. --- Στις Πέμ., 07/01/10, ο/η henry83 heam...@gmail.com έγραψε: Από: henry83 heam...@gmail.com Θέμα: [GRASS-user] v.out.ogr kml error Προς: grass-user@lists.osgeo.org Ημερομηνία: Πέμπτη, 7 Ιανουάριος 2010, 2:06

Re: [GRASS-user] v.out.ogr kml error

Thank you Leonidas I will try to do it that way and hope it works, but before that I would like to get the contours as less dispersed polylines. As you can see in the image I have attached contours doesn't look as smoth lines as I would like, do you know how to improve this? Thank you.

Re: [GRASS-user] v.out.ogr kml error

henry83 wrote: I would like to get the contours as less dispersed polylines. As you can see in the image I have attached contours doesn't look as smoth lines as I would like, do you know how to improve this? Thank you. http://n2.nabble.com/file/n4269927/contours.png v.generalize Hamish

[GRASS-user] v.out.ogr kml error

Hi everyone! I have created a contour map from a SRTM elevation model, after filling nulls, filling depressions and creating the contour map I need to export it to kml. I have used the following command v.out.ogr input=srtm_contours dsn=/home/henry/srtm_contours.kml format=KML output:

[GRASS-user] v.out.ogr - missing attributes

Dear all, When exporting a polygon layer with v.out.ogr, specifically: v.out.ogr input=input type=boundary output All the attributes are null or zero, including the cat column. This doesn't happen if I use type=area. Could someone please tell me if this is normal? Is there a way to at least get

Re: [GRASS-user] v.out.ogr - missing attributes

William Temperley wrote: Dear all, When exporting a polygon layer with v.out.ogr, specifically: v.out.ogr input=input type=boundary output All the attributes are null or zero, including the cat column. This doesn't happen if I use type=area. Could someone please tell me if this is normal?

Re: [GRASS-user] v.out.ogr - missing attributes

2009/12/18 Markus Metz markus.metz.gisw...@googlemail.com: William Temperley wrote: Dear all, When exporting a polygon layer with v.out.ogr, specifically: v.out.ogr input=input type=boundary output All the attributes are null or zero, including the cat column. This doesn't happen if I

[GRASS-user] v.out.ogr kml does not add name field

Hi, I have a grass vector of provincial boundaries db.describe -c generalized_adminncols: 3 nrows: 415 Column 1: cat:INTEGER:11 Column 2: region:CHARACTER:15 Column 3: province:CHARACTER:50 Now, I exported the vector to KML polygon using the province attributes as the KML name element.

[GRASS-user] v.out.ogr on windows - the right path to dsn?

WinVista 32 Grass65-svn - self-compiled today nc-dataset self-compiled today in the osgeo4w-tree with gdal1.6? maybe a gdal-problem? checking whether to use GDAL... yes checking for gdal-config... /C/OSGeo4W/bin/gdal-config [...] GRASS is now configured for: i686-pc-mingw32 [...] GDAL

[GRASS-user] v.out.ogr on windows - the right path to dsn?

maybe a gdal-problem? maybe not, because r.out.gdal is working: r.out.gdal input=lsat5_1987...@landsat output=C:\wd\testlandsat.tif Exporting to GDAL data type: Byte r.out.gdal complete. helli __ GRATIS für alle WEB.DE-Nutzer:

[GRASS-user] v.out.ogr kml

Hello, when exporting from a projected system to KML, is a reprojection into WGS84 included? in the manual there is: v.out.ogr input=random3d_hull dsn=random3d_hull.kml format=KML \ type=face dsco=AltitudeMode=absolute Let's say I use the EPSG:2965 projection. in my works. Exporting to KML

Re: [GRASS-user] v.out.ogr kml

Hi:It seems that I have encountered the same problem,actually you should reproject your map by yourself if you are using a earlier version. In the later version it can reproject autoly. -- If I was wrong,I hope someone can modify it . 2009/6/23 Tim Michelsen

Re: [GRASS-user] v.out.ogr kml

maven apache wrote: Hi:It seems that I have encountered the same problem,actually you should reproject your map by yourself if you are using a earlier version.In the later version it can reproject autoly. i.e. a bug in GDAL/OGR got fixed so you need a newish version of that. you might

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

maven apache wrote: Thanks Micha for his help! Following his advise, I install the qgis,and the grass plugin and create new location(epsg4326),and reproj my vector map to this proj,then export it to kml successfully,however when add the kml to googlearth I found the layer doesnot match the

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

2009/6/22 Micha Silver mi...@arava.co.il maven apache wrote: Thanks Micha for his help! Following his advise, I install the qgis,and the grass plugin and create new location(epsg4326),and reproj my vector map to this proj,then export it to kml successfully,however when add the kml to

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

2009/6/22 Micha Silver mi...@arava.co.il maven apache wrote: I did have five vector layer each of which have only one categories,Actually I got the five vector from the commond v.extract..; Normally you would use d.vect.thematic if you have 5 categories in *one* vector map.

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

maven apache wrote: I am using 6.3,my tiff info: --- Coordinate System is: PROJCS[WGS 84 / UTM zone 20S, GEOGCS[WGS 84, DATUM[WGS_1984, SPHEROID[WGS 84,6378137,298.2572235630016, AUTHORITY[EPSG,7030]],

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

Thanks Micha for his help!Following his advise, I install the qgis,and the grass plugin and create new location(epsg4326),and reproj my vector map to this proj,then export it to kml successfully,however when add the kml to googlearth I found the layer doesnot match the tiff,the annex can give a

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

maven apache wrote: This is a vector layer transfered from a raster and its general info can be seen as follows: | | Projection: Universe Transverse Mercator (zone 0) |

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

On 19/06/09 04:40, maven apache wrote: This is a vector layer transfered from a raster and its general info can be seen as follows: ++ | Layer: sw...@permanent |

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

On 19/06/09 09:27, Moritz Lennert wrote: On 19/06/09 04:40, maven apache wrote: This is a vector layer transfered from a raster and its general info can be seen as follows: ++ | Layer: sw...@permanent

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

Moritz wrote: Sorry, just reread your message, and my answer is probably not really helpful. In fact v.out.ogr does transform your data to EPSG 4326, as the following message shows: Warning 1: Longitude 638073.992861 has been modified to fit into range [-180,180]. This warning will not

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

2009/6/19 Hamish hamis...@yahoo.com Moritz wrote: Sorry, just reread your message, and my answer is probably not really helpful. In fact v.out.ogr does transform your data to EPSG 4326, as the following message shows: Warning 1: Longitude 638073.992861 has been modified to fit into

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

On 19/06/09 10:57, Hamish wrote: Moritz wrote: Sorry, just reread your message, and my answer is probably not really helpful. In fact v.out.ogr does transform your data to EPSG 4326, as the following message shows: Warning 1: Longitude 638073.992861 has been modified to fit into range

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

maven wrote: I am trying to change the projection ,but have not successed.. create a new lat/lon WGS84 location with EPSG code # 4326, then pull in maps from source mapset using r.proj, v.proj. Hamish ___ grass-user mailing list

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

I have lose my heart so So many people have gave me help,...I can not do it. 2009/6/19 Hamish hamis...@yahoo.com maven wrote: I am trying to change the projection ,but have not successed.. create a new lat/lon WGS84 location with EPSG code # 4326, then pull in maps from

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

I am using 6.3,my tiff info:--- Coordinate System is: PROJCS[WGS 84 / UTM zone 20S, GEOGCS[WGS 84, DATUM[WGS_1984, SPHEROID[WGS 84,6378137,298.2572235630016, AUTHORITY[EPSG,7030]], AUTHORITY[EPSG,6326]],

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

maven wrote: First I create location :g.proj -c georef=d:/swilAlphaTIFF.tif datumtrans=0 location=newlocationthen import it to the new location: get four raster maps(it has three band),I composite them and then transfer the composted raster to vector,then extract each category to a

Re: [GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

2009/6/19 Hamish hamis...@yahoo.com maven wrote: First I create location :g.proj -c georef=d:/swilAlphaTIFF.tif datumtrans=0 location=newlocationthen import it to the new location: get four raster maps(it has three band),I composite them and then transfer the composted raster to

[GRASS-user] v.out.ogr to KML ERROR 1: Latitude is invalide

This is a vector layer transfered from a raster and its general info can be seen as follows: ++ | Layer: sw...@permanent | Mapset: PERMANENT | Location:newlocation | Database:

Re: [GRASS-user] v.out.ogr

Thanks Tom and Alex! it works mow! silvia On Sep 10, 2008, at 10:54 PM, Tom Russo wrote: On Wed, Sep 10, 2008 at 10:42:12PM +0200, we recorded a bogon- computron collision of the [EMAIL PROTECTED] flavor, containing: Hi grass users, i'm trying to export a grass vector and generate a

[GRASS-user] v.out.ogr

Hi grass users, i'm trying to export a grass vector and generate a shapefile using v.out.ogr. the vector contains 4 points and 6 boundaries each has its own centroids. the output shapefile contains 4 objects out of 10. WHY? How can I get all the objects? (i created the vector using

Re: [GRASS-user] v.out.ogr

Silvia Simoni wrote: Hi grass users, i'm trying to export a grass vector and generate a shapefile using v.out.ogr. the vector contains 4 points and 6 boundaries each has its own centroids. the output shapefile contains 4 objects out of 10. WHY? How can I get all the objects? (i created

Re: [GRASS-user] v.out.ogr

On Wed, Sep 10, 2008 at 10:42:12PM +0200, we recorded a bogon-computron collision of the [EMAIL PROTECTED] flavor, containing: Hi grass users, i'm trying to export a grass vector and generate a shapefile using v.out.ogr. the vector contains 4 points and 6 boundaries each has its own

Re: [GRASS-user] v.out.ogr multiple

On 08/07/08 22:33, Gabriele N. wrote: Hello. I want to create a script bash (GUI) to export many vector in shapefile having the opportunity to decide which export layer (0, 1, 2) and type=line,area ecc.. Does this mean interactive decision layer by layer, or that the module should allow for

Re: [GRASS-user] v.out.ogr multiple

On 09/07/08 10:42, Gabriele N. wrote: Hi Moritz. Moritz Lennert-2 wrote: On 08/07/08 22:33, Gabriele N. wrote: Hello. I want to create a script bash (GUI) to export many vector in shapefile having the opportunity to decide which export layer (0, 1, 2) and type=line,area ecc.. Does this mean

Re: [GRASS-user] v.out.ogr multiple

Thanks Moritz. I have made some improvements. I give you an example and the new script. Now I export all vectors with name that starts with foglio_1 But I do not know how to select a folder where to export the shapes. Now, only works if I enter the path by hand or select from a graphical user

[GRASS-user] v.out.ogr multiple

Hello. I want to create a script bash (GUI) to export many vector in shapefile having the opportunity to decide which export layer (0, 1, 2) and type=line,area ecc.. I would also like to know if you can use the characters as' * 'to be able to export all instance vector starting with' nome_vector