[Gvsig_english] Re: Gvsig_internacional Digest, Vol 24, Issue 32

[Pepe Vidal Balaguer]

gvsig_internacional-request at runas.cap.gva.es escribió:
> Send Gvsig_internacional mailing list submissions to
> 	gvsig_internacional at runas.cap.gva.es
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
> or, via email, send a message with subject or body 'help' to
> 	gvsig_internacional-request at runas.cap.gva.es
>
> You can reach the person managing the list at
> 	gvsig_internacional-owner at runas.cap.gva.es
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gvsig_internacional digest..."
>
>
> Today's Topics:
>
>    1. Re: symbols (jaume dom?nguez faus)
>    2. Re: Calculating areas in the atribute table. (Wolfgang Qual)
>    3. Next version release. (Antonio Gennarini)
>    4. labeling (pvmstg)
>    5. Snap one layer to another (Luca Casagrande)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 28 Jan 2008 10:15:47 +0100
> From: jaume dom?nguez faus <jaume.dominguez at iver.es>
> Subject: Re: [Gvsig_english] symbols
> To: Users and Developers mailing list
> 	<gvsig_internacional at runas.cap.gva.es>
> Message-ID: <479D9D43.7030608 at iver.es>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hello again!
>
> pvmstg wrote:
>   
>> Hi,
>>
>> Great work developpers.  It's look like you include all the need for 
>> modern symbo in a easy way.   The video doesn't show it but,  I hope 
>> you can put symbology base on many field criteria (arcmap offer 3 but 
>> more could be verry helpfull).
>>     
> Well, the set of symbols applied to a layer is a task performed by what 
> we call a "legend", in other systems it is called "renderer", or 
> "filter". The next version will allow to plug as many as new types of 
> legend as desired. As part of the shipped version, we'll include the 
> already existing "single symbol", "unique value legend", "dot density 
> legend", and "interval legend", but also the new ones "proportional 
> symbols legend" (2 variable), "graduated symbols legend" (2 variable), 
> "quantity by category legend" (2 variable), "graphic legends" (n 
> variable), "expression legends" (n variable)...
>   
>> If we can set the size of the symbols to a reference scale...
>>     
> At the moment in the developing code, there are two ways of sizing 
> symbols (well, in fact three).
>
> 1. You can set the size of the symbol in an amount of pixels. So, your 
> map will be rendered directly with this amount of pixels.
>
> This is intended for projects whose main purpose is to make spatial 
> analysis or for publishing services to map servers (see the publishing 
> extension by José Vicente Higón) where either there is no need to print 
> map layouts or the target server does not support other symbol sizing 
> than pixels.
>
> 2. You can set the size of the symbol in an amount of one of the gvSIG 
> supported units (say kilometers, miles, meters, yards, inches, 
> millimeters, etc..) and in rendering time the symbol will be scaled 
> according on the reference system selected. The reference systems 
> already coded are:
>
>     a) real world reference system. Where a meter in the symbol size 
> represents a meter in the real world. So, the closer zoom you have the 
> bigger symbol become. Intended for engineering tasks.
>     b) paper reference system. Where the unit scaled to the distance in 
> the map layout (or even screen). This means that if you want a symbol to 
> be say 2cm length, it will be drawn at this size in the screen, in the 
> paper, no matter the zoom. It is calculated based in the DPI 
> (dots-per-inch) in the current rendering context. This is intended for 
> map producing tasks
>   
>> Also, like I ask before, can we be able to export these labeling to an 
>> annotation class for faster rendering and edition.
>>     
> Yes, as I wrote in the previous mail, the annotations will export all 
> the new features and enable edition capabilities as they are native 
> geometries in native layers.
>   
>> If, in the future you could also make these annotation manualy 
>> ajustable...  You can't always have the best location of annotation 
>> so, beeing able to edit labeling to manualy place them  could be verry 
>> usefull.
>>     
> Of course!
>   
>> I ask before but, no answer.  Since esri is moving to file geodatabase 
>> and plan to release and api for that I hope gvsig project will include 
>> it's support as soon as possible.
>>     
> Sorry, I cannot answer this.
>   
>> Thanks again... waiting for the next release..
>>
>> Marcel
>>
>>
>> _______________________________________________
>> Gvsig_internacional mailing list
>> Gvsig_internacional at runas.cap.gva.es
>> http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
>>     
>
> Hope the work will be useful.
> Salut!
>
>   



Este mensaje y sus archivos son confidenciales. No está permitida su reproducción o distribución sin la autorización expresa de "IVER Tecnologías de la Información". Si usted no es el destinatario previsto, queda desautorizado cualquier uso, acceso o copia de este mensaje. Si ha recibido este mensaje por error, por favor bórrelo e infórmenos por esta misma vía.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pepe_vidal.vcf
Type: text/x-vcard
Size: 260 bytes
Desc: not available
Url : http://runas.cap.gva.es/pipermail/gvsig_internacional/attachments/20080128/45fcef94/pepe_vidal.vcf