What triggers a dataset to move from pending to being available in the library?

[Hugo Estrada]

Hi,

I am uploading a dataset using the REST API. When I look in the
Geocommons UI, the data appears as pending. I assume that some
metadata must be filled before you can see it in the regular library.
What are those needed attributes?

[Bill Dollins]

Hugo,

I was having the opposite problem a while back  in that my .csv was not appearing in a pending state, which differed from the behavior in the UI. It turns out that was okay. The response I got from Kate at the time may shed some light on your situation:

"If you have geoms and the API can figure out it out the status goes all they way to completed.  The thought was people might not want to have to go through the whole wizard process if they uploaded through the API."

Based on that response, it could be that the API is not recognizing your geometries.

Bill

[Kate Chapman]

Hey Hugo,

Are you doing this through a CSV upload? You can define the types of
columns in upload.

If you look here you can see how to define column types:
http://geocommons.com/help/Data_API#Geocoding

Our new REST API documentation (which is hopefully a lot cleaner) is
here: http://developer.geoiq.com/api/rest-api/ I noticed the dataset
column definitions portion hasn't been updated yet though.

Thanks,

Kate

On Fri, Mar 18, 2011 at 7:35 AM, Hugo Estrada <hugo...@gmail.com> wrote:

[Hugo Estrada]

Hi, Bill,

Oh, so the geometry column is the trigger.

Yes, you are right. it is not recognizing the geometries. My understanding is that I must tell GeoIQ somehow which column has the geometries and what kind they are.


Kate
Yes, I am doing it through a CSV upload. So you are saying that I could include the information letting GeoIQ know the type at upload? That would be great if I could do that. Can I do that when the CSV is in the body, or will I have to create a temp file holding the CSV to be able to define the types.

Hugo

[Kate Chapman]

Hi Hugo,

If you name the column wkt or wkb it will detect it as wkt or wkb
respectively. There appears to be an issue with changing the
datatypes using URL parameters at the moment. We are looking into
though.

Thanks,

Kate

--
Kate Chapman
GeoIQ - http://developer.geoiq.com
GeoCommons - http://www.geocommons.com
c: 703-673-8834 e: ka...@geoiq.com t: @geocommons
--
This email and the information it contains are confidential and may be privileged. If you have received this email in error please notify me immediately. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and, therefore, FortiusOne does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. If you suspect the message may have been intercepted or amended please contact the sender.

[Hugo Estrada]

Hi,

Just to let other people know who run into this issue, one must call the wkt column 'ewkt'. Just using wkt doesn't seem to work, but ewkt did the trick.

Hugo