RE: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Kyle Shannon 
I looked in 2.1, the spec is the same, google was just being lenient on parsing.

From: gdal-dev-boun...@lists.osgeo.org 
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Roland Duhaime
Sent: Friday, November 18, 2011 2:24 PM
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

No, but that would be nice if it did. - Roland
On Fri, Nov 18, 2011 at 3:22 PM, Roger André 
mailto:ran...@gmail.com>> wrote:
If you change the namespace declaration in the KML from "2.2" to "2.1", does it 
still work?


On Fri, Nov 18, 2011 at 11:17 AM, Even Rouault 
mailto:even.roua...@mines-paris.org>> wrote:
Le vendredi 18 novembre 2011 20:12:27, Kyle Shannon a écrit :
> Thanks Even, I have a patch, but I can't test it here.  It is probably
> faster and easier for you anyway.  Thanks again.
Filed and fixes commited : http://trac.osgeo.org/gdal/ticket/4347#comment:1
___
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

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

Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Roland Duhaime 
No, but that would be nice if it did. - Roland

On Fri, Nov 18, 2011 at 3:22 PM, Roger André  wrote:

> If you change the namespace declaration in the KML from "2.2" to "2.1",
> does it still work?
>
>
>
> On Fri, Nov 18, 2011 at 11:17 AM, Even Rouault <
> even.roua...@mines-paris.org> wrote:
>
>> Le vendredi 18 novembre 2011 20:12:27, Kyle Shannon a écrit :
>> > Thanks Even, I have a patch, but I can't test it here.  It is probably
>> > faster and easier for you anyway.  Thanks again.
>>
>> Filed and fixes commited :
>> http://trac.osgeo.org/gdal/ticket/4347#comment:1
>> ___
>> 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
>
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Re: Problem joining a shapefile and MDB

2011-11-18 Thread Brent Fraser 

A response from the mapserver list:

http://forums.devarticles.com/microsoft-sql-server-5/data-source-name-not-found-and-no-default-driver-specified-8346.html

When you use a 64bits Windows, ODBC manager at Control Panel will only
create 64bits connection.
I had problems with that in the past and had to force 32bits
connections using 32bits ODBC manager at
C:\Windows\SysWOW64\odbcad32.exe


Best Regards,
Brent Fraser


On 11/18/2011 2:00 PM, boesiii wrote:

Even,

What is the correct procedure to upgrade a MS4W installation?  I downloaded
release-1310-gdal-1-8-1-mapserver-6-0-1.zip and I copied OGRINFO.EXE to the
current location.  After I did this OGRINFO still crashed.  Do I need to
copy other files?

Thanks,

Ed

--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/Problem-joining-a-shapefile-and-MDB-tp7009404p7009680.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



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

Re: [gdal-dev] Re: OGR Driver for Norwegian SOSI standard

2011-11-18 Thread Mateusz Łoskot 
On 17 November 2011 21:31, Frank Warmerdam  wrote:
>  o RFC 8 on coding guidelines and such is *not* adopted and
>    in any event it would be advisory and I would not try to apply
>    it to essentially external code.

I assumed the issue is with driver code, which is proposed to be
included in GDAL.

>  o Code with names and comments in Norwegian, or any
>    non-English language is going to be harder to support.

That's what I meant.

>    If it just works this might not matter, and if there is a developer
>    who does understand it who is willing to support it that is great.

...people come and go, but code stays.

>    I would not be inclined to exclude code just because the
>    comments and variables are in a different language  -
>    particularly in a driver where expectations are often more relaxed
>    than in the core.

Understood.

> From my perspective, I'm inclined to take a fairly relaxed
> view of code standards and other requirements on driver
> code.

Thanks for clarification

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Re: Problem joining a shapefile and MDB

2011-11-18 Thread Even Rouault 
Le vendredi 18 novembre 2011 22:00:55, boesiii a écrit :
> Even,
> 
> What is the correct procedure to upgrade a MS4W installation?  I downloaded
> release-1310-gdal-1-8-1-mapserver-6-0-1.zip and I copied OGRINFO.EXE to the
> current location.  After I did this OGRINFO still crashed.  Do I need to
> copy other files?

