New answers tagged

0

For the climate data, there is PlanetOS API with a number of public datasets that have modelled and reanalysis data. You can access that data per geo point (LonLat) and time range in JSON or CSV format. Or you can acquire raster data via OpenDAP API. Disclaimer: I work for PlanetOS, we support & promote public and open source projects. So here are some ...


0

Have you considered GeoNode? It's based on Django which is used for user/groups authentication and it is using the same stack you mentioned (Postgres/PostGIS Geoserver & Openlayers) http://geonode.org/


0

Have you tried restarting your computer? Seriously. Also, what kind of server are you connecting to? Troubleshooting is different depending on if it's Oracle, Microsoft SQL Server, open source, etc.


0

This may not be the source of your problems, but make sure the "show all records" icon is selected. Otherwise the row values will be shown for only the rows that have been selected.


3

Assuming you have two tables "a" and "b". Table "a" is the table to be cut. CREATE TABLE a ( id serial PRIMARY KEY, geom geometry(MultiPolygon,31370) ); Table "a" is of type multipolygon because we don't know yet if some polygons will be separated in multiple parts afther the "cookie cut". CREATE TABLE b ( id serial PRIMARY KEY, geom ...


1

Yep! All you need is the username and table name and use CartoDB's SQL API like this: http://{user name}.cartodb.com/api/v2/sql?q=SELECT%20*%20FROM%20{table name}&format=csv&filename={whatever you want} For instance, I have a table of earthquakes in my account that you can get the CSV for like this: ...


0

If you don't need the old copy of the table anymore you could use: if arcpy.Exists(table): arcpy.Delete_management(table) to get rid of the old table, then use arcpy.TableToTable_conversion() (http://pro.arcgis.com/en/pro-app/tool-reference/conversion/table-to-table.htm) to convert your attributes to a dbase table in your SDE. Alternatively you'd have ...


1

For the record: Enterprise geodatabase libraries were available for both 32-bit and 64-bit servers at 10.0, and have shipped exclusively 64-bit since ArcGIS 10.1. There has never been a "32-bit bottleneck" in ArcSDE client applications (as of the time of the original post, the increased 64-bit instruction size actually slowed performance, though modern ...



Top 50 recent answers are included