Calvin Metcalf

Oh I misunderstood you I thought you meant you wanted it to async load the projections in the browser, building for one projection IM down with On Dec 8, 2013...

Sorry went back and read your original post. Here is the deal. Conditional loading only is helpful in the browser, not node. To load stuff conditionally in the browser we'd...

I'm getting you, I agree building with a proj string or wkt would be a great feature. Using the proj4 def json would be even better but is dependent on...

We are on same page in general, but we can end up doing it without the try. Step 1 is to do it with proj names step 2 is based...

the [relevant code](https://github.com/proj4js/proj4js/blob/master/lib/Proj.js#L52-L59) is here but yes it's more or less exactly what your talking about the external call is `proj4.Proj.projections.get(projName)` and you can add a projection with `proj4.Proj.projections.add(require('blah'))` I...

@probins true, though when you have 2 and 3 projection builds is where we would run into problems, one thing we could have a core build with no projections and...

nothing I'm planning is going to prevent us from doing one projection builds, I'm just thinking this all the way through, people are probobly going to want tmerc + lcc...

to summarize the ideas we all have had 1. create the ability to make builds with custom projections 1. be able to pass proj strings or wkt to this 2....

my thought was that if some one wanted just utm and tmerc we could either just use the browserify ability to alias files to replace https://github.com/proj4js/proj4js/blob/master/lib/projections/index.js with one that did...

so from the first one comment, I was envisioning calling lib/projString.js or lib/wkt.js to figure out which projection is necessary. so I was thinking that a hook could [go here](https://github.com/proj4js/proj4js/blob/master/lib/Proj.js#L66)...