Re: [gdal-dev] Motion: Migrate gdal.org to ReadTheDocs

+1 ;-) Martin Howard Butler via gdal-dev wrote: > All, > > I would like to motion to migrate gdal.org from our > self-managed GitHub Pages infrastructure to ReadTheDocs. You can read > specific details about the migration in the ticket at >

Re: [gdal-dev] Support for VPF (vector product format) files with OGDI

On Sun, Jan 22, 2012 at 01:32:04PM -0700, Billy Newman wrote: 1. What command did you use to covert the vmap files to shapefiles, ogrinfo or ogdi_info? And can you give me a quick example to make sure I am doing it correctly.

Re: [gdal-dev] Support for VPF (vector product format) files with OGDI

Martin Spott wrote: Yes, I ran ogrinfo on all available features via some obscure, very long Bash command. Something like this: martin@sphere:~$ for VMAP_URL in v0eur_5/vmaplv0/eurnasia v0noa_5/vmaplv0/noamer v0sas_5/vmaplv0/sasaus v0soa_5/vmaplv0/soamafr; do /opt/GRASS.32/bin/ogrinfo

Re: [gdal-dev] Support for VPF (vector product format) files with OGDI

Billy Newman wrote: I compiled on Redhat EL version 5.6 64 bit, gcc 4.2.x Last time I tried direct access to VMap0 I reverted back to a 32 bit platform from my 64 bit setup (both Linux Debian). I don't remember the exact reason but your message sounds somewhat familiar. The first thing I did

Re: [gdal-dev] VPF support

Even Rouault wrote: So perhaps the issue you saw was specifically a 64bit issue. Indeed, this appears to be obvious. BTW, just to make sure we're talking about the same symptoms: May I assume that the voids as shown in this shot: http://foxtrot.mgras.net/bitmap/VMap0-voids.png

Re: [gdal-dev] VPF support

Sommer, Martin wrote: current OGDI sources (betas) need a bit of tweaking, if you want it to build yourself. Version 3.1.5 is far way better to build. It's just an imprecise annotation, yet I'd like to share my findings with you that the simple joy of getting an OGDI library built without