GithubHelp home page GithubHelp logo

Comments (9)

randallwhitman avatar randallwhitman commented on May 30, 2024

JSON To Features is expected to work with all of Point, Line, and Polygon.
In fact, Vehicle Trip Discovery with GIS Tools for Hadoop shows an example with Polygon.

from geoprocessing-tools-for-hadoop.

StefanJaq avatar StefanJaq commented on May 30, 2024

Thanks Randall, I will check that link.
The funny thing is:
I export a Poly-FC with the tool "Feature to JSON" (attached in the post above).
So I would expect that this JSON-file should be a valid input for the tool "JSON to Features". But it throws an error ("sequence size must match size of the row").

from geoprocessing-tools-for-hadoop.

randallwhitman avatar randallwhitman commented on May 30, 2024

That does not sound right.
@azhigimont

from geoprocessing-tools-for-hadoop.

azhigimont avatar azhigimont commented on May 30, 2024

hmmm... let me see

from geoprocessing-tools-for-hadoop.

azhigimont avatar azhigimont commented on May 30, 2024

Here we go.
The provided file contains fields named SHAPE_Length, SHAPE_Area while the code checks for Shape_Length and Shape_Area (which is the way it's spelled in FGDB). It's easy to fix.
I wonder, where the alternative spelling is coming from?

from geoprocessing-tools-for-hadoop.

StefanJaq avatar StefanJaq commented on May 30, 2024

Thanks for the Research.
The fGDB and the FC were created with ArcGIS (ArcCatalog) 10.5 and the fieldnames are written SHAPE_Length, SHAPE_Area.
Now I changed the filednames in the JSON and now it works. Thanks for the hint.

from geoprocessing-tools-for-hadoop.

azhigimont avatar azhigimont commented on May 30, 2024

@StefanJaq Thanks, I can see it now. I've installed a quick fix for this issue. Please pull the latest code from the repo & let us know it it works for you!

from geoprocessing-tools-for-hadoop.

StefanJaq avatar StefanJaq commented on May 30, 2024

Sorry, the quick fix doesn't really solve the issue. I still get the same error ("sequence size must match size of the row") when trying to import the JSON.
The output json-file itself seems now right. SHAPE_Length and SHAPE_Area are spelled in the same manner in the whole file.

from geoprocessing-tools-for-hadoop.

StefanJaq avatar StefanJaq commented on May 30, 2024

@azhigimont Any idea why it didn't help?

from geoprocessing-tools-for-hadoop.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.