Opened 18 months ago
Closed 18 months ago
#5552 closed defect (invalid)
topology.AsTopoJSON bogus output
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.4.1 |
| Component: | topology | Version: | 3.4.x |
| Keywords: | Cc: |
Description ¶
According to downstream ticket https://gitlab.com/nibioopensource/pgtopo_update_gui/-/issues/13#note_1578681242 the topology.AsTopoJSON function is producing invalid TopoJSON.
I'm attaching an export of the topology referred to as "case3" in the downstream ticket.
Change History (3)
by , 18 months ago
| Attachment: | topojson-issue.pgtopo added |
|---|
comment:1 by , 18 months ago
comment:2 by , 18 months ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I confirm this was a downstream issue. Closing as invalid.
Note:
See TracTickets
for help on using tickets.
I could not reproduce this in core and I'm now thinking it's not the topology.AsTopoJSON function itself but the caller outputting the "arcs" array in the wrong way. See https://gitlab.com/nibioopensource/pgtopo_update_sql/-/issues/265
I guess we could be providing some function to output that "arcs" object to help users.