Repository navigation
Conversation
robward-ms
approved these changes
Jun 30, 2017
xuzhg
force-pushed
the
Bug846_RawValueForSpatial
branch
from
July 4, 2017 00:03
0cd9e9d to
f49b05a
Compare
xuzhg
added a commit
that referenced
this pull request
Jul 4, 2017
Contributor
Author
|
Merged at: f49b05a |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues
Description
In
RawValueWriter.cs, There's a function namedWriteRawValue(object value), in which it has the following codes to write the Spatial object:However, it should call
WriteJsonLight, notTryWriteAtom.For example:
Expected result
{"type":"Point","coordinates":[1.2,3.16],"crs":{"type":"name","properties":{"name":"EPSG:4326"}}}Actual result
Checklist (Uncheck if it is not completed)
Additional work necessary