d3.geoPath, d3.geoProjection and basic projections about d3-geo HOT 4 CLOSED

d3-geo-projection would include d3.geoPath, too, yes. But at any rate, we’re going to put all the d3.geo stuff into d3-geo for 4.0, excepting only the extended projections which are in d3-geo-projection.

I’m actually going to work on this today and try to get as much done as possible. There are only two weeks left before my self-imposed July deadline. I’ve made good progress on the release notes but this is the last major piece of the code, so I’m going to try to finish the port today.

from d3-geo.

Cool, I've got a port of geoBounds ready to go once you merge geoArea.

from d3-geo.

Thanks!

from d3-geo.

I understand the value of the d3-geo functions as tools for doing spherical math, but without projections, no one will be able to render maps. Do you see a lot of use cases where developers might import d3-geo and not need d3-geo-projection?

I don’t see d3-geo being hugely useful without d3-geo-projection, but it might be moderately useful… and maybe there are different geographic projection abstractions (libraries) you might want to use? Separating our projection implementation from spherical math allows you to pick which projection library you want to use while still using our spherical math utilities if desired.

I’d rather err on the side of keeping things separated and keeping the modules smaller, and it seems like a reasonable split, here, given the complexity of geographic projection.

from d3-geo.