I'm not sure you can mix stuff like that. You should ask for confirmation from 
the MS4W packagers, but perhaps they have already an updated version of MS4W 
with GDAL 1.8.1

> 
> Thanks,
> 
> Ed
> 
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/Problem-joining-a-shapefile-and-MDB
> -tp7009404p7009680.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
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

[gdal-dev] Re: Problem joining a shapefile and MDB

2011-11-18 Thread boesiii 
Even,

What is the correct procedure to upgrade a MS4W installation?  I downloaded
release-1310-gdal-1-8-1-mapserver-6-0-1.zip and I copied OGRINFO.EXE to the
current location.  After I did this OGRINFO still crashed.  Do I need to
copy other files?

Thanks,

Ed

--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/Problem-joining-a-shapefile-and-MDB-tp7009404p7009680.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] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Roger André 
If you change the namespace declaration in the KML from "2.2" to "2.1",
does it still work?



On Fri, Nov 18, 2011 at 11:17 AM, Even Rouault  wrote:

> Le vendredi 18 novembre 2011 20:12:27, Kyle Shannon a écrit :
> > Thanks Even, I have a patch, but I can't test it here.  It is probably
> > faster and easier for you anyway.  Thanks again.
>
> Filed and fixes commited :
> http://trac.osgeo.org/gdal/ticket/4347#comment:1
> ___
> 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] Problem joining a shapefile and MDB

2011-11-18 Thread Even Rouault 
Le vendredi 18 novembre 2011 20:14:42, boesiii a écrit :
> I am trying to join a shapefile and MDB using the following command:
> 
> ogrinfo -sql  "SELECT * FROM PLOTS LEFT JOIN
> 'ODBC:geoplan,County_Taxid_Parcels'.County_Taxid_Parcels ON
> PLOTS.SHRT_TXID=County_Taxid_Parcels.SHRT_TXID"
> D:\ms4w\apps\ftmagisapp_v2\maps\background\PLOTS.shp
> 
> The ogrinfo command says it opens the shapefile but then it immediately
> crashes.
> 
> What could be causing it to crash?
> 
> I ultimately will be using this inside a MapServer map file to display
> owner names from the MDB.

You didn't mention which GDAL version you are using. But if it is 1.8.0, then 
you probably have hit http://trac.osgeo.org/gdal/ticket/4112 that has been 
fixed in 1.8.1

> 
> Thanks.
> 
> 
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/Problem-joining-a-shapefile-and-MDB
> -tp7009404p7009404.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
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Even Rouault 
Le vendredi 18 novembre 2011 20:12:27, Kyle Shannon a écrit :
> Thanks Even, I have a patch, but I can't test it here.  It is probably
> faster and easier for you anyway.  Thanks again.

Filed and fixes commited : http://trac.osgeo.org/gdal/ticket/4347#comment:1
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

[gdal-dev] Problem joining a shapefile and MDB

2011-11-18 Thread boesiii 
I am trying to join a shapefile and MDB using the following command:

ogrinfo -sql  "SELECT * FROM PLOTS LEFT JOIN
'ODBC:geoplan,County_Taxid_Parcels'.County_Taxid_Parcels ON
PLOTS.SHRT_TXID=County_Taxid_Parcels.SHRT_TXID" 
D:\ms4w\apps\ftmagisapp_v2\maps\background\PLOTS.shp

The ogrinfo command says it opens the shapefile but then it immediately
crashes.

What could be causing it to crash?

I ultimately will be using this inside a MapServer map file to display owner
names from the MDB.

Thanks.


--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/Problem-joining-a-shapefile-and-MDB-tp7009404p7009404.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] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Kyle Shannon 
Thanks Even, I have a patch, but I can't test it here.  It is probably faster 
and easier for you anyway.  Thanks again.

kss


-Original Message-
From: Even Rouault [mailto:even.roua...@mines-paris.org] 
Sent: Friday, November 18, 2011 12:11 PM
To: gdal-dev@lists.osgeo.org
Cc: Kyle Shannon
Subject: Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

