@tchannel i think i would look at open source more as an engineering implementation detail rather than some huge shift in how the business operates. you work on it as much as the project requires + whatever extra you want to throw in for good karma. open source does not really take any more time than a closed source implementation done properly would take. Either way, projects should have tests, basic security, modularity, etc.
another point here is that we started as a very small, inexperienced bunch, so we have only sort of recently started doing the "done properly" part of things, with our regular work. I'm looking at embracing open source as a way to help push that more, by saying "look, all those little things you might have just hacked together as one off solutions before, try and think about how you would make these a package that other people might use" and then we'll open it if we want to. I'm wanting that to help motivate more upfront thought, better documentation, etc
i would turn that objection upside down. issues and requests are actually the most valuable part of open source. its a giant community QA department that operates for free. you can always ignore or 'wontfix' and issue if it is totally unimportant to you, but who wouldn't want to know that their software had a critical security vulnerability or a tricky logic bomb waiting to be discovered?
i pointed to free fixes and advice as one of the big sells if you're looking at open source from a business perspective
lol so sounds like the answer is "make sure you have people on your team who have their head on straight about priorities"... which... makes perfect sense
only took.... a few hours.
mostly because of huge datasets, but also because it's kinda complicated
I'm not much of a node guy (most of my suff must works offline too), so I'm sure I miss lots of node related stuff in my commits. Sorry in advance!
I had a lot of 128 Git errors yesterday, so maybe the uploaded code is not my last version. I am using turf-polygon-reduce and turf-cut in production environment, so I can assure their reliability (turf-cut tolerance: 10^-9 meters, turf-buffer issue 23). Regarding node stuff... sorry. And documentation... I know, I know... I will expand and update these days.
My tasks queue has something like that: crossing two data sets with zillions of (complex) polygons each, to find overlappings and make some spatial operations using those overlappings. Searching the way that best fits our needs (not only peformance), we have already achieved this using DotSpatial and using a custom-made QGIS plugin, next try is TURF, just for the joy of it. Once done, will post performace results.
@giulioungaretti most of the processing I do is with large datasets. Turf does well provided you think about optimizations where necessary. For example, indexing data is going to have a dramatic increase in algorithm performance, just like it would in PostGIS or other GIS engines.
@giulioungaretti also, forgot to mention that you can also test the performance of any turf module. clone the module repo and run
node bench.js to see the number of operations per second for any function. https://dl.dropbox.com/s/16v5j5y5dpubzyv/Screenshot%202015-05-05%2012.09.55.png?dl=0
I'm working on an R client for turf.js https://github.com/ropensci/lawn http://cran.rstudio.com/web/packages/lawn/ - Is there a place in turf docs to list this so others know its available?
Hey guys, I have a bunch of points (available from the api as JSON or GeoJSON) and I'd like to gradient a polygon map based on how many points reside in each polygon, similar to what happens here: https://data.phila.gov/view/hc2b-xbvz -- would turf be able to help with that?
Hey guys, I have a map where I subtract existing polygons from a newly drawn polygon using turfjs. The result polygon seems to have the wrong projection. I have explained the issue here http://stackoverflow.com/questions/32192699/turf-js-erase-produces-polygon-with-wrong-projection. Any help would be much appreciated!
@timwis - I think you could use turf-count (https://github.com/Turfjs/turf-count) to assign a count of points in each polygon, and then something like @morganherlocker's geocolor (https://github.com/morganherlocker/geocolor) to assist with the coloring
This message was deleted
@mrmanhluc no idea about turf's browser compatibility, but just guessing, I don't think IE9 compatibility is a top priority, but at the same time I'd be surprised if not most things would work.
Hey guys! I've recently wrote a simple turf module that wraps the world around 180 meridian. It's analogue of PostGIS ST_Shift_Longitude. Maybe it can be included in turf. See https://github.com/stepankuzmin/turf-shift-longitude