[Gvsig_english] Problems with EPSG.21781

[FANGER Lorenz]

Thanks again for the inputs

Sorry I can't provide access to the Postgis-Datas as the server sits behind a firewall. If you like I can provide some file based version you can upload to the own server.

However the input with the Integerfield helped me further. gvSIG obviously does not accept integer (int[4]) and longinteger (int[8]) field types of gid field. It works with smallint (int[2]) and i also tested successfully with some other field types like varchar, numeric etc... As int[4] and [8] are likely to be field types for gid fields this seems to me like a bug, which should be solved.

How ever. EPSG:21781 remains not nativly supported by gvSIG 1.9 (build 1250). The hack with the user CRS is the only way I could handle  that issue. Would be nice if that issue could be solved on the code level as Antonio has suggested. With that I look forward to introduce gvSIG in our company for common gis-user.

Freundliche Grüsse
Lorenz Fanger

 

> -----Ursprüngliche Nachricht-----
> Von: gvsig_internacional-bounces at listserv.gva.es 
> [mailto:gvsig_internacional-bounces at listserv.gva.es] Im 
> Auftrag von Francisco José Peñarrubia
> Gesendet: Donnerstag, 12. November 2009 11:20
> An: Users and Developers mailing list
> Betreff: Re: [Gvsig_english] Problems with EPSG.21781
> 
> Hi Lorenz.
> 
> I think this is a different problem. The gvSIG driver is not 
> reprojecting, so, I think the problem is not related with the 
> kind of projection.
> I guess there is a problem with an Integer field in your 
> table. Try to select only the geometry field for your layer 
> in order to isolate the problem.
> 
> To be sure about this problem, we need to connect to your 
> data. Is it possible to do so? If yes, you can use my private 
> mail, don't send the parameters to the whole list.
> 
> Cheers.
> 
> Fran Peñarrubia
> www.scolab.es
> 
> FANGER Lorenz escribió:
> > Hi List
> >
> > Thanks for the answers. 
> >
> > Well the hack with the user CRS works fine for shapes and 
> wms but not for postgis-datas. With postgis-datas the 
> following error was thrown in the information console:
> >
> > null 
> > java.nio.BufferUnderflowException: null     
> > java.nio.Buffer.nextGetIndex(Unknown Source)     
> > java.nio.HeapByteBuffer.getInt(Unknown Source
> > 
> com.iver.cit.gvsig.fmap.drivers.jdbc.postgis.PostGisDriver.getFieldVal
> > ue(PostGisDriver.java:466)
> > 
> com.iver.cit.gvsig.fmap.drivers.jdbc.postgis.PostGisFeatureIte
> rator.next(PostGisFeatureIterator.java:171
> > 
> com.iver.cit.gvsig.fmap.drivers.featureiterators.ReprojectWrap
> perFeatureIterator.next(ReprojectWrapperFeatureIterator.java:9
> 2) 
> com.iver.cit.gvsig.fmap.layers.FLyrVect._draw(FLyrVect.java:43
> 7)     
> com.iver.cit.gvsig.fmap.layers.FLyrVect.draw(FLyrVect.java:631
> ) 
> com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMa
> pContextDrawer.java:209) 
> com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMa
> pContextDrawer.java:175) 
> com.iver.cit.gvsig.fmap.MapContext.draw(MapContext.java:1092)     
> > 
> com.iver.cit.gvsig.fmap.MapControl$PaintingRequest.paint(MapCo
ntrol.java:1043)     
> > 
> com.iver.cit.gvsig.fmap.MapControl$Drawer2$Worker.run(MapContr
ol.java:1234)     
> > java.lang.Thread.run(Unknown Source)
> >
> > Therefor I would like to check the hack from Frank. But as 
> I'm new in that proj-stuff I have no idea where to find the 
> PROJ.4 epsg init file. And is just enough to change the 
> <21781> entry in that file and afterwards to restart the 
> program? Thanks for helping a greenhorn.
> >
> > Freundliche Grüsse
> > Lorenz Fanger
> >  
> > ---------------------------------------------------------
> > Lorenz Fanger
> > Dipl. Natw. ETH & MSc (GIS)
> >  
> > CSD Ingenieure und Geologen AG
> > Rathaus, Postfach 34
> > 7430 Thusis
> > Tel. +41 (0)81 632 15 00
> > Fax +41 (0)81 632 15 01
> > e-mail: l.fanger at csd.ch   www.csd.ch
> >
> >
> >   
> >> Folks,
> >>
> >> I examined the current PROJ.4 epsg init file and for 21781 it uses:
> >>
> >> # CH1903 / LV03
> >> <21781> +proj=somerc +lat_0=46.95240555555556
> >> +lon_0=7.439583333333333 +k_0=1
> >> +x_0=600000 +y_0=200000 +ellps=bessel
> >> ++towgs84=674.374,15.056,405.346,0,0,0,0
> >> +units=m +no_defs  <>
> >>
> >> I have tried this and do not get the mentioned error.  I believe 
> >> there was an error in the epsg init file in some versions 
> of PROJ.4 
> >> so replacing the <21781> entry in the init file will hopefully 
> >> correct the issue till it is upgraded.
> >>
> >> Best regards,
> >> --
> >> ---------------------------------------+----------------------
> >> ----------
> >> ---------------------------------------+------
> >> I set the clouds in motion - turn up   | Frank Warmerdam, 
> >> warmerdam at pobox.com
> >> light and sound - activate the windows | 
> http://pobox.com/~warmerdam
> >> and watch the world go round - Rush    | Geospatial 
> >> Programmer for Rent
> >>
> >> _______________________________________________
> >> Gvsig_internacional mailing list
> >> Gvsig_internacional at listserv.gva.es
> >> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
> >>
> >>     
> > _______________________________________________
> > Gvsig_internacional mailing list
> > Gvsig_internacional at listserv.gva.es
> > http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
> >   
> 
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>