Support topojson?

[josiekre]

Have you thought about supporting topojson? It would mean using pre-specified topology from topojson. I use topojson a lot, and I'd prefer to calculate the shortest paths based on the topology building algo there.

[perliedman]

That does indeed make a lot of sense. I seem to remember looking into TopoJSON when I started the project, but don't remember why I decided against it.

In principle, I don't see any issue with using TopoJSON, all the information GeoJSON Path Finder needs should definitely be there. The main issue I see is with TopoJSON's alternative coordinate format (IIRC it uses some form of compressed coordinates): GeoJSON Path Finder needs to access the edges' coordinates directly in some places, and would need to be adapted to TopoJSON's alternative format.

This is not something I'm likely to take on myself at this point, but I would be happy to help out answering questions if this is something you would be interested in adding.

[josiekre]

Thanks for the reply. I'll think about extending your work for topojson if I cannot find a solution already. I've only begun digging around.