4 ms·
I only have a little bit of GIS abilities but I found the page interesting. I think it's suitable for people as long as they have non-zero exposure to geographi
by jeffbee 6y ago
I only have a little bit of GIS abilities but I found the page interesting. I think it's suitable for people as long as they have non-zero exposure to geographic coordinate systems.
One thing about this topic that makes it hard to learn is software ergonomics. It seems like a lot of tools can work with GeoJSON now, and as I understand it GeoJSON has simply declared that there is only one coordinate system and every file uses that one. Declaring a different CRS is not allowed in the standard. However, ESRI ArcGIS will emit GeoJSON with any CRS you want. In fact if you don't tell it specifically to use the GeoJSON standard, it will instead emit GeoJSON in EPSG 3857, which is not just irritating but plainly incorrect. It further confuses the issue that the 3857 system has six other alternate names, each seemingly as well known as any of the others.
It doesn't help that geopandas will cheerfully perform a spatial join of two dataframes despite the fact that it knows full well that the two frames have incompatible coordinate reference systems. It will warn about this condition but it will do the join anyway and you might not see the warning after a million lines of console spew.
- ngcc_hk 6y agoEmbrace, extend, extinct ... ESRI arcGIS may I be suspicious
- perrygeo 6y agoYeah the software ergonomics is the challenging part. It's all tradeoffs. In the case of geopandas, would you rather: a) have the software (silently) transform your data, making decisions on your behalf about which are the source and destination projections, datum transforms, raster resampling, line densification, and precision. PRO: easy, CON: potential poor performance, accuracy. b) fail because the coordinate references systems don't match. PRO: logical, type-safe, CON: Comparing coordinate systems is not a solved problem. You can have two identical (or practically identical) systems that are not equal by their representation or your programming language semantics. c) try to naively attempt the spatial analysis in 2D cartesian space. PRO: does what it says, leaves the responsibility to the programmer. CON: does what it says, leaves the responsibility to the programmer. I've seen justification for all three approaches but no obvious solution. I tend to go with c) ala geopandas since ultimately the responsibility lies with the person building the system.
- j-pb 6y agoI think Erlangs approach is valuable: fail early and loud. There is no harm done by b), there will never be a costly mistake. If the programmer has to deal with it anyways, at least make them very aware of the fact, they can then still decide to perform c).
- framecowbird 6y agoDefinitely this. When software silently thinks it knows what I wanted and silently does the wrong thing, sometimes you find out a long time later, and it ends up being very expensive, particularly when it’s to do with data analysis. I would always prefer an error. I think this is a huge weakness of Pandas. I have to put “errors=raise” all over the place, although not many functions have that parameter.