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

Create example records #20

Open
3 tasks
kgjenkins opened this issue Apr 20, 2021 · 6 comments
Open
3 tasks

Create example records #20

kgjenkins opened this issue Apr 20, 2021 · 6 comments

Comments

@kgjenkins
Copy link
Contributor

Several examples would be useful:

  • simple bare-bones example
  • more complex map sheets
  • more complex air photo frames
@ect123
Copy link
Contributor

ect123 commented May 3, 2021

this is a good idea, especially if the intention is for them to be imported/copied and used as boilerplate. Which would be better: downloadable text files, or embedded text? If embedded text, then they could probably only be only a single feature.

@srappel
Copy link
Member

srappel commented Dec 1, 2021

@kgjenkins
Copy link
Contributor Author

Thanks for the example, @srappel! What did you use to create it? I think you get extra points for making the value of the "location" field an array of strings (rather than just a concatenated string)!

The only issue I see is the color attribute -- shouldn't it just be "color" rather than "Printed Map (Color)"? I'm not sure where the "printed map" info go... maybe that is something that should be specified in the as-yet-undefined collection-level metadata?

@srappel
Copy link
Member

srappel commented Dec 2, 2021

Thanks, @kgjenkins . "Printed Map (Color)" is how we store that information in our Geodex system, so I just copied it verbatim. Looking at the spec, I see it's a controlled vocab. I'll push an updated version with a correction.

@kgjenkins
Copy link
Contributor Author

The spec currently has "Color", but I'd recommend we update that to be all lowercase.

@srappel
Copy link
Member

srappel commented Dec 2, 2021

I wonder if we really intended it to be controlled, or if those are examples. After all it does say "...or other color type". We have a bunch of different color types we store: color, false color IR, monochrome, blueprint, black and white, grayscale, and a few others. It wouldn't be the end of the world to lose some of that resolution, but it doesn't seem like it would hurt anything.

And to answer your other question, I exported the records from our Geodex Geodatabase as a table, supplemented and cleaned it up a bit, and then just wrote a python script to map the fields from the Geodex Schema to the OIM schema and write out the records as a GeoJSON. Sloppy trial-and-error python 😄.

My intern and I are working on some other example sets and trying to streamline the process.

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

No branches or pull requests

3 participants