Hi Oscar

i do not know if this is the reason, but there is a typo:

"Geoemtry"

Regards

Jesús

El lun, 15 abr 2024 a las 10:57, Oscar Diago Alonso via Geoserver-users (<
geoserver-users@lists.sourceforge.net>) escribió:

> Good morning.
>
>
>
> I have a layer with two geometry attributes: one is to store a line and
> the other has the position of its label.
>
>
>
> If I do an SLD to symbolize just the line it works fine. When I add the
> label without indicating the attribute of its position, the layer works
> fine, too.
>
>
>
> But after adding that the label should be displayed in the position of
> that second geometry field, the performance plummets and I don’t know why.
> Both fields have spatial indexes and use the same coordinate system. The
> table is stored in an Oracle database, so I made sure both fields are
> registered in the USER_SDO_GEOM_METADATA.
>
>
>
> The data comes from a view of a view.
>
>
>
> The GeoServer is 2.24.2.
>
>
>
> The style is very simple:
>
>
>
> <LineSymbolizer>
>
> […]
>
> </LineSymbolizer>
>
> <TextSymbolizer>
>
>                 <Geoemtry>
>
>                                <PropertyName>ETIQUETA</PropetyName>
>
> </Geometry>
>
> <Label>
>
>                                <PropertyName>ETIQUETA_TEXT</PropetyName>
>
> </Label>
>
> […]
>
> </TextSymbolizer>
>
>
>
> Does anyone have any idea of what could be happening? What am I doing
> wrong?
>
>
>
> Thanks for any help provided.
>
>
>
> Best regards.
>
>
> *Óscar Diago Alonso — Ingeniero GIS *(+34) 945 13 13 72 | Plza. del
> Renacimiento, 9, 2.ª planta, Oficina 2 - 01004 Vitoria-Gasteiz
> <https://www.linkedin.com/company/geograma/>
> Si no ves la imagen puedes acceder desde aquí
> <https://www.linkedin.com/company/geograma/>
>
> Esta comunicación contiene información de acceso restringido y de uso
> exclusivo del destinatario. Si usted no es el destinatario tenga en cuenta
> que cualquier distribución, copia o uso de esta comunicación o la
> información que contiene está estrictamente prohibida. Si usted ha recibido
> esta comunicación por error por favor notifíquelo en la dirección
> d...@geograma.com. Tratamos su dirección de correo electrónico y otros
> datos personales para mantener el contacto y comunicación con Ud. y, en su
> caso, remitirle información sobre nuestros productos y servicios. Si no
> desea recibir tal información envíe un e-mail en tal sentido a
> d...@geograma.com. Puede acceder, rectificar y suprimir los datos, así
> como otros derechos, como se detalla en la información adicional y completa
> a su disposición en nuestra política de privacidad en la URL
> www.geograma.com/politica-privacidad/
>
> <https://www.geograma.com/>
> <http://geograma.com/wp-content/eventos/linkedin.php>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to