Tag Info

New answers tagged

1

Vince is right. in the jsapi this is expressed as query.orderByFields https://developers.arcgis.com/javascript/jsapi/query-amd.html#orderbyfields in REST itself, the parameter is the same: http://resources.arcgis.com/en/help/arcgis-rest-api/index.html#/Query_Feature_Service_Layer/02r3000000r1000000/


0

Just in case anyone has this same problem in the future I solved this issue as below: clicked = mMapView.toMapPoint(v1, v2); Query query = new Query(); query.setOutFields(new String[] {"*"}); query.setSpatialRelationship(SpatialRelationship.INTERSECTS); Point refClicked = mMapView.toMapPoint(v1 + 35, v2); double len = refClicked.getX() - clicked.getX(); ...


0

Using the Summary Statistics option on the SLID field with "High" values for the Date_ field gave me the most recent records. You can then create concatenated fields on which to base a join, and join the original table to the summary statistics table, thus bringing in all the other relevant fields for the records.


1

I found an answer with a count & group by: select c.gid, c.*, count(c.gid) from c1 join c2 on st_disjoint(c1.geom, c2.geom) WHERE c2.nom_comm ILIKE 'blabla' GROUP BY c.gid having count(c.gid) >22 ; 22 means disjoint with all features of c2.


4

I'm having difficulty with the classification of "search by attribute" as a "language". To understand an answer to this startlingly broad question requires understanding of the meanings of a number of computer terms, including: Application software, programming language, data format, user interface, and access paradigm. ArcGIS is application software. It ...


0

You can also use the QuickOSM plugin in QGIS. You can open a local OSM file and get all keys as a column. QuickOSM will split the "other_tags" column as you want.


0

SELECT "MF_with_Zones_atts".'Geometry' AS Geometry, "MF_with_Zones_atts".'PKUID' AS ID, "Apt_Bldg_Footprints".'STATE_ID' AS STATE_ID, "MF_with_Zones_atts".'JURIS_CITY' AS JURISDICTION, "MF_with_Zones_atts".'MAIL_CITY' AS CITY, "MF_with_Zones_atts".'STATE' AS STATE, "MF_with_Zones_atts".'ZIPCODE' AS ZIP, "MF_with_Zones_atts".'COUNTY' AS COUNTY, ...


1

The problem here is you are converted the FID (objectID field type) value to string which should be a numeric value within the expression, try this: with arcpy.da.UpdateCursor('Sales_lyr', ["BOROUGH", "FID", "COUNT"]) as cursor: for row in cursor: expression = '"FID" = {}'.format(row[1]) ...


2

I'd suggest an alternative approach: Download raw OSM data and use OGR to prepare your data in such a way that the relevant tags are not mashed together in the "other_tags" column. This can be achieved by customizing OGR's osmconf.ini file as documented in http://www.gdal.org/drv_osm.html. Look for the lines # keys to report as OGR fields ...


1

I would recommend to extract all relevant ways from Overpass API using regular expressions. Here's an example which returns only ways with a permissive value in any key in the current bbox. [bbox:{{bbox}}]; way[~"."~"^permissive$"]; (._;>;); out meta; Overpass Turbo Link: http://overpass-turbo.eu/s/9ML (Hit "Run" to test) You can use pretty much the ...


0

In addition to NathanW's comment, the Contains expression must use the geometry columns: WHERE ST_Contains("MF_with_Zones_atts".geometry, "Apt_Bldg_Footprints".geometry)


0

Your variable water_buf_size is outside the scope of the Buffer_analysis. You need create the variable outside the SearchCursor, then assign the variable within the SearchCursor so it can then be accessed for the Buffer_analysis....also I would add a where clause to the search cursor where water_buf_size is not null so you only get the features that have a ...


2

I always encourage to use field delimiters to access the fields in a right way: field_name = "UNIQUEID" input_value = 5 sql_exp = """{0} = {1}""".format(arcpy.AddFieldDelimiters('c:/data/file_gdb.gdb', field_name),input_value) print sql_exp >>> 'UNIQUEID=5' Another way to do this is to use the str.format(): sql_exp = """{0} = ...


2

Just as an update to reflect the fast development in QGIS: In QGIS 2.8.2 (I don't know when it was introduced), commenting in expressions now seems to work! Using -- for one-line comments and /* ... */ for multi-line comments turnes the letters to a green color in the expression builder window and they seem indeed to be commented out! Thanks to the ...



Top 50 recent answers are included