Live data from Hacker News

PostGIS – Spatial and Geographic Objects for PostgreSQL

postgis.net

51–60 of 89 posts

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#51

What would be a good front end framework to use with PostGIS with capable rendering of GiS artifacts to make a compete desktop GIS application? The only viable open source route I am seeing is through some kind of QGIS extensions. Is there something better for that purpose?

R seems like a great idea, with building shiny apps...

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#52

FWIW, even though PostGIS is pretty great, if your use-case is primarily offline analysis and you don't need the data to be permanently accessible or writable, consider not using a database at all. You can do a lot, a lot faster with e.g. https://shapely.readthedocs.io/en/stable/manual.html and/or https://geopandas.org/ .

Yes, even for on-disk read-only use cases, shapefiles are almost always much faster. Overhead from serialization, network, etc often dominates the performance of GIS.

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#53
post #27
post #25

Earlier quoted context omitted.

Comparatively, I've spent 4 years of my life on a CompSci degree + 2 years on a GIS Advanced Diploma achieved over 10 years ago mind you). There was a point in my life a few years ago where my study was so unnoticed and under appreciated that I gave it up and now I just do full project management - and I barely even do that. I blame the internet and the accessibility of knowledge to the point where people can go "IDK…

Not his or her fault the tooling obseleted the specialty knowledge.

I think it's more that the tooling has been commoditised. Historically, professional GIS was very much about Esri's tools (and, to a lesser extent, MapInfo). Your employability was directly linked to your ArcGIS proficiency.

Now, there's a massive ecosystem of open-source GIS: PostGIS is probably the standout, but also QGIS, everything around OSM, GDAL/OGR, and a hundred others. For government work and some parts of academia then Esri still dominates, but there's now much more to "geo".

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#54

FWIW, even though PostGIS is pretty great, if your use-case is primarily offline analysis and you don't need the data to be permanently accessible or writable, consider not using a database at all. You can do a lot, a lot faster with e.g. https://shapely.readthedocs.io/en/stable/manual.html and/or https://geopandas.org/ .

Do those assume/require that all the data will fit into memory?

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#55
post #25
post #12

4 years ago one of my clients wanted to "donate" a system for the local fire department to help them do a quick proximity search to find the fire hydrants and quickly choose the healthy one near the fire. And since it was charity and had a bunch of private data Google was not an option ($$$$), so I (just a full-stack developer back then) was like "listen I have no idea what is this GIS stuff, but I'll give it a try",…

Comparatively, I've spent 4 years of my life on a CompSci degree + 2 years on a GIS Advanced Diploma achieved over 10 years ago mind you). There was a point in my life a few years ago where my study was so unnoticed and under appreciated that I gave it up and now I just do full project management - and I barely even do that. I blame the internet and the accessibility of knowledge to the point where people can go "IDK…

i've seen some people complain in that manner.

not sure if this applies to you directly, but here's my 2¢:

1. a lot of people fall for the meme and drink the koolaid that if you spend 6+ years doing nothing more than studying then BOOM, you'll graduate and companies will just blindly start throwing money at your face. surprise surprise, it doesn't work like that.

2. people should follow their passion and everything but they should also at least keep an eye on the market.

3. students (not universities) should really start considering an university course unfinished without some kind of internship. if you manage to get an internship in a company that uses the tech you're interested into (in your case, gis) you can either realize you don't like it that much or understand what the direction for your studies need to be in order to be more proficient. (applying for internships is sampling the market, btw)

4. specialists are only needed up to a certain points. in most situations a good generalists can learn enough to get the ball rolling and bring home results. see like an 80-20 pareto principle or something like that. btw, a good generalist can surpass a specialist over time.

> I blame the internet and the accessibility of knowledge to the point where people can go "IDK WTF this is, but lemme google it".

the people you complain about probably can already do a lot of other useful stuff, to the point they can just "lemme google it".

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#58
post #33

PostGIS is loads of fun with sports data. Being able to find similar passages of play just using ST_MakeLine and ST_FrechetDistance feels like magic when you first do it in all of five lines of code. Spatial tools are a bit like logic programming in that they’re very slightly esoteric. But once you know they’re the right hammer for some nails, they’ll save you lots of time and effort over your life, and let you expre…

This sounds really interesting. Was thinking it would be cool to build a hobby project in this space, but wasn't sure how to get started. Do you have any recommended sources for sample datasets to play around with?

We (StatsBomb) make a bunch of stuff available at:

https://github.com/statsbomb/open-data

Interesting stuff from Metrica too:

https://github.com/metrica-sports/sample-data

There are other less legit sources that you may be able to work out for yourself. :)

Re: PostGIS – Spatial and Geographic Objects for PostgreSQL

#59
post #27

Earlier quoted context omitted.

Not his or her fault the tooling obseleted the specialty knowledge.

I think it's more that the tooling has been commoditised. Historically, professional GIS was very much about Esri's tools (and, to a lesser extent, MapInfo). Your employability was directly linked to your ArcGIS proficiency. Now, there's a massive ecosystem of open-source GIS: PostGIS is probably the standout, but also QGIS, everything around OSM, GDAL/OGR, and a hundred others. For government work and some parts of…

This right here. GIS is accessible to anyone who knows Javascript, Python, and SQL thanks to the open source GIS ecosystem. Previously it was the sole domain of ESRI priests.

Now this is a net good thing, but there are downsides. Generalists wielding specialist tools means that a lot of the wonky basics aren't known until things break. But this is a blip compared to the step-change of making an entire field accessible to anyone who's a decent programmer with a healthy appetite for research. It's crazy how much you can spin up with PostGIS, Python, Mapbox and/or Leaflet...no ESRI license needed.

Post reply on HN