Lots of lead scraper websites online, D7 leads, KleanLeads, Apollo is a big one. My niche is local businesses however so I just go to Google maps and compile a list manually although there are some Chrome extensions that just scrape it for you for free. Then I cold call myself, yeah.
Some older context is they price per CPU core and I remember something like $10k/CPU core per year. This is from years ago and there were "enterprise" agreements in place and many millions of dollars being spent. I can't imagine they lowered prices other than maybe cloud offerings.
The support contract costs more than the "license" if my memory serves me, but its very expensive. If you're doing anything remotely complicated, using their advanced tools beyond a basic RDBMS (replication, clustering, etc.) then you need that support contract.
We were paying over $1M/yr for it inclusive of support. One real production instance (with Veritas Cluster), one reporting instance, 3 dev/QA instances. This was circa 2012, when the company had roughly $300M/yr in revenue.
I heard that a year or two after I left the company got an Oracle Audit and ended up paying a huge penalty.
Maybe they'll change it at some point. I believe if SQL Server was free, it would dominate the business. I last used it 7+ years ago and back then it was (from my subjective experience) better than Postgres is now. And I love Postgres. But SQL Server was a dream to work with. Feature rich with amazing tooling. You can get most features in Postgres with plugins and manual work, but SQL Server does it all for you.
I want to start off by saying that I am not a dev, my job is engineering that uses advanced mathematical theory to solve physical problems.
I have only set up a LinkedIn profile. Recruiters have my email from there, the conferences I've attended and contact information I've passed to my friends (being an engineering grad student helps). It varies, but the lowest is 45k/year, which living in the capital (even more if I lived in a village) of Chile means that as a single male I would live comfortably and without worries.
Yes, 45k USD remote for US companies, as opposed to entry level salary for MSc grads of 18k for the field I'm working in, in Chile. As I said, that's the lowest salary offer of remote jobs. The theory is numerical analysis of partial differential equations, specifically, the finite element method (for CFD, fluid-structure interaction, thin shell mechanics, buckling, and so on). To have a basic understanding of how to code custom FEM programs one needs at least an understanding of the fundamentals of functional analysis + analysis of PDEs + tensor calculus + the specific theory of physical application involved. These are non-trivial skills that take years and years to develop, so I would advise to anyone interested that it's best to get a job as a dev instead. I do it out of passion and because my family has a history of civil/mech eng.
The reason for such spread, I suspect, is that there is not much market for FEM professionals outside of the US and Europe, and if it exists, it's very small and unsophisticated.
No, because any further details would highlight where I work and specifically what office.
Lets just say the data intersection of: density and geocoding of users, density and location of office sites, travel time bands, and service level expectations all have a part in the final calculation.
The data is either base layers imported, or calculated layers. There is no one "comprehensive layer" nor does that concept make sense. Different groups handle their own data. We import it in and use their data for our final result.
(In fact, its the OSM approach of everything as 1 layer and tags everywhere is why a DB import and data handling is so obnoxious.)
What you’re describing sounds like it fits perfectly into PostGiS. You can have tables and you can normalize your geospatial data. With SQL, and temporary tables, you can build absolutely any analytics.
I worked in a GIS Lab with an ESRI endorsed all Arc stuff textbook author/instructor for a number years. Working on similar projects, for anything remotely complicated, I could implement anything he could do, with some python and PostGIS SQL, usually faster, and instantly reproducible.
ArcGIS is a crutch for people who can’t and aren’t willing to program. This goes for all data manipulation tools that aren’t focused on visualization.
If you have an ETL pipeline, probably best to get GIT involved.
What features do you think are missing in QGIS which hamper you in your work? I am asking because I am developing a spatial query engine which will work directly with openstreetmap.
I’m not sure that I believe you know what you’re talking about. Not trying to be offensive in that statement, but “can’t back up my very broad, generalized statement with any detail or explanation” comes across as though you’re afraid to reveal your lack of understanding about the details you elided.
You’re saying he doesn’t know what he’s talking about? He is saying you can’t really do GIS without multiple layers. This is basic knowledge for anyone working in GIS.
Explain how qgis doesn’t allow multiple layers. I have a project open right now with 6 layers. That to me seems like “multiple layers.”
And how would that concept even apply to postgis? A postgis query can operate over many tables.
And there are a variety of open source tools that allow multi-dimensional data structures. That’s multiple layers in multiple dimensions.
So I’m hoping, if there’s some aspect of a GIS layer I don’t understand, he can explain it. Qgis totally supports multiple layers in the sense that most people think of it.
He doesn’t have to divulge “secret information” to do this. If he is referring to some aspect of the qgis architecture he can just say so. Qgis is open source, their GitHub repo is clean and well documented. Im merely asking for him to explain why it handling multiple layers is somehow not really handling multiple layers.
I am not claiming to be world class expert in GIS and English is not my mother tongue. This comment by tarotuser is confusing me "Yeah, there's a massive amount of essential features just missing from OSM and QGIS. Like, even the most basic - layers. They don't even really exist in OSM side of things. Whereas if I'm doing travel-time-bands from medical centers, I absolutely must use multiple boundary layers." Layers have existed in QGIS for a long time. What are those "massive amount of essential features just missing from OSM and QGIS"?
