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

Update Spatial docs #2723

Merged
merged 1 commit into from
Oct 5, 2020
Merged

Update Spatial docs #2723

merged 1 commit into from
Oct 5, 2020

Conversation

bricelam
Copy link
Contributor

@bricelam bricelam commented Oct 1, 2020

Fixes #1118, fixes #2352, fixes #2611, fixes #2674

@bricelam bricelam requested a review from a team October 1, 2020 23:01
@smitpatel
Copy link
Member

I was just surprised that Brice wrote 9,700 lines worth of content in docs. 😮

@bricelam
Copy link
Contributor Author

bricelam commented Oct 1, 2020

lol, that JSON file is pretty big. I'll reduce it.


By default, spatial properties are mapped to `geography` columns in SQL Server. To use `geometry`, [configure the column type](xref:core/modeling/entity-properties#column-data-types) in your model.

## Geography polygon rings
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be a lower-level heading?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so, it's not really related to choosing between geometry or geography

@@ -23,22 +23,19 @@ Microsoft.EntityFrameworkCore.SqlServer | [Microsoft.EntityFrameworkCore.SqlServ
Microsoft.EntityFrameworkCore.Sqlite | [Microsoft.EntityFrameworkCore.Sqlite.NetTopologySuite](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Sqlite.NetTopologySuite)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can remove the 'EF Core 2.2' note

Should we add a column for the first version where spatial is supported for each provider?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to keep the 2.2 note until 2.1 goes out of support. All providers work on EF Core 3.1.

@@ -233,6 +233,9 @@
href: core/providers/sql-server/indexes.md
- name: Memory-optimized tables
href: core/providers/sql-server/memory-optimized-tables.md
- name: Spatial data
displayName: GIS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we leave spatial data as the display name? Am just not sure everyone knows the name GIS. Not sure.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add Spatial Data too for localization.

Copy link
Contributor Author

@bricelam bricelam Oct 2, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol, displayName has nothing to do with the displayed name. (But I can certainly see why you might think that.) It's for additional keywords users can search for:
image

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