Closed cvvergara closed 2 years ago
A revision of the documentation was performed on develop branch. Porting that revision to 3.3.2 and adjusting to 3.3.2's functions.
edges
edge_table
category_id
reverse_category_id
combinations
combinations_table
geom
the_geom
pgr_extractVertices
The general looks of this documentation: https://docs.pgrouting.org/dev/en/index.html the pgRouting concepts page: https://docs.pgrouting.org/dev/en/pgRouting-concepts.html
Translation was ported, but is not all processed because of fuzzy marks that need to be resolved with weblate.
fuzzy
@pgRouting/admins
Coday is not checking, (maybe because of so many differences) So please ignore codacy checks.
Documentation
A revision of the documentation was performed on develop branch. Porting that revision to 3.3.2 and adjusting to 3.3.2's functions.
edges
instead ofedge_table
category_id
andreverse_category_id
.combinations
instead ofcombinations_table
geom
instead ofthe_geom
pgr_extractVertices
to create a routing topologyThe general looks of this documentation: https://docs.pgrouting.org/dev/en/index.html the pgRouting concepts page: https://docs.pgrouting.org/dev/en/pgRouting-concepts.html
Translation was ported, but is not all processed because of
fuzzy
marks that need to be resolved with weblate.@pgRouting/admins