You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sedona.apache.org by ji...@apache.org on 2023/01/26 11:12:33 UTC
[sedona] 14/23: Deployed 8f95a2d7 to latest-snapshot with MkDocs 1.4.2 and mike 1.1.2
This is an automated email from the ASF dual-hosted git repository.
jiayu pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/sedona.git
commit 07b9bede750adf24e5800dc3b61fd2687bc6d6a3
Author: Jia Yu <ji...@apache.org>
AuthorDate: Thu Jan 26 01:36:48 2023 -0800
Deployed 8f95a2d7 to latest-snapshot with MkDocs 1.4.2 and mike 1.1.2
---
latest-snapshot/api/java-api/index.html | 2 +-
latest-snapshot/api/r-api/index.html | 2 +-
latest-snapshot/api/viz/java-api/index.html | 2 +-
latest-snapshot/community/contributor/index.html | 170 +++++++++------------
latest-snapshot/community/publish/index.html | 2 +-
latest-snapshot/gallery/airport-country/index.html | 2 +-
latest-snapshot/gallery/foot-traffic/index.html | 2 +-
latest-snapshot/gallery/raster/index.html | 2 +-
latest-snapshot/search/search_index.json | 2 +-
latest-snapshot/sitemap.xml.gz | Bin 236 -> 236 bytes
latest-snapshot/tutorial/sql/index.html | 14 +-
latest-snapshot/tutorial/viz-r/index.html | 4 +-
12 files changed, 85 insertions(+), 119 deletions(-)
diff --git a/latest-snapshot/api/java-api/index.html b/latest-snapshot/api/java-api/index.html
index 4fc7d975..3be910d9 100644
--- a/latest-snapshot/api/java-api/index.html
+++ b/latest-snapshot/api/java-api/index.html
@@ -2414,7 +2414,7 @@
<h1>Scala/Java doc</h1>
-<p>Please read <a href="/api/javadoc/core/">Javadoc</a></p>
+<p>Please read <a href="../javadoc/core/">Javadoc</a></p>
<p>Note: Scala can call Java APIs seamlessly. That means Scala users use the same APIs with Java users</p>
<hr>
diff --git a/latest-snapshot/api/r-api/index.html b/latest-snapshot/api/r-api/index.html
index f5ea9ba0..b4be8640 100644
--- a/latest-snapshot/api/r-api/index.html
+++ b/latest-snapshot/api/r-api/index.html
@@ -2414,7 +2414,7 @@
<h1>R doc</h1>
-<p>Please read <a href="/api/rdocs/">R docs</a></p>
+<p>Please read <a href="../rdocs/">R docs</a></p>
<hr>
<div class="md-source-file">
diff --git a/latest-snapshot/api/viz/java-api/index.html b/latest-snapshot/api/viz/java-api/index.html
index 1b1b48b1..990b0fc1 100644
--- a/latest-snapshot/api/viz/java-api/index.html
+++ b/latest-snapshot/api/viz/java-api/index.html
@@ -2414,7 +2414,7 @@
<h1>RDD</h1>
-<p>Please read <a href="/api/javadoc/viz/">Javadoc</a></p>
+<p>Please read <a href="../../javadoc/viz/">Javadoc</a></p>
<p>Note: Scala can call Java APIs seamlessly. That means Scala users use the same APIs with Java users</p>
<hr>
diff --git a/latest-snapshot/community/contributor/index.html b/latest-snapshot/community/contributor/index.html
index 3ebbb8f7..10d06dc2 100644
--- a/latest-snapshot/community/contributor/index.html
+++ b/latest-snapshot/community/contributor/index.html
@@ -2103,15 +2103,6 @@
</a>
-</li>
-
- <li class="md-nav__item">
-
- <a href="#mentors" class="md-nav__link">
- Mentors
- </a>
-
-
</li>
<li class="md-nav__item">
@@ -2153,8 +2144,8 @@
<li class="md-nav__item">
- <a href="#send-a-notice-to-ipmc" class="md-nav__link">
- Send a notice to IPMC
+ <a href="#send-a-notice-to-asf-board" class="md-nav__link">
+ Send a notice to ASF Board
</a>
@@ -2573,15 +2564,6 @@
</a>
-</li>
-
- <li class="md-nav__item">
-
- <a href="#mentors" class="md-nav__link">
- Mentors
- </a>
-
-
</li>
<li class="md-nav__item">
@@ -2623,8 +2605,8 @@
<li class="md-nav__item">
- <a href="#send-a-notice-to-ipmc" class="md-nav__link">
- Send a notice to IPMC
+ <a href="#send-a-notice-to-asf-board" class="md-nav__link">
+ Send a notice to ASF Board
</a>
@@ -2783,36 +2765,29 @@
<td align="center">zongsizhang</td>
<td align="center"><a href="mailto:zongsizhang@apache.org">zongsizhang@apache.org</a></td>
</tr>
-</tbody>
-</table>
-<h2 id="mentors">Mentors<a class="headerlink" href="#mentors" title="Permanent link">¶</a></h2>
-<p>Mentors from Apache Incubator help the project to turn into a good shape following the "Apache" way. Thank you, mentors!</p>
-<table>
-<thead>
-<tr>
-<th align="center">Name</th>
-<th align="center">Apache id</th>
-</tr>
-</thead>
-<tbody>
<tr>
<td align="center">Felix Cheung</td>
+<td align="center"></td>
<td align="center"><a href="mailto:felixcheung@apache.org">felixcheung@apache.org</a></td>
</tr>
<tr>
<td align="center">Von Gosling</td>
+<td align="center"></td>
<td align="center"><a href="mailto:vongosling@apache.org">vongosling@apache.org</a></td>
</tr>
<tr>
<td align="center">Jean-Baptiste Onofré</td>
+<td align="center"></td>
<td align="center"><a href="mailto:jbonofre@apache.org">jbonofre@apache.org</a></td>
</tr>
<tr>
<td align="center">George Percivall</td>
+<td align="center"></td>
<td align="center"><a href="mailto:percivall@apache.org">percivall@apache.org</a></td>
</tr>
<tr>
<td align="center">Sunil Govindan</td>
+<td align="center"></td>
<td align="center"><a href="mailto:sunilg@apache.org">sunilg@apache.org</a></td>
</tr>
</tbody>
@@ -2832,19 +2807,16 @@
1. Call a vote (templates/committerVote.txt)
2. Close the vote. If the result is positive, invite the new committer.</p>
<h3 id="call-for-a-vote">Call for a vote<a class="headerlink" href="#call-for-a-vote" title="Permanent link">¶</a></h3>
-<p>We do the vote and discussion on the <a href="mailto:private@sedona.apache.org">private@sedona.apache.org</a> to enable a frank discussion. Please read <a href="hhttps://incubator.apache.org/guides/ppmc.html">ASF Incubator [...]
+<p>We do the vote and discussion on the <a href="mailto:private@sedona.apache.org">private@sedona.apache.org</a> to enable a frank discussion.</p>
<p>Let the Vote thread run for one week. A positive result is achieved by Consensus Approval: at least 3 +1 votes and no vetoes.</p>
<h4>PMC vote template</h4>
-<p>This is the email to commence a vote for a new PMC candidate. New PMC members need to be voted for by the existing PMC members and subsequently approved by the Board (or Incubator PMC for incubating projects).</p>
+<p>This is the email to commence a vote for a new PMC candidate. New PMC members need to be voted for by the existing PMC members and subsequently approved by the Board.</p>
<div class="highlight"><pre><span></span><code>To: private@sedona.apache.org
Subject: [VOTE] New PMC candidate: [New PMC NAME]
[ add the reasons behind your nomination here ]
Voting ends one week from today, or until at least 3 +1 votes are cast.
-
-See voting guidelines at
-https://incubator.apache.org/guides/ppmc.html
</code></pre></div>
<h3 id="close-a-vote">Close a vote<a class="headerlink" href="#close-a-vote" title="Permanent link">¶</a></h3>
@@ -2863,64 +2835,66 @@ Binding Votes:
The vote is ***successful/not successful***
</code></pre></div>
-<h3 id="send-a-notice-to-ipmc">Send a notice to IPMC<a class="headerlink" href="#send-a-notice-to-ipmc" title="Permanent link">¶</a></h3>
-<p>The nominating PPMC member should send a message to the IPMC (<a href="mailto:private@incubator.apache.org">private@incubator.apache.org</a>) with a reference to the vote result in the following f [...]
-<div class="highlight"><pre><span></span><code>To: private at incubator.apache.org
+<h3 id="send-a-notice-to-asf-board">Send a notice to ASF Board<a class="headerlink" href="#send-a-notice-to-asf-board" title="Permanent link">¶</a></h3>
+<p>The nominating PMC member should send a message to the ASF Board (<a href="mailto:board@apache.org">board@apache.org</a>) with a reference to the vote result in the following form:</p>
+<div class="highlight"><pre><span></span><code>To: board at apache.org
CC: private at sedona.apache.org
-Subject: [NOTICE] New PMC NAME for Apache Sedona PPMC
+Subject: [NOTICE] New PMC NAME for Apache Sedona PMC
Body:
-New PMC NAME has been voted as a new member of the Apache Sedona PPMC. the vote thread is at: *link to the vote result thread*
+New PMC NAME has been voted as a new member of the Apache Sedona PMC. the vote thread is at: *link to the vote result thread*
</code></pre></div>
-<p><strong>Note that there is a grace period of 72 hours from when the PPMC sends the NOTICE to the IPMC to when the PPMC should formally invite the proposed member. This is an important part of the overall process. Failure to do this can result in an embarassing situation for people involved.</strong></p>
<h3 id="send-the-invitation">Send the invitation<a class="headerlink" href="#send-the-invitation" title="Permanent link">¶</a></h3>
<div class="highlight"><pre><span></span><code>To: New PMC Email address
CC: private@sedona.apache.org
-Dear NEW PMC NAME,
-
-In recognition of your demonstrated commitment to, and alignment with, the
-goals of the Apache Sedona project, the Sedona PPMC has voted to offer you
-membership in the Sedona PPMC ("Podling Project Management Committee").
-
-Please let us know if you accept by replying to this email
-(including private@sedona.apache.org).
-
-The PPMC is the Incubator podling version of a project PMC ("Project
-Management Committee") that for every top-level project is tasked by the
-Apache Board of Directors with official oversight and binding votes in
-that project. When Sedona graduates from the Incubator to a top-level
-project, the project PMC is usually formed from the membership of the PPMC.
-Note that while participation in the PMC after graduation is not
-guaranteed, simply continuing your constructive and active participation
-is usually sufficient.
-
-As a PPMC member, and later as a PMC member, you are responsible for
-continuing the general project, code, and community oversight that you
-have exhibited so far. The votes of the PPMC are not legally binding;
-votes of the Incubator PMC are. However, many of the PPMC members
-are also Incubator PMC members, so they implicitly cast binding votes
-when we vote on PPMC issues. While this is an important legal
-distinction, it shouldn't enter your thinking when working on the PPMC -
-members should treat every decision as if it were legally binding for the
- ASF. Also, in day-to-day activities, the Incubator PMC member vs PPMC
- member distinction should be invisible -- we are peers.
-
-Finally, the PPMC (and assuming graduation, the PMC) is not meant to create
-a hierarchy within the committership or the community. In fact, a goal is
-to add all committers over time to the PPMC/PMC, as our belief is that those
-who do the work should get a binding vote. Therefore, in our day-to-day
-interactions with the rest of the community, we continue to interact as
-peers, where every reasonable opinion is considered, and all community
-members are invited to participate in our public voting. If there ever
-is a situation where the PMC/PPMC's view differs significantly from that
-of the rest of the community, this is a symptom of a problem that needs to
-be addressed.
-
-With the expectation of your acceptance, welcome!
-
-The Apache Sedona PPMC
+Hello [New PMC NAME],
+
+The Sedona Project Management Committee (PMC)
+hereby offers you committer privileges to the project
+[as well as membership in the PMC]. These privileges are
+offered on the understanding that you'll use them
+reasonably and with common sense. We like to work on trust
+rather than unnecessary constraints.
+
+Being a committer enables you to more easily make
+changes without needing to go through the patch
+submission process. Being a PMC member enables you
+to guide the direction of the project.
+
+Being a committer does not require you to
+participate any more than you already do. It does
+tend to make one even more committed. You will
+probably find that you spend more time here.
+
+Of course, you can decline and instead remain as a
+contributor, participating as you do now.
+
+A. This personal invitation is a chance for you to
+accept or decline in private. Either way, please
+let us know in reply to the private@sedona.apache.org
+address only.
+
+B. If you accept, the next step is to register an iCLA:
+ 1. Details of the iCLA and the forms are found
+ through this link: https://www.apache.org/licenses/#clas
+
+ 2. Instructions for its completion and return to
+ the Secretary of the ASF are found at
+ https://www.apache.org/licenses/#submitting
+
+ 3. When you transmit the completed iCLA, request
+ to notify the Apache Sedona project and choose a
+ unique Apache ID. Look to see if your preferred
+ ID is already taken at
+ https://people.apache.org/committer-index.html
+ This will allow the Secretary to notify the PMC
+ when your iCLA has been recorded.
+
+When recording of your iCLA is noted, you will
+receive a follow-up message with the next steps for
+establishing you as a committer.
</code></pre></div>
<h3 id="pmc-accept-and-icla-instruction">PMC Accept and ICLA instruction<a class="headerlink" href="#pmc-accept-and-icla-instruction" title="Permanent link">¶</a></h3>
@@ -2928,8 +2902,7 @@ The Apache Sedona PPMC
Cc: private@sedona.apache.org
Subject: Re: invitation to become Apache Sedona PMC
-Welcome. Here are the next steps in becoming a project committer. After that we will make
-an announcement to the dev@sedona.apache.org
+Welcome. Here are the next steps in becoming a project committer. After that we will make an announcement to the dev@sedona.apache.org
1. You need to send a Contributor License Agreement to the ASF.
Normally you would send an Individual CLA. If you also make
@@ -2957,11 +2930,6 @@ resources:
https://www.apache.org/foundation/how-it-works.html
https://www.apache.org/dev/
-The incubator also has some useful information for new committers
-in incubating projects:
- https://incubator.apache.org/guides/committer.html
- https://incubator.apache.org/guides/ppmc.html
-
Just as before you became a committer, participation in any ASF community
requires adherence to the ASF Code of Conduct:
https://www.apache.org/foundation/policies/conduct.html
@@ -2974,13 +2942,13 @@ The Apache Sedona PMC
<p>Once the ICLA has been filed, use the <a href="https://whimsy.apache.org/officers/acreq">ASF New Account Request form</a> to generate the request. Sedona mentors will request the account.</p>
<p>Once Sedona graduates, the PMC chair will make the request.</p>
<h3 id="add-to-the-system">Add to the system<a class="headerlink" href="#add-to-the-system" title="Permanent link">¶</a></h3>
-<p>Once the new PPMC subscribes to the Sedona mailing lists using his/her ASF account, one of the PPMC needs to add the new PPMC to the Whimsy system (<a href="https://whimsy.apache.org/roster/ppmc/sedona">https://whimsy.apache.org/roster/ppmc/sedona</a>).</p>
+<p>Once the new PMC subscribes to the Sedona mailing lists using his/her ASF account, one of the PMC needs to add the new PMC to the Whimsy system (<a href="https://whimsy.apache.org/roster/pmc/sedona">https://whimsy.apache.org/roster/pmc/sedona</a>).</p>
<h3 id="pmc-annoucement">PMC annoucement<a class="headerlink" href="#pmc-annoucement" title="Permanent link">¶</a></h3>
<p>This is the email to announce the new committer to sedona-dev once the account has been created.</p>
<div class="highlight"><pre><span></span><code>To: dev@sedona.apache.org
Subject: new committer: ###New PMC NAME
-The Podling Project Management Committee (PPMC) for Apache Sedona
+The Project Management Committee (PMC) for Apache Sedona
has invited New PMC NAME to become a committer and we are pleased
to announce that they have accepted.
@@ -3003,7 +2971,7 @@ committer account with the username '####'.
You have commit access to specific sections of the
ASF repository, as follows:
-https://github.com/apache/incubator-sedona
+https://github.com/apache/sedona
You need to link your ASF Account with your GitHub account.
@@ -3022,9 +2990,9 @@ member of the team https://github.com/orgs/apache/teams/sedona-committers
Optionally, if you want, please follow the instructions to set up your GitHub, SSH, svn password, svn configuration, email forwarding, etc.
https://www.apache.org/dev/#committers
-Additionally, if you have been elected to the Sedona Podling
- Project Mgmt. Committee (PPMC): Verify you are part of the LDAP sedona
- ppmc https://whimsy.apache.org/roster/ppmc/sedona
+Additionally, if you have been elected to the Sedona
+ Project Mgmt. Committee (PMC): Verify you are part of the LDAP sedona
+ pmc https://whimsy.apache.org/roster/pmc/sedona
</code></pre></div>
<hr>
diff --git a/latest-snapshot/community/publish/index.html b/latest-snapshot/community/publish/index.html
index 430cff4f..ed04b84e 100644
--- a/latest-snapshot/community/publish/index.html
+++ b/latest-snapshot/community/publish/index.html
@@ -3273,7 +3273,7 @@ R CMD check --as-cran apache.sedona_*.tar.gz
<h3 id="prepare-the-environment-and-doc-folder">Prepare the environment and doc folder<a class="headerlink" href="#prepare-the-environment-and-doc-folder" title="Permanent link">¶</a></h3>
<ol>
<li>Check out the 1.4.0 Git tag on your local repo.</li>
-<li>Read <a href="../../setup/compile/#compile-the-documentation">Compile documentation website</a> to set up your environment. But don't deploy anything yet.</li>
+<li>Read <a href="../../setup/compile">Compile documentation website</a> to set up your environment. But don't deploy anything yet.</li>
<li>Add the download link to <a href="../../download">Download page</a>.</li>
<li>Add the news to <code>docs/index.md</code>.</li>
</ol>
diff --git a/latest-snapshot/gallery/airport-country/index.html b/latest-snapshot/gallery/airport-country/index.html
index 1a9702d7..03d066cf 100644
--- a/latest-snapshot/gallery/airport-country/index.html
+++ b/latest-snapshot/gallery/airport-country/index.html
@@ -2417,7 +2417,7 @@
<small>
Last update:
- <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">January 26, 2023 09:04:09</span>
+ <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">January 26, 2023 09:36:43</span>
</small>
diff --git a/latest-snapshot/gallery/foot-traffic/index.html b/latest-snapshot/gallery/foot-traffic/index.html
index 12fb9f6a..671aa6a6 100644
--- a/latest-snapshot/gallery/foot-traffic/index.html
+++ b/latest-snapshot/gallery/foot-traffic/index.html
@@ -2417,7 +2417,7 @@
<small>
Last update:
- <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">January 26, 2023 09:04:09</span>
+ <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">January 26, 2023 09:36:44</span>
</small>
diff --git a/latest-snapshot/gallery/raster/index.html b/latest-snapshot/gallery/raster/index.html
index 5251518c..0b78185d 100644
--- a/latest-snapshot/gallery/raster/index.html
+++ b/latest-snapshot/gallery/raster/index.html
@@ -2417,7 +2417,7 @@
<small>
Last update:
- <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">January 26, 2023 09:04:09</span>
+ <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">January 26, 2023 09:36:44</span>
</small>
diff --git a/latest-snapshot/search/search_index.json b/latest-snapshot/search/search_index.json
index 3ddaaf1a..f92baf88 100644
--- a/latest-snapshot/search/search_index.json
+++ b/latest-snapshot/search/search_index.json
@@ -1 +1 @@
-{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":true,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"01/2023: Apache Sedona graduated to an Apache Top Level Project! \u00b6 12/23/2022: Sedona 1.3.1-incubating is released. It adds native support of GeoParquet, DataFrame style API, Scala 2.13, Python 3.10, spatial aggregation on Flink. Please check Sedona release notes. \u00b6 08/30/2022: Sedona 1.2.1-incubating is released. It supports Spark 2.4 - [...]
\ No newline at end of file
+{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":true,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"01/2023: Apache Sedona graduated to an Apache Top Level Project! \u00b6 12/23/2022: Sedona 1.3.1-incubating is released. It adds native support of GeoParquet, DataFrame style API, Scala 2.13, Python 3.10, spatial aggregation on Flink. Please check Sedona release notes. \u00b6 08/30/2022: Sedona 1.2.1-incubating is released. It supports Spark 2.4 - [...]
\ No newline at end of file
diff --git a/latest-snapshot/sitemap.xml.gz b/latest-snapshot/sitemap.xml.gz
index b15ef064..79d79689 100644
Binary files a/latest-snapshot/sitemap.xml.gz and b/latest-snapshot/sitemap.xml.gz differ
diff --git a/latest-snapshot/tutorial/sql/index.html b/latest-snapshot/tutorial/sql/index.html
index 826f1919..4788aad9 100644
--- a/latest-snapshot/tutorial/sql/index.html
+++ b/latest-snapshot/tutorial/sql/index.html
@@ -2848,7 +2848,7 @@
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
-<p>To enjoy the full functions of Sedona, we suggest you include <mark>the full dependencies</mark>: <a href="https://mvnrepository.com/artifact/org.apache.spark/spark-core_2.11">Apache Spark core</a>, <a href="https://mvnrepository.com/artifact/org.apache.spark/spark-sql">Apache SparkSQL</a>, Sedona-core, Sedona-SQL, Sedona-Viz. Please see <a href="/tutorial/demo/">SQL example project</a></p>
+<p>To enjoy the full functions of Sedona, we suggest you include <mark>the full dependencies</mark>: <a href="https://mvnrepository.com/artifact/org.apache.spark/spark-core_2.11">Apache Spark core</a>, <a href="https://mvnrepository.com/artifact/org.apache.spark/spark-sql">Apache SparkSQL</a>, Sedona-core, Sedona-SQL, Sedona-Viz. Please see <a href="../demo/">SQL example project</a></p>
</div>
<h2 id="initiate-sparksession">Initiate SparkSession<a class="headerlink" href="#initiate-sparksession" title="Permanent link">¶</a></h2>
<p>Use the following code to initiate your SparkSession at the beginning:
@@ -2971,7 +2971,7 @@ The output will be as follows:</p>
<p>The first EPSG code EPSG:4326 in <code>ST_Transform</code> is the source CRS of the geometries. It is WGS84, the most common degree-based CRS.</p>
<p>The second EPSG code EPSG:3857 in <code>ST_Transform</code> is the target CRS of the geometries. It is the most common meter-based CRS.</p>
-<p>This <code>ST_Transform</code> transform the CRS of these geomtries from EPSG:4326 to EPSG:3857. The details CRS information can be found on <a href="https://epsg.io/.">EPSG.io</a></p>
+<p>This <code>ST_Transform</code> transform the CRS of these geomtries from EPSG:4326 to EPSG:3857. The details CRS information can be found on <a href="https://epsg.io/">EPSG.io</a></p>
<p>The coordinates of polygons have been changed. The output will be like this:</p>
<div class="highlight"><pre><span></span><code>+--------------------+---+---+--------+-----+-----------+--------------------+---+
| newcountyshape|_c1|_c2| _c3| _c4| _c5| _c6|_c7|
@@ -3039,7 +3039,7 @@ The output will be as follows:</p>
<h2 id="convert-between-dataframe-and-spatialrdd">Convert between DataFrame and SpatialRDD<a class="headerlink" href="#convert-between-dataframe-and-spatialrdd" title="Permanent link">¶</a></h2>
<h3 id="dataframe-to-spatialrdd">DataFrame to SpatialRDD<a class="headerlink" href="#dataframe-to-spatialrdd" title="Permanent link">¶</a></h3>
-<p>Use SedonaSQL DataFrame-RDD Adapter to convert a DataFrame to an SpatialRDD. Please read <a href="/api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a></p>
+<p>Use SedonaSQL DataFrame-RDD Adapter to convert a DataFrame to an SpatialRDD. Please read <a href="../../api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a></p>
<div class="highlight"><pre><span></span><code><span class="kd">var</span><span class="w"> </span><span class="n">spatialRDD</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nc">Adapter</span><span class="p">.</span><span class="n">toSpatialRdd</span><span class="p">(</span><span class="n">spatialDf</span><span class="p">,</span><span class="w"> </span><span class="s">"usacounty"</span><span class="p">)</span><span class="w"></span>
</code></pre></div>
@@ -3049,15 +3049,14 @@ The output will be as follows:</p>
<p>Only one Geometry type column is allowed per DataFrame.</p>
</div>
<h3 id="spatialrdd-to-dataframe">SpatialRDD to DataFrame<a class="headerlink" href="#spatialrdd-to-dataframe" title="Permanent link">¶</a></h3>
-<p>Use SedonaSQL DataFrame-RDD Adapter to convert a DataFrame to an SpatialRDD. Please read <a href="/api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a></p>
+<p>Use SedonaSQL DataFrame-RDD Adapter to convert a DataFrame to an SpatialRDD. Please read <a href="../../api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a></p>
<div class="highlight"><pre><span></span><code><span class="kd">var</span><span class="w"> </span><span class="n">spatialDf</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nc">Adapter</span><span class="p">.</span><span class="n">toDf</span><span class="p">(</span><span class="n">spatialRDD</span><span class="p">,</span><span class="w"> </span><span class="n">sparkSession</span><span class="p">)</span><span class="w"></span>
</code></pre></div>
<p>All other attributes such as price and age will be also brought to the DataFrame as long as you specify <mark>carryOtherAttributes</mark> (see <a href="../rdd#read-other-attributes-in-an-spatialrdd">Read other attributes in an SpatialRDD</a>).</p>
<p>You may also manually specify a schema for the resulting DataFrame in case you require different column names or data
types. Note that string schemas and not all data types are supported—please check the
-<a href="/api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a> and
-<a href="/sql/src/main/scala/org/apache/sedona/sql/utils/Adapter.scala">source code</a> to confirm what is supported for your use
+<a href="../../api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a> to confirm what is supported for your use
case. At least one column for the user data must be provided.</p>
<div class="highlight"><pre><span></span><code><span class="kd">val</span><span class="w"> </span><span class="n">schema</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nc">StructType</span><span class="p">(</span><span class="nc">Array</span><span class="p">(</span><span class="w"></span>
<span class="w"> </span><span class="nc">StructField</span><span class="p">(</span><span class="s">"county"</span><span class="p">,</span><span class="w"> </span><span class="nc">GeometryUDT</span><span class="p">,</span><span class="w"> </span><span class="n">nullable</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="kc">true</span><span class="p">),</span><span class="w"></span>
@@ -3081,8 +3080,7 @@ case. At least one column for the user data must be provided.</p>
<p>All other attributes such as price and age will be also brought to the DataFrame as long as you specify <mark>carryOtherAttributes</mark> (see <a href="../rdd#read-other-attributes-in-an-spatialrdd">Read other attributes in an SpatialRDD</a>).</p>
<p>You may also manually specify a schema for the resulting DataFrame in case you require different column names or data
types. Note that string schemas and not all data types are supported—please check the
-<a href="/api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a> and
-<a href="/sql/src/main/scala/org/apache/sedona/sql/utils/Adapter.scala">source code</a> to confirm what is supported for your use
+<a href="../../api/javadoc/sql/org/apache/sedona/sql/utils/index.html">Adapter Scaladoc</a> to confirm what is supported for your use
case. Columns for the left and right user data must be provided.</p>
<div class="highlight"><pre><span></span><code><span class="kd">val</span><span class="w"> </span><span class="n">schema</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="nc">StructType</span><span class="p">(</span><span class="nc">Array</span><span class="p">(</span><span class="w"></span>
<span class="w"> </span><span class="nc">StructField</span><span class="p">(</span><span class="s">"leftGeometry"</span><span class="p">,</span><span class="w"> </span><span class="nc">GeometryUDT</span><span class="p">,</span><span class="w"> </span><span class="n">nullable</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="kc">true</span><span class="p">),</span><span class="w"></span>
diff --git a/latest-snapshot/tutorial/viz-r/index.html b/latest-snapshot/tutorial/viz-r/index.html
index dcb78ba3..c95246ce 100644
--- a/latest-snapshot/tutorial/viz-r/index.html
+++ b/latest-snapshot/tutorial/viz-r/index.html
@@ -2424,7 +2424,7 @@
<h1 id="map-visualization-applications-in-r-language">Map Visualization applications in R language<a class="headerlink" href="#map-visualization-applications-in-r-language" title="Permanent link">¶</a></h1>
<p>An important part of <code>apache.sedona</code> is its collection of R interfaces
to Sedona visualization routines. For example, the following is
-essentially the R equivalent of <a href="https://github.com/apache/incubator-sedona/blob/f6b1c5e24bdb67d2c8d701a9b2af1fb5658fdc4d/viz/src/main/scala/org/apache/sedona/viz/showcase/ScalaExample.scala#L142-L160">this example in
+essentially the R equivalent of <a href="https://github.com/apache/sedona/blob/f6b1c5e24bdb67d2c8d701a9b2af1fb5658fdc4d/viz/src/main/scala/org/apache/sedona/viz/showcase/ScalaExample.scala#L142-L160">this example in
Scala</a>.</p>
<div class="highlight"><pre><span></span><code><span class="nf">library</span><span class="p">(</span><span class="n">sparklyr</span><span class="p">)</span>
<span class="nf">library</span><span class="p">(</span><span class="n">apache.sedona</span><span class="p">)</span>
@@ -2477,7 +2477,7 @@ Scala</a>.</p>
<p>It will create a scatter plot, and then overlay it on top of a
choropleth map, as shown below:</p>
-<p><img src="/image/choropleth-map.png" width=800 /></p>
+<p><img src="../../image/choropleth-map.png" width=800 /></p>
<p>See <code>?apache.sedona::sedona_render_scatter_plot</code>,
<code>?apache.sedona::sedona_render_heatmap</code>, and
<code>?apache.sedona::sedona_render_choropleth_map</code> for more details on