Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify Property Type for Metadata #37

Open
samapriya opened this issue Jul 15, 2017 · 0 comments
Open

Specify Property Type for Metadata #37

samapriya opened this issue Jul 15, 2017 · 0 comments

Comments

@samapriya
Copy link

I don't know if many people have realized this or faced this problem
Google Collections now have a property type tag meaning for every property you need to specify a type or it assumes one for you based on the first asset which was uploaded

So for example: If someone has has a metadata which has both numeric as well as string values if the string value is uploaded first then Google will not let you upload a purely numeric string with the same metadata column.

ImageID
1189-122f0-ad123 --alphanumeric uploaded as string
1882-12929-19192-- This is purely numeric and will be uploaded as Float64

so depending on the order of the upload the property type for ImageID is either string or Float64

This can be fixed post ingestion but for now this means it will stop ingestion if an image metadata type does not match with each other so I cannot upload both these images one after the other.

I am including a task id for quick check
property satID (type FLOAT64), whose type does not match the schema (type STRING).
Exampled Task Id: TVK2FLYIW42ICXTAKFWJOEJU

Wonder if there is a way to specify a property during ingestion.

To correct this post ingestion is
earthengine asset set -p '(string)ImageID=1882-12929-19192' users/username/asset_id
However since you cannot upload the images to begin with you cannot correct the property post ingestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants