pgRouting/pgRouting — Spanish @ OSGeo Weblate: Other PostGIS options are * `ST_ConvexHull <https://postgis.net/docs/ST_ConvexHull.html>`__ * `ST_ConcaveHull <https://postgis.net/docs/ST_ConcaveHull.html>`_

Translation

English

Spanish

Needs editing

Skip

	English	Spanish	Actions
	Kruskal's running time: :math:`O(E * log E)`	Tiempo de ejecución de Kruskal: :math:`O(E * log E)`
	Metrics - Family of functions	Métricas - Familia de funciones
	Migration guide	Guía de migración
	Several functions are having changes on the signatures, and/or have been replaced by new functions.	Varias funciones están teniendo cambios en las firmas, y/o han sido remplazadas por nuevas funciones.
	Results can be different because of the changes.	Resultados pueden ser diferentes dado los cambios.
	All deprecated functions will be removed on next major version 4.0.0	Todas las funciones obsoletas serán removidas en las siguiente versión mayor 4.0.0
	Migration of ``pgr_alphaShape``	Migración de ``pgr_alphaShape``
	Starting from `v3.8.0 <https://docs.pgrouting.org/3.8/en/migration.html>`__	Comenzando en `v3.8.0 <https://docs.pgrouting.org/3.8/en/migration.html>`__
	Before Deprecation: The following was calculated:	Antes de la Depreciación: Se calculó lo siguiente:
	An alphaShape was calculated	Se ha calculado un alphaShape
	After Deprecation:	Después de la migración
	PostGIS has two ways of generating alphaShape.
	If you have SFCGAL, which you can install using
	Since PostGIS 3.5+ use `CG_AlphaShape <https://postgis.net/docs/CG_AlphaShape.html>`__
	For PostGIS 3.5+ use the old name ``ST_AlphaShape``
	Other PostGIS options are * `ST_ConvexHull <https://postgis.net/docs/ST_ConvexHull.html>`__ * `ST_ConcaveHull <https://postgis.net/docs/ST_ConcaveHull.html>`__	Se pueden utilizar varias funciones de PostGIS: `ST_Intersects <https://postgis.net/docs/ST_Intersects.html>`__, `ST_Crosses <https://postgis.net/docs/ST_Crosses.html>`__, `ST_Overlaps <https://postgis.net/docs/ST_Overlaps.html>`__, etc.
	Migration of ``pgr_createTopology``	Migración de ``pgr_createTopology``
	A table with `<edges>_vertices_pgr` was created.	Se ha creado una tabla con `<edges>_vertices_pgr`.
	After Deprecation: The user is responsible to create the complete topology.	Después de la depreciación El usuario es responsable de crear la topología completa.
	Build a routing topology	Construir una topología de ruteo
	The basic information to use the majority of the pgRouting functions ``id, source, target, cost, [reverse_cost]`` is what in pgRouting is called the routing topology.	La información básica para usar la mayoría de las funciones de pgRouting ``id, source, target, cost, [reverse_cost]`` es lo que en pgRouting se llama topología de ruteo.
	``reverse_cost`` is optional but strongly recommended to have in order to reduce the size of the database due to the size of the geometry columns. Having said that, in this documentation ``reverse_cost`` is used in this documentation.	``reverse_cost`` es opcional pero se recomienda encarecidamente tenerlo para reducir el tamaño de la base de datos debido al tamaño de las columnas de geometría. Dicho esto, en esta documentación se utiliza ``reverse_cost``.
	When the data comes with geometries and there is no routing topology, then this step is needed.	Cuando los datos vienen con geometrías y no hay topología de ruteo, entonces este paso es necesario.
	All the start and end vertices of the geometries need an identifier that is to be stored in a ``source`` and ``target`` columns of the table of the data. Likewise, ``cost`` and ``reverse_cost`` need to have the value of traversing the edge in both directions.	Todos los vértices iniciales y finales de las geometrías necesitan un identificador que se almacenará en las columnas ``source`` y ``target`` de la tabla de los datos. Del mismo modo, ``cost`` y ``reverse_cost`` necesitan tener el valor de atravesar la arista en ambas direcciones.
	If the columns do not exist they need to be added to the table in question. (see `ALTER TABLE <https://www.postgresql.org/docs/current/sql-altertable.html>`__)	Si las columnas no existen, hay que añadirlas a la tabla en cuestión. (véase `ALTER TABLE <https://www.postgresql.org/docs/current/sql-altertable.html>`__)
	The function :doc:`pgr_extractVertices` is used to create a vertices table based on the edge identifier and the geometry of the edge of the graph.	La función :doc:`pgr_extractVertices` se utiliza para crear una tabla de vértices basada en el identificador de arista y la geometría de la arista del grafo.
	Finally using the data stored on the vertices tables the ``source`` and ``target`` are filled up.	Finalmente, utilizando los datos almacenados en las tablas de vértices, se rellenan los campos ``source`` y ``target``.
	Migration of ``pgr_createVerticesTable``	Migracion de ``pgr_createVerticesTable``
	After Deprecation: The user is responsible to create the vertices table, indexes, etc. They may use :doc:`pgr_extractVertices` for that purpose.	Después de la depreciación: El usuario es responsable de crear la tabla de vértices, índices, etc. Para ello puede utilizar :doc:`pgr_extractVertices`.
	Migration of ``pgr_analyzeOneWay``	Migración de ``pgr_analyzeOneWay``
	Number of potential problems in directionality	Número de problemas potenciales en la dirección

mt:deepl

Suggestion added

Suggested change:

19 hours ago

Loading…

mt:deepl

Suggestion added

English

Spanish 126 characters edited

19 hours ago

None

String added in the repository

English

Spanish 237 characters edited Current translation Needs editing

19 hours ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

String age

19 hours ago

Last updated

19 hours ago

Source string age

19 hours ago

Translation file

locale/es/LC_MESSAGES/pgrouting_doc_strings.po, string 1244