Le vendredi 18 novembre 2011 20:04:13, Kyle Shannon a écrit :
> I doubt they will change the spec, and I am sure you are right about 
> the many bad files.  I imagine that most people just checked the 
> output from his or her program in google earth and said "Good enough".  
> If no one gets around to it before I get off work and to a *nix 
> workstation, I will file a ticket and a patch.  It is probably safe to 
> backport to 1.8 as well.
> 
I was just looking at this. I'll notify you of the ticket when done. Testing 
will be welcome because I have a much older GE version.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Even Rouault 
Le vendredi 18 novembre 2011 20:04:13, Kyle Shannon a écrit :
> I doubt they will change the spec, and I am sure you are right about the
> many bad files.  I imagine that most people just checked the output from
> his or her program in google earth and said "Good enough".  If no one gets
> around to it before I get off work and to a *nix workstation, I will file
> a ticket and a patch.  It is probably safe to backport to 1.8 as well.
> 
I was just looking at this. I'll notify you of the ticket when done. Testing 
will be welcome because I have a much older GE version.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

RE: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Kyle Shannon 
I doubt they will change the spec, and I am sure you are right about the many 
bad files.  I imagine that most people just checked the output from his or her 
program in google earth and said "Good enough".  If no one gets around to it 
before I get off work and to a *nix workstation, I will file a ticket and a 
patch.  It is probably safe to backport to 1.8 as well.

From: gdal-dev-boun...@lists.osgeo.org 
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Roland Duhaime
Sent: Friday, November 18, 2011 9:59 AM
To: gdal-dev@lists.osgeo.org"
Subject: Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

Kyle,

Yes, I just removed the spaces after the commas in the  tag and 
was then able to open one of the kml files in G.E.  I suspect that there are 
m(b)illions? of kmz files in cyberspace that won't meet the 2.2 standard 
because of this.  I am not sure of the most effective solution.  In addition to 
documentation, perhaps we need a conversion tool for legacy 2.1 kml 
superoverlays.  Perhaps getting the 2.2 KML standard to lighten-up a tad would 
be complicated.

Thanks Again,
Roland

On Fri, Nov 18, 2011 at 11:14 AM, Kyle Shannon 
mailto:kshan...@gcs-research.com>> wrote:
Possible issue with output (from 
http://earth.google.com/support/bin/answer.py?answer=40901):

To conform more closely with the OGC KML 2.2 standard, we've made the parsing 
of the  tag more strict in version 6.1. Spaces must only be used 
to separate the (longitude,latitude,altitude) triplets which specify the 
coordinates of a single point. It is invalid to add spaces between individual 
coordinates. We understand that previous versions of the client were more 
lenient, so if your KML files contain spaces beween coordinates in coordinate 
triplets, an easy workaround is to remove all whitespace located immediately 
before or after commas inside a  tag.

I checked one file, and there were spaces after the commas:

http://earth.google.com/kml/2.1"; 
xmlns:gx="http://www.google.com/kml/ext/2.2";>
 
   1/1/1.kml
   

 checkHideChildren

   
   

 128
 2048


 41.900791
 41.890160
 12.505676
 12.492253

   
   
1

 1.jpg


 
   12.492253, 41.890160, 0
   12.506078, 41.890461, 0
   12.505676, 41.900791, 0
   12.491848, 41.900490, 0
 

   
...

Seems like a quick fix.  Someone should probably file a ticket for 
documentation, I can do that if need be.

kss

From: gdal-dev-boun...@lists.osgeo.org 
[mailto:gdal-dev-boun...@lists.osgeo.org]
 On Behalf Of Roland Duhaime
Sent: Friday, November 18, 2011 7:14 AM
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

Roger,

The PNG gdalinfo details are:

Driver: PNG/Portable Network Graphics
Files: 7.png
Size is 218, 218
Coordinate System is `'
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (0.0,0.0)
Lower Left  (0.0,  218.0)
Upper Right (  218.0,0.0)
Lower Right (  218.0,  218.0)
Center  (  109.0,  109.0)
Band 1 Block=218x1 Type=Byte, ColorInterp=Red
  Mask Flags: PER_DATASET ALPHA
Band 2 Block=218x1 Type=Byte, ColorInterp=Green
  Mask Flags: PER_DATASET ALPHA
Band 3 Block=218x1 Type=Byte, ColorInterp=Blue
  Mask Flags: PER_DATASET ALPHA
Band 4 Block=218x1 Type=Byte, ColorInterp=Alpha

Thanks,
Roland


On Thu, Nov 17, 2011 at 5:21 PM, Roger André 
mailto:ran...@gmail.com>> wrote:
What is the output of gdalinfo on one of the PNG's in the superoverlay?


On Thu, Nov 17, 2011 at 1:36 PM, Roland Duhaime 
mailto:roland.duha...@gmail.com>> wrote:

Has anyone else experienced the latest version of Google Earth (6.1.0.5001) or 
the G.E. API not loading PNG formatted KMLSUPEROVERLAYs created using 
gdal_translate?  The same KMZ files worked in the past.

Thanks,
Roland


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



This email message is for the sole use of the intended recipient(s) and may 
contain confidential and privileged information. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and delete the original 
message.   ­­

__

Re: [gdal-dev] VSI issue

2011-11-18 Thread Even Rouault 
Le vendredi 18 novembre 2011 15:04:55, Ari Jolma a écrit :
> Hi,
> 
> A few days ago on this list I mentioned that the following works using a
> recent version from trunk (and Perl bindings):
> 
> use Geo::GDAL;
> $datasource = Geo::OGR::Open('/home/ajolma/data/parks.shp');
> Geo::OGR::Driver('GML')->Copy($datasource, '/dev/stdout');
> 
> I'm testing a simple WFS written in Perl and basically the above is the
> contents of the GetFeature subroutine (the datasource name comes of
> course from a configuration file). However, using this in a Perl CGI
> program leads to "RuntimeError Failed to create GML file /dev/stdout." -
> it seems like the VSI does not work when the Perl program is run as a
> CGI program. I may investigate the issue more but maybe somebody has an
> answer right away. - I can forward the output to a file and then send
> the file but it would be nice to feed it directly to the client.

The most obvious idea I have is that something closes the stdout of the forked 
CGI ?

> 
> Regards,
> 
> 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] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Roland Duhaime 
Kyle,

Yes, I just removed the spaces after the commas in the  tag
and was then able to open one of the kml files in G.E.  I suspect that
there are m(b)illions? of kmz files in cyberspace that won't meet the 2.2
standard because of this.  I am not sure of the most effective solution.
 In addition to documentation, perhaps we need a conversion tool for legacy
2.1 kml superoverlays.  Perhaps getting the 2.2 KML standard to lighten-up
a tad would be complicated.

Thanks Again,
Roland


On Fri, Nov 18, 2011 at 11:14 AM, Kyle Shannon wrote:

>  Possible issue with output (from
> http://earth.google.com/support/bin/answer.py?answer=40901):
>
> ** **
>
> *To conform more closely with the OGC KML 2.2 standard, we've made the
> parsing of the  tag more strict in version 6.1. Spaces must
> only be used to separate the (longitude,latitude,altitude) triplets which
> specify the coordinates of a single point. It is invalid to add spaces
> between individual coordinates. We understand that previous versions of the
> client were more lenient, so if your KML files contain spaces beween
> coordinates in coordinate triplets, an easy workaround is to remove all
> whitespace located immediately before or after commas inside a
>  tag.*
>
> * *
>
> I checked one file, and there were spaces after the commas:
>
> ** **
>
> http://earth.google.com/kml/2.1"; xmlns:gx="
> http://www.google.com/kml/ext/2.2";>
>
>  
>
>1/1/1.kml
>
>
>
> 
>
>  checkHideChildren
>
> 
>
>
>
>
>
> 
>
>  128
>
>  2048
>
> 
>
> 
>
>  41.900791
>
>  41.890160
>
>  12.505676
>
>  12.492253
>
> 
>
>
>
>
>
> 1
>
> 
>
>  1.jpg
>
> 
>
> 
>
>  
>
>12.492253, 41.890160, 0
>
>12.506078, 41.890461, 0
>
>12.505676, 41.900791, 0
>
>12.491848, 41.900490, 0
>
>  
>
> 
>
>
>
> ...
>
> ** **
>
> Seems like a quick fix.  Someone should probably file a ticket for
> documentation, I can do that if need be.
>
> ** **
>
> kss
>
> ** **
>
> *From:* gdal-dev-boun...@lists.osgeo.org [mailto:
> gdal-dev-boun...@lists.osgeo.org] *On Behalf Of *Roland Duhaime
> *Sent:* Friday, November 18, 2011 7:14 AM
> *To:* gdal-dev@lists.osgeo.org
> *Subject:* Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001
>
> ** **
>
> Roger,
>
> ** **
>
> The PNG gdalinfo details are:
>
> ** **
>
> Driver: PNG/Portable Network Graphics
>
> Files: 7.png
>
> Size is 218, 218
>
> Coordinate System is `'
>
> Image Structure Metadata:
>
>   INTERLEAVE=PIXEL
>
> Corner Coordinates:
>
> Upper Left  (0.0,0.0)
>
> Lower Left  (0.0,  218.0)
>
> Upper Right (  218.0,0.0)
>
> Lower Right (  218.0,  218.0)
>
> Center  (  109.0,  109.0)
>
> Band 1 Block=218x1 Type=Byte, ColorInterp=Red
>
>   Mask Flags: PER_DATASET ALPHA
>
> Band 2 Block=218x1 Type=Byte, ColorInterp=Green
>
>   Mask Flags: PER_DATASET ALPHA
>
> Band 3 Block=218x1 Type=Byte, ColorInterp=Blue
>
>   Mask Flags: PER_DATASET ALPHA
>
> Band 4 Block=218x1 Type=Byte, ColorInterp=Alpha
>
> ** **
>
> Thanks,
>
> Roland
>
> ** **
>
> ** **
>
> On Thu, Nov 17, 2011 at 5:21 PM, Roger André  wrote:
>
> What is the output of gdalinfo on one of the PNG's in the superoverlay?***
> *
>
> ** **
>
> ** **
>
> On Thu, Nov 17, 2011 at 1:36 PM, Roland Duhaime 
> wrote:
>
>  ** **
>
> Has anyone else experienced the latest version of Google Earth
> (6.1.0.5001) or the G.E. API not loading PNG formatted KMLSUPEROVERLAYs
> created using gdal_translate?  The same KMZ files worked in the past.
>
> ** **
>
> Thanks,
>
> Roland
>
> ** **
>
> ** **
>
> ___
> gdal-dev mailing list
> gdal-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
>  ** **
>
> ** **
>
> This email message is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply email and delete the
> original message.   ­­
>
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo

RE: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Kyle Shannon 
Strange that turning on "Tools->Options->General->KML Error Handling->Show 
prompts for all errors" doesn't report anything.

From: gdal-dev-boun...@lists.osgeo.org 
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Kyle Shannon
Sent: Friday, November 18, 2011 9:14 AM
To: Roland Duhaime; gdal-dev@lists.osgeo.org
Subject: RE: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

Possible issue with output (from 
http://earth.google.com/support/bin/answer.py?answer=40901):

To conform more closely with the OGC KML 2.2 standard, we've made the parsing 
of the  tag more strict in version 6.1. Spaces must only be used 
to separate the (longitude,latitude,altitude) triplets which specify the 
coordinates of a single point. It is invalid to add spaces between individual 
coordinates. We understand that previous versions of the client were more 
lenient, so if your KML files contain spaces beween coordinates in coordinate 
triplets, an easy workaround is to remove all whitespace located immediately 
before or after commas inside a  tag.

I checked one file, and there were spaces after the commas:

http://earth.google.com/kml/2.1"; 
xmlns:gx="http://www.google.com/kml/ext/2.2";>
 
   1/1/1.kml
   

 checkHideChildren

   
   

 128
 2048


 41.900791
 41.890160
 12.505676
 12.492253

   
   
1

 1.jpg


 
   12.492253, 41.890160, 0
   12.506078, 41.890461, 0
   12.505676, 41.900791, 0
   12.491848, 41.900490, 0
 

   
...

Seems like a quick fix.  Someone should probably file a ticket for 
documentation, I can do that if need be.

kss

From: gdal-dev-boun...@lists.osgeo.org 
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Roland Duhaime
Sent: Friday, November 18, 2011 7:14 AM
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

Roger,

The PNG gdalinfo details are:

Driver: PNG/Portable Network Graphics
Files: 7.png
Size is 218, 218
Coordinate System is `'
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (0.0,0.0)
Lower Left  (0.0,  218.0)
Upper Right (  218.0,0.0)
Lower Right (  218.0,  218.0)
Center  (  109.0,  109.0)
Band 1 Block=218x1 Type=Byte, ColorInterp=Red
  Mask Flags: PER_DATASET ALPHA
Band 2 Block=218x1 Type=Byte, ColorInterp=Green
  Mask Flags: PER_DATASET ALPHA
Band 3 Block=218x1 Type=Byte, ColorInterp=Blue
  Mask Flags: PER_DATASET ALPHA
Band 4 Block=218x1 Type=Byte, ColorInterp=Alpha

Thanks,
Roland


On Thu, Nov 17, 2011 at 5:21 PM, Roger André 
mailto:ran...@gmail.com>> wrote:
What is the output of gdalinfo on one of the PNG's in the superoverlay?


On Thu, Nov 17, 2011 at 1:36 PM, Roland Duhaime 
mailto:roland.duha...@gmail.com>> wrote:

Has anyone else experienced the latest version of Google Earth (6.1.0.5001) or 
the G.E. API not loading PNG formatted KMLSUPEROVERLAYs created using 
gdal_translate?  The same KMZ files worked in the past.

Thanks,
Roland


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



This email message is for the sole use of the intended recipient(s) and may 
contain confidential and privileged information. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and delete the original 
message.   ­­
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

RE: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Kyle Shannon 
Possible issue with output (from 
http://earth.google.com/support/bin/answer.py?answer=40901):

To conform more closely with the OGC KML 2.2 standard, we've made the parsing 
of the  tag more strict in version 6.1. Spaces must only be used 
to separate the (longitude,latitude,altitude) triplets which specify the 
coordinates of a single point. It is invalid to add spaces between individual 
coordinates. We understand that previous versions of the client were more 
lenient, so if your KML files contain spaces beween coordinates in coordinate 
triplets, an easy workaround is to remove all whitespace located immediately 
before or after commas inside a  tag.

I checked one file, and there were spaces after the commas:

http://earth.google.com/kml/2.1"; 
xmlns:gx="http://www.google.com/kml/ext/2.2";>
 
   1/1/1.kml
   

 checkHideChildren

   
   

 128
 2048


 41.900791
 41.890160
 12.505676
 12.492253

   
   
1

 1.jpg


 
   12.492253, 41.890160, 0
   12.506078, 41.890461, 0
   12.505676, 41.900791, 0
   12.491848, 41.900490, 0
 

   
...

Seems like a quick fix.  Someone should probably file a ticket for 
documentation, I can do that if need be.

kss

From: gdal-dev-boun...@lists.osgeo.org 
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Roland Duhaime
Sent: Friday, November 18, 2011 7:14 AM
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

Roger,

The PNG gdalinfo details are:

Driver: PNG/Portable Network Graphics
Files: 7.png
Size is 218, 218
Coordinate System is `'
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (0.0,0.0)
Lower Left  (0.0,  218.0)
Upper Right (  218.0,0.0)
Lower Right (  218.0,  218.0)
Center  (  109.0,  109.0)
Band 1 Block=218x1 Type=Byte, ColorInterp=Red
  Mask Flags: PER_DATASET ALPHA
Band 2 Block=218x1 Type=Byte, ColorInterp=Green
  Mask Flags: PER_DATASET ALPHA
Band 3 Block=218x1 Type=Byte, ColorInterp=Blue
  Mask Flags: PER_DATASET ALPHA
Band 4 Block=218x1 Type=Byte, ColorInterp=Alpha

Thanks,
Roland


On Thu, Nov 17, 2011 at 5:21 PM, Roger André 
mailto:ran...@gmail.com>> wrote:
What is the output of gdalinfo on one of the PNG's in the superoverlay?


On Thu, Nov 17, 2011 at 1:36 PM, Roland Duhaime 
mailto:roland.duha...@gmail.com>> wrote:

Has anyone else experienced the latest version of Google Earth (6.1.0.5001) or 
the G.E. API not loading PNG formatted KMLSUPEROVERLAYs created using 
gdal_translate?  The same KMZ files worked in the past.

Thanks,
Roland


___
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] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Roland Duhaime 
Roger,

The PNG gdalinfo details are:

Driver: PNG/Portable Network Graphics
Files: 7.png
Size is 218, 218
Coordinate System is `'
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (0.0,0.0)
Lower Left  (0.0,  218.0)
Upper Right (  218.0,0.0)
Lower Right (  218.0,  218.0)
Center  (  109.0,  109.0)
Band 1 Block=218x1 Type=Byte, ColorInterp=Red
  Mask Flags: PER_DATASET ALPHA
Band 2 Block=218x1 Type=Byte, ColorInterp=Green
  Mask Flags: PER_DATASET ALPHA
Band 3 Block=218x1 Type=Byte, ColorInterp=Blue
  Mask Flags: PER_DATASET ALPHA
Band 4 Block=218x1 Type=Byte, ColorInterp=Alpha

Thanks,
Roland


On Thu, Nov 17, 2011 at 5:21 PM, Roger André  wrote:

> What is the output of gdalinfo on one of the PNG's in the superoverlay?
>
>
>
> On Thu, Nov 17, 2011 at 1:36 PM, Roland Duhaime 
> wrote:
>
>>
>> Has anyone else experienced the latest version of Google Earth
>> (6.1.0.5001) or the G.E. API not loading PNG formatted KMLSUPEROVERLAYs
>> created using gdal_translate?  The same KMZ files worked in the past.
>>
>> Thanks,
>> Roland
>>
>>
>> ___
>> 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

[gdal-dev] VSI issue

2011-11-18 Thread Ari Jolma 

Hi,

A few days ago on this list I mentioned that the following works using a 
recent version from trunk (and Perl bindings):


use Geo::GDAL;
$datasource = Geo::OGR::Open('/home/ajolma/data/parks.shp');
Geo::OGR::Driver('GML')->Copy($datasource, '/dev/stdout');

I'm testing a simple WFS written in Perl and basically the above is the 
contents of the GetFeature subroutine (the datasource name comes of 
course from a configuration file). However, using this in a Perl CGI 
program leads to "RuntimeError Failed to create GML file /dev/stdout." - 
it seems like the VSI does not work when the Perl program is run as a 
CGI program. I may investigate the issue more but maybe somebody has an 
answer right away. - I can forward the output to a file and then send 
the file but it would be nice to feed it directly to the client.


Regards,

Ari

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

Re: [gdal-dev] KMLSuperOverlay in Google Earth 6.1.0.5001

2011-11-18 Thread Vincent Schut 

On 11/17/2011 10:36 PM, Roland Duhaime wrote:


Has anyone else experienced the latest version of Google Earth 
(6.1.0.5001) or the G.E. API not loading PNG formatted 
KMLSUPEROVERLAYs created using gdal_translate?  The same KMZ files 
worked in the past.

Yes, I can confirm this.

Vincent.


Thanks,
Roland



___
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

[gdal-dev] Re: OGR Driver for Norwegian SOSI standard

2011-11-18 Thread relet 
Thank you all for your comments --

Even:
* I think the build system is easy to do. The library does not have any
significant external dependencies so wrapping it into a circle of auto* was
not my top priority.
* I would of course be available to maintain the synchronization. If the
library/driver would be co-hosted with gdal, I would not use the bitbucket
as ticket system. In that case, sync will happen between the ogr/public
version as public code (portability, interfacing, bug fixes) and internal
development (updates wrt newer versions of the SOSI standard). It remains to
see which side is "upstream".  

Mateusz: 
* I understand your concern. I'm not a native speaker of Norwegian myself.
Translation however would break the sync, even if I had the resources to do
it. 
* I am also a bit worried about the public version of the driver being
neglected in a few years if it does not manage to create an user base to
create pressure on the authorities who should be publishing it. ;)

Frank:
* Fyba is a 500KB standalone binary from a gcc build, or roughly 30K lines
including extensive comment blocks on every method. Sorting out the most
common commenter ids gets me to 15K lines.
* Depending on your perspective, SOSI may be a niche format, but it is also
a national standard used by most geospatial actors of an European country on
a daily basis. They just haven't got to see it integrated in their open
source utilities.

So much for my arguments. ;) I'll leave the decision to you.
I'll be happy to provide the support I can provide to either a standalone or
an integrated library. 

--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/OGR-Driver-for-Norwegian-SOSI-standard-tp5282431p7007514.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