X

NV5 Geospatial Blog

Each month, NV5 Geospatial posts new blog content across a variety of categories. Browse our latest posts below to learn about important geospatial information or use the search bar to find a specific topic or author. Stay informed of the latest blog posts, events, and technologies by joining our email list!



Not All Supernovae Are Created Equal: Rethinking the Universe’s Measuring Tools

Not All Supernovae Are Created Equal: Rethinking the Universe’s Measuring Tools

6/3/2025

Rethinking the Reliability of Type 1a Supernovae   How do astronomers measure the universe? It all starts with distance. From gauging the size of a galaxy to calculating how fast the universe is expanding, measuring cosmic distances is essential to understanding everything in the sky. For nearby stars, astronomers use... Read More >

Using LLMs To Research Remote Sensing Software: Helpful, but Incomplete

Using LLMs To Research Remote Sensing Software: Helpful, but Incomplete

5/26/2025

Whether you’re new to remote sensing or a seasoned expert, there is no doubt that large language models (LLMs) like OpenAI’s ChatGPT or Google’s Gemini can be incredibly useful in many aspects of research. From exploring the electromagnetic spectrum to creating object detection models using the latest deep learning... Read More >

From Image to Insight: How GEOINT Automation Is Changing the Speed of Decision-Making

From Image to Insight: How GEOINT Automation Is Changing the Speed of Decision-Making

4/28/2025

When every second counts, the ability to process geospatial data rapidly and accurately isn’t just helpful, it’s critical. Geospatial Intelligence (GEOINT) has always played a pivotal role in defense, security, and disaster response. But in high-tempo operations, traditional workflows are no longer fast enough. Analysts are... Read More >

Thermal Infrared Echoes: Illuminating the Last Gasp of a Dying Star

Thermal Infrared Echoes: Illuminating the Last Gasp of a Dying Star

4/24/2025

This blog was written by Eli Dwek, Emeritus, NASA Goddard Space Flight Center, Greenbelt, MD and Research Fellow, Center for Astrophysics, Harvard & Smithsonian, Cambridge, MA. It is the fifth blog in a series showcasing our IDL® Fellows program which supports passionate retired IDL users who may need support to continue their work... Read More >

A New Era of Hyperspectral Imaging with ENVI® and Wyvern’s Open Data Program

A New Era of Hyperspectral Imaging with ENVI® and Wyvern’s Open Data Program

2/25/2025

This blog was written in collaboration with Adam O’Connor from Wyvern.   As hyperspectral imaging (HSI) continues to grow in importance, access to high-quality satellite data is key to unlocking new insights in environmental monitoring, agriculture, forestry, mining, security, energy infrastructure management, and more.... Read More >

1345678910Last
13474 Rate this article:
5.0

Why Can’t I “Get” My Data

Anonym

While working on a recent project, I needed to pull some data off of an ESRI server using a REST API. This is by no means a novel task, but just like many of you, this is not something I do on a daily basis. In preparation for this task, I brushed up on my IDLnetURL objects and read through the subsequent documentation. I felt as though I was adequately prepared and it was off to the races. First, I coded up my “get” call to obtain the geometry of the region I was working in (for this example I will use Utah).

oURL = obj_new('IDLnetURL')

oURL->SetProperty, $

  url_scheme='https', $

  url_host = 'sampleserver6.arcgisonline.com',$

  url_path = 'arcgis/rest/services/USA/MapServer/2/query?
text=Utah&geometryType=esriGeometryEnvelope&spatialRel
=esriSpatialRelIntersects&f=pjson'

Cords_Json = oUrl->Get(/string_array, /BUFFER)

Cords_Json = JSON_PARSE(strjoin(Cords_Json))

GeomJson = JSON_SERIALIZE(((Cords_Json['features'])[0])['geometry'])

This worked great and the next step was to find all the vectors that fell within the given region (for this example I will use counties). However, when I went back to my trusty “get” command it fell apart. 

oURL = obj_new('IDLnetURL')

oURL->SetProperty, $

  url_scheme='https', $

  url_host = 'sampleserver6.arcgisonline.com',$

  url_path = 'arcgis/rest/services/USA/MapServer/3/query?geometry='+GeomJson+'&geometryType=esriGeometryPolygon&spatialRel
=esriSpatialRelContains&outFields=*&f=json'

County_Json = oUrl->Get(/string_array)

Instead of nicely formed JSON it was HTML, and incomplete HTML at that. I found this perplexing until I realized that the “get” request has a return character limit of 2,048. This posed a problem given that in my region there are 29 vectors and each one has complex geometry with hundreds of vertices. So it was back to the drawing boards.

When performing a request-response from a client to a server, there are two options for returning data.  There is the “get” method and the “post” method. There are several subtle differences when it comes to these two methods, but for our purpose the main thing to note is that “get” returns the data you request embedded within the URL and because of that there is a limit on how long it can be. On the other hand, “post” returns it with the body of the request and thus does not have a limit. So as I’m sure you’ve already figured out, the “post” method was the answer to my problem.

oURL = obj_new('IDLnetURL')

oURL->SetProperty, $

  url_scheme='https', $

  url_host = 'sampleserver6.arcgisonline.com',$

  url_path = 'arcgis/rest/services/USA/MapServer/3/query?f
=json'

data = 'geometry='+GeomJson+'&geometryType=esriGeometryPolygon&spatialRel
=esriSpatialRelContains&outFields=*'

County_Json = oURL->Put(data, /POST, /BUFFER)

By using the “post” method over the “get” method, I was able to retrieve all of the counties and their names.

; get county names

County_Json = JSON_PARSE(County_Json, /TOSTRUCT)

County_Names = strarr(n_elements(County_Json.features))

for i = 0, n_elements(County_Json.features)-1 do County_Names[i] = (County_Json.features)[i].Attributes.name

print, County_Names, FORMAT='(a)'

Please login or register to post comments.