New answers tagged

0

This was merely a stupid mistake. My app's code wasn't updating the place's point column being used in the query and the data in the point query wasn't actually near London. So I thought I was setting the points close to London, but it wasn't really doing it!


1

The reason that your current query is not returning anything is because you do not have the data there to complete the query that you want. I think that you are heading in the right direction, but you will need to have more data in your places table to properly realise the way the query will behave. You stated in your comments that you want to you want to ...


2

If I understand what you are trying to do, you don't need to dissolve, you just need to summarize by landscape zone after intersecting the two datasets. If you do this in a geodatabase the area of each polygon is calculated when the intersection is completed.


1

DO NOT use Set Layer CRS unless you are told to do so. It will corrupt your data. Instead, use Save As ... to a new filemane and different CRS for vector data, and Raster -> Projections -> Warp for rasters.


0

Seems like you calculated the area after you erroneously defined the layer's crs to be a projected UTM crs from a geographic one. This is wrong. Export your polygon layer to a new layer with the required CRS, then change the map canvas CRS to the same one. This way your calculation will be correct Example: Here is your polygon when defined in WGS 84 ...


0

This method should clean up the point layer many points per polygon: Use Feature To Point to create new centroid point layer representing each polygon Use Generate Near Table to identify the nearest point layer to the new polygon/centroid point layer (this will give you the fid value of each layer) Join near table result back to original point layer (using ...


1

I can't comment because of status credits, but in response to You could just calculate and export the centroid of the polygon/building footprint to give you one point. It is to be weary that centroids don't necessarily fall within polygons (buildings), such as polygons with donuts (in your instance a building with an atrium). http://support.esri....


2

I suggest using the Delete Identical Tool. However, the precise application depends on both your data and the purpose of your task. In case your point features share the same location (you want to delete duplicates), use the Delete Identical Tool and select the "Shape" field. In case your point features don't share the same location and you want to ...


1

You could just calculate and export the centroid of the polygon/building footprint to give you one point.


4

If you already have the Name field, as your images shows, then right-click on the field header and select "Field Calculator...". In the field calculator window, enter an expression in either VB Script or Python which checks the value of GRIDCODE and returns the appropriate name for each of the four possible values. To calculate the total area for each ...


1

MapInfo Pro Advanced can also be used for multi-spectral analysis on Landsat data. Here's an article from The MapInfo Pro Journal that gets you started: http://web.pb.com/mapinfopro-dec-2015/Get-On-The-Grid-Working-With-Multispectral-Image-Files


1

A good starting point is the Semi-Automatic Classification toolbox in QGis. The plugin can be found here and a good basic tutorial can be found here. On the same site as the tutorial, you can find other, more complex, tutorials on the same topic.


0

Maybe you can find the solution via the is_in parameter of overpass-api? see these postings: http://forum.openstreetmap.org/viewtopic.php?id=29128 http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#Query_for_areas_.28is_in.29]2 https://help.openstreetmap.org/questions/48088/what-makes-a-closed-way-show-up-as-an-enclosing-feature-with-query-...


0

Set quantize to false before adding featureLayer to map. featureLayer.quantize = false;


0

I might expect the results for area calculated in the projected space to be different from those using geographic coordinates. It just depends what areas the tool claim to compute. Consider the "square" whose corners are at the UTM coordinates 18n 528007 4467447 18n 528008 4467447 18n 528008 4467448 18n 528007 4467448 It might be plausible to ...



Top 50 recent answers